In article <xn0eippie1uf6t001_at_news-south.connect.com.au>, murdoc_0
@hotmail.com says...
> Personally, I believe translation is purely a presentation function,
> rather than a data/business function. I would store the text in
> whatever language you want as a base level (English, probably),
> then when displaying the text, translate it. This cuts down on the
> database size, and leaves all the translation in the Presentation
> layer. Also, your database schema does not need to change every
> time a new language becomes supported.
Doesn't this just move the problem to the Presentation layer? You will
still need to design a translation database there.
--
Jon
Received on Mon Feb 20 2006 - 10:45:36 CST
