|
|
Posted by Andy Dingley on 01/20/07 13:16
CptDondo wrote:
> Right now all the pages are hard-coded in English. We need to provide
> multi-lingual support.
For serious non-XSLT work, consider JSP instead of PHP. The i18n tools
are vastly better. Read the O'Relliy Java internationalization book,
just for a guide to web i18n.
> backend to serve up the language based a) the user's locale, and if that
> is not set, its own locale.
Make the selection completely user-selectable, with cookie persistence,
with the methods you describe setting the default. It works just the
same by default, but it's more flexible for casual users finding
themselves using other people's computers' It's a real nuisance
otherwise!
> The PHP backend creates the pages on the fly from XML templates, so it
> wouldn't be that hard for us to change the language.
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.
Navigation:
[Reply to this message]
|