Re: [PEPr] Comment on Internationalisation::I18N_Gettext

> Lorenzo Alberton (http://pear.php.net/user/quipo) has commented on > the proposal for Internationalisation::I18N_Gettext. > > Comment: > > I think that (as it is now), this package just acts as a wrapper to > gettext, with very small added value. > > I don't know if forcing a list of charsets in the code (files .inc) > is a good idea, since you risk to leave out many of them. I'd leave > it on to the user. Well, that's in deed the problem - at all. The key intention for this package was providing portability to users. The fact is that scripts that call PHPs setlocale() are not portable yet. Windows expects language/country codes in a three letter format like deu, dea, fra, frc etc... and Linux expexts the more common de_DE, en_US and so on. Additionally gettext behaves differently on these two platforms - it depends on the env vars LANG/LANGUAGE *and* expexts different values for these on Windows/Linux, which are de, fr, en on Windows and de_DE, en_US, ... on Linux - AFAICS. As already mentioned in the proposal exhaustive testing is needed though. > Since guessHTTP() and setCharset() are already on the TODO list for > PEAR::Translation2, what do you think about helping me with the > gettext driver for that package? I already talked to Stefan N. about integration in I18N and mailed Wolfram K. regarding this idea - I must admint I didn't have deeper look into Translation yet because it obvoisly seemed to be DB dependent. > Your .mo/.po parsers look very nice, and could replace my very naive > .po parser. A MO writer would be very interesting... :) The PO parser has been updated lately but is rather a regex-hack than a parser yet. > Please think about it, and let me know. Regards, -- Michael - < mike(@)php.net >

Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc