Re: building a language pack

From: Date: Wed, 24 Jan 2001 19:17:27 +0000
Subject: Re: building a language pack
References: 1  Groups: php.general 
Request: Send a blank email to php-general+get-36456@lists.php.net to get a copy of this message
I'm of the opinion that abstracting all "lang-specific" strings to an xml file is the easiest, cleanest way to go. that means "layman" authors can translate without screwing up your code, and you can get a lot of languages fast. it's also pretty convenient to get the strings out, and to add new ones. just assign an id, like: <string> <id>12</id> <lang:en>hello, world</lang:en> <lang:fr>bonjour, monde</lang:fr> </string> or something :) _alex -- Alex Black, Head Monkey enigma@turingstudio.com The Turing Studio, Inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 Saul Zaentz Film Center 2600 Tenth St Suite 433 Berkeley, CA 94710-2522 > From: jeremyf10@excite.com > Newsgroups: php.general > Date: 24 Jan 2001 10:08:55 -0800 > Subject: [PHP] building a language pack > > I'm the author of an opensource php auctioning system and have recently been > receving alot of emails concerning the availibility of different languages. > I was wondering what the best way to build a sort of language pack would be > (one file for french, one for english, one for german, etc). Something like > replacing one file containing the language specs & translations would > translate the entire system. I'm just looking for recommendations before I > start asking volunteers to translate the words. Thanks. > > > > > > _______________________________________________________ > Send a cool gift with your E-Card > http://www.bluemountain.com/giftcenter/ > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >

« previous php.general (#36456) next »