Re: UU UI organization

["Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>]

You seem to be missing what I'm talking about. Yes, of course we will
use message catalogs (C/C++ have their own way of handling that,
which is conceptually similar to Java properties files).

What I am talking about is _what_ is going to be in those catalogs,
and where it'll come from. You realize that explicitly listing all available
messages is not very scalable way of doing it, right?

sergey@total-knowledge.com wrote:
> The only way to handle this stuff easily, imo, is to use properties
> files(text files with map-like structure), which attributes can be called
> from any template. Properties files can be updated through admin interface
> or even manually. So, no DB calls will be involved, which will make it
> faster.
>
>   
>> Themes can have their own user interface strings, simply because they
>> might
>> break up formatting differently. There could be also other quirks - i.e.
>> particular
>> set up might have their own themes/templates defined, and have some
>> setup-specific
>> explanations added to pages. We need to have a framework to handle these
>> sorts
>> of things easily.
>>
>> sergey@total-knowledge.com wrote:
>>     
>>> Why would they need an extra translation? Are you talking about new
>>> strings written in "user prefernces" language or any other language
>>> which
>>> is not defined in our default "language list" that can be used by user?
>>> Please elaborate with example, if possible.
>>>       
>>>> Problem here is that we will have concept of "themes", and if any
>>>> theme has its own message strings, they'll need an extra translation,
>>>> or we'll need an easy way to add message strings to global message
>>>> catalogs.
>>>>         
-- 
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com