Re: Multilingual table design questions
Date: Tue, 21 Feb 2006 14:48:54 +0200
Message-ID: <dtf27o$7a2$1_at_emma.aioe.org>
"Jon Heggland" <heggland_at_idi.ntnu.no> wrote in message
news:MPG.1e641084949ec8a6989768_at_news.ntnu.no...
> In article <xn0eippie1uf6t001_at_news-south.connect.com.au>, murdoc_0
> _at_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.
One can also use a DBMS for the presentation layer. Received on Tue Feb 21 2006 - 13:48:54 CET