Translation issues aside, one of the best parts of storing translations in a database is that you can quite easily build a web interface to the database table. You write a script which greps your source-code/templates so that it inserts the new strings, and deletes any unused ones.
This works really well for web pages as you simply set the encoding to UTF8, provide a combobox of selectable languages / regions, provide a textarea for the string input and a submit button. As a programmer I never need to speak to the translators as they simply use the web interface. The only real issue that the programmer has to do is to set a few extra template variables: TMPL_VAR document_charset TMPL_VAR document_direction TMPL_VAR document_language TMPL_VAR document_direction_default TMPL_VAR document_direction_inverse The first three should be used in your document headers and occasionaly in table headers. The other two are used for formatting within tables, so that your text/image alignment comes out correct for the language. hope this helps Mathew ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Html-template-users mailing list Html-template-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/html-template-users
