Reply to Re: i18n - how best to provide multilingual content

Your name:

Reply:


Posted by J.O. Aho on 01/20/07 14:01

Andy Dingley wrote:

> XML or XSLT ? If you structure the data model reasonably well, it's
> not hard to extract text strings stored in groups for each function,
> one for each language. It's easier to manage the translation and
> deployment though if the text are grouped by language into separate
> files and identified by a short identifier. The XSLT document()
> function is especially handy.

Seen such files in the Gnome2 application desktop icons, they only have one
short line in each language, the application description, but those files are
big, think how large files will become if you have 20-30 languages and you
have to replace the big file each time a language is updated or added, it's
easier IMHO to handle files that has only one language and on the server side
script it's easy select the right language file and use a backup if a
translation would be missing.

--

//Aho

[Back to original message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация