Hello Jeff, Actually, I wrote the PEAR I18N class with Wolfram Kriesing. We aimed at providing generic API that have gettext like functionality.
There is only File Container for now. It can be used without gettext module for people who don't have authority to recompile/install PHP. (i.e. Shared server users) but Gettext Container(wrapper) is planned for future release. That way, developer will be able to switch container(File, Gettext) without modifying your script. Other than that, I18N provides language negotiation, ISO-639-1 two letter language code to language name mapping, and ISO-3166 two letter country code to country name mapping. Either way, I could happily deployed Japanese/English web site. Naoki Shima -----Original Message----- From: Jeff Bailey [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 10:38 PM To: [EMAIL PROTECTED] Subject: [PHP-I18N] Opinion of cleanest/fastest php i18n solution. I'm in the process of evaluation the various ways to implement an interationally supported web application using php. So far i've taken a look at two standards based routes. 1. Pear i18n located in the cvs.php.net repository. http://cvs.php.net/cvs.php/pear/I18N?Horde=694161bb2ea40c04dfc77f8647bdc983 2. Gettext which is a function support extension within php. The Pear i18n code is experimental so I would venture to guess that the gettext solution leave something to be desired within php if it is something being worked on within the Pear project. I'd just like to get some opinions from other people that have implemented internationally support php driven websites on this mailing list. The main things that I am looking for are clean "standardized" code, speed, 100% support for the major languages including Japanese, Chinese, etc.. Thanks, -Jeff -- PHP Internationalization Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internationalization Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
