Re: Multilingual table design questions
From: Jon Heggland <heggland_at_idi.ntnu.no>
Date: Mon, 20 Feb 2006 17:45:36 +0100
Message-ID: <MPG.1e641084949ec8a6989768_at_news.ntnu.no>
Date: Mon, 20 Feb 2006 17:45:36 +0100
Message-ID: <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.
-- JonReceived on Mon Feb 20 2006 - 17:45:36 CET