This is how I did it on http://kuehnle.de
I don't rely on browser information, though. I let users make
their choice.
I didn't try to find a single solution for all purposes. Instead,
I have a general translation table 'strings' for words or sentences
that normally would appear in my code and
I'm working on two projects for which I'm trying to build in
functionality to localize or internationalize later.
For one project, a large chunk of text would be translated into an
unknown number of languages. For this I'm allowing the text to be a
'text' field in a record, with other fields
my only comment on this is that although you appear to have two different
problems - you don't!
pick a single solution to both cases; then when your solution needs
modification, you only have one set of code to change.
this obviously is computer science; only tenuously related to mysql.
At
