Re: Localization, Internationalization, Multilanguatisation

> We need a conclusion here, too!
> 
> I vote for a caching and translating include_once function. Please agree 
> or disagree and tell us why.

I did not say much on this subject, but :

> No, really, if multiple trees per language should be maintained,
> I would think twice.

I give you 3 arguments:

1. It's principe.

2. Language comes from locale. So caching does not depend on the 
availability of translated languages, but is triggered by visitors of the 
website. This means there is no control on the size of the cache.

3. I did inventory, as you might remember. There are about 4 real 
messages, the rest is error-text. Error text happens to be displayed on 
failure. So, the complete cache is for this 4 messages only.
3. -more- You would even cache scripts without any language in it, won't 
you?

This *is* clear. I know, it's *my* opinion. And I would think twice to get 
involved with a system that silently replicates multiple times.

Cheers,
wim niemans



> 
> 
> Manuel
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe-zNu2Yekbks92Brm55YPRC3dfcadvtA/[email protected]
> For additional commands, e-mail: dev-help-zNu2Yekbks92Brm55YPRC3dfcadvtA/[email protected]
> 
>