Re: [PEPr] Comment on Internationalization::Manager

From: Date: Sun, 10 Oct 2004 20:43:29 +0000
Subject: Re: [PEPr] Comment on Internationalization::Manager
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-33753@lists.php.net to get a copy of this message
On Sunday 10 October 2004 09:28 am, Michael Wallner wrote: > Michael Wallner (http://pear.php.net/user/mike) has commented on the > proposal for Internationalization::Manager. > > Comment: > > While I find it quite cool, I wonder how its scope of functionality differs > from Translation2 and its gettext driver. > Transation2 seems focused on getting the strings out of the database/file/foo container. I18N_Manager is concerned with getting them in, and you then use the standard gettext function to get them out again, e.g. I18N_Manager::addString("Hello world."); I18N_Manager::addString("Hello world.", 'de', "Hallo Welt."); echo _("Hello, world."); This seemed to be the case when I looked at Translation1 as well. I had to spend some time with the code figuring out how the database needed to be laid out in order to work. Are you interested in integrating this kind of functionality into Translation2? > You may want to have a look at I18Nv2::setLocale() for a more distinct and > cross-platform approach to the setlocale() problem. If it doesn't fit the > needs I would be very grateful if you can describe its deficiencies, so > that I could improve I18Nv2::setLocale(). > Indeed. I had not looked at either Translation2 or I18Nv2, as I was under the mistaken impression that they were PHP5-only packages. You are correct, my functionality is superfluous. > Please note, that there's a typo in the first two lines of ::compile(). > Fixed.

Attachment: [application/pgp-signature]
« previous php.pear.dev (#33753) next »