Re: [Phpgroupware-developers] Next Generation Framework

[C K Wu]

With 'current [language encoding] restriction', I am referring to the 
'xx' language
encoding scheme as reflected in the file name, phpgw_xx.lang .

[Correct me if I am wrong], apparently, gettext is tolerant enough to
accept xx or xx_CC as the lang specification (xx=lang code, CC=Country 
code).

As a result,

================Comment from php.net gettext function page 
=================================================
| Even though in some cases setlocale() may require a country code in 
addition to the language code this does not mean that it is required for 
gettext.

If setlocale() is set to either es_ES or es_MX gettext() will still get 
the text from a po file in the 'es' folder.

|================Another Comment from php.net gettext function page 
=================================================
|||Note to Chinese programmers....

Took me hours to figure out you cannot use

LANG=zh
but have to use
LANG=zh_TW
on some machines...

a good way to test will be to check the return of setlocale()|
====================================================================================================

It seem to me that gettext is too lenient on this count. This is why a 
xx_CC or xx_CC.charset preference setting within phpgroupware
is more desirable. It may also be a good idea that phpgroupware enforce 
the 'xx_CC' convention on folder naming.

Cheers,
CK


Dan Kuykendall ??:

> we are using the normal gettext list of lang codes. Is this not the 
> correct list we should use?
>
> C K Wu wrote:
>
> > Yes. I agree with Dave that proper or full locale support is the way 
> > to go.
> >
> > As an example of current restriction, Traditional Chinese have to 
> > been coded as 'zt', which is non-standard language encoding. AFAIK, 
> > this is causing Sitemgr to wrongly detect some Chinese user's default 
> > language setting.
> >
> > Cheers,
> > CK