in reply to Re^2: i18n best practice
in thread i18n best practice

The only experience I have this was for GUI interfaces not web pages, but we found very quickly that it was better to use a separate resource (the GUI equivalent of a template) for each language, than lots of individual strings. The problem being that saying the same thing in different langauges can mean the length of the strings vary enormously, which makes layout a pain.

It's probably less of a pain with web pages as HTML is more flexible, but there are other considerations too. Eg. Different countries perceive colors differently according to their cultural references. I can't remember which, but one country had a real problem with there being any red on a page. It was far easier to accommodate such preferences by having a separate template for each.

The only other piece of advice I'd offer is that you get your translations done by one native speaker and verified by another independant native speaker. We had some done by a second language translator and the results were more than a little embarassing.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"I'd rather go naked than blow up my ass"

Replies are listed 'Best First'.
Re^4: i18n best practice
by jmo (Sexton) on Mar 16, 2010 at 21:19 UTC

    Somewhat disappointing but I suppose that's the way it is, I've been working at a company having the same code base for several countries and that's how they where doing it, one template per language. A bit disappointing but when also considering layout and colours it makes sense.

    Oh well, was hoping for a silver bullet here but I guess as long there are no werewolves one should be content.