on 9/27/2000 1:29 PM, "Christophe Lombart" <[EMAIL PROTECTED]> wrote:
> and why not to use a XML repository for that which will contains all
> translation and define just only one template. by this if we change the
> template or add a new language, it should be easier.
>
> Christophe
Because internationalization affects layout. A page in Japanese will read
totally differently than a page in English and the character size as well as
the number of words might affect the layout as well because there might not
be enough space to accommodate the translation.
By having different screens, it sucks as a maintenance problem, but if you
can think of a better way to deal with the layout issue, feel free to
suggest it.
<rant>
I am getting *really* tired of people trying to throw XML at every single
solution without actually thinking of *why* they are doing it or the larger
picture involved. XML is not the solution to everything.
</rant>
thanks,
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
