Re: Localization, Internationalization, Multilanguatisation

On 25 Feb 2005 at 1:29, Jean-Christophe Michel wrote:

> 
> If conf is long to load all values, conf should be cached.

Yes. You mean conf.php or the conf_values?

> Since lang strings will always change slower than php/tpl/ndf files will
> be used, files with lang strings replaced should be cached. This is the
> case with our current phing-time localization. I propose to keep this
> behaviour but wait till someone asks for a page to rebuild it.

First. Convince yourself that momentarily only error messages needs 
translation. They happen to display once a month, I guess.
You favour caching (and using filemtime() 3000 times an hour) in order to
have these messages display faster? We are talking about very few real messages here.
(exagerating makes it more clear ;-))
Second. Some vietnamees visits your site. The language is not available. 
You set the language to default french, I guess. How do you cache, as 
being french or as vietnamees?
Third. My workspace application does it's own translation. It supports 
vietnamees. But not for binarycloud core using string files.
How would you cache that one? Being french or vietnamees?

It will become complicated. I've seen software that does an install for a 
language. That install does read the complete translated_strings_thing, 
finds the php_files using the strings and creates specific translation 
files for these php_files individually.
A variation of this would be: find the php_files which uses the strings, 
insert defines for them in all these files and caches them.

wim