For Web applications you may as well maintain your strings in a database. The language table will have columns for message key, language identifier, and string. MSG0, en-US, Welcome to our website! MSG0, fr-CA, ..... MSG125, en-US, blah blah... MSG125, fr-CA, ....
You can be a bit more clever and have keys consist of web page and id, so that you can easily read into n array all the keys associated with a page for a single language, and then reference them from the array rather than individual database calls. But with good database cacheing, it’s not always a significant optimization. tex -----Original Message----- From: Andre Polykanine [mailto:an...@oire.org] Sent: Monday, January 17, 2011 5:49 AM To: php-i18n@lists.php.net Subject: [PHP-I18N] How to make the i18n without serious tools? Hello Php-i18n, I need to make my projects international. However, my hosting provider won't install anything for me, so no GetText, no ICU. Could you suggest me something? I tried to make constants definitions like this: <? define("MSG0", "Welcome to our website!"); ... define(MSG125", "blah blah"); ?> But it's reeeally hard to maintain in future. Thanks! -- With best regards from Ukraine, Andre Skype: Francophile Twitter: http://twitter.com/m_elensule Facebook: http://facebook.com/menelion -- PHP Unicode & I18N Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Unicode & I18N Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
