RE: [Webwork-user] Localization i18n

[Edwin D. <ede...@ja...>]

Rickard,
If you build a Example which includes the "gudelines you have outlined in
previous posts" -- it will really help WebWork ;-)

Actually, I would recommend something like this:
-- Give the Example a Meaningful Name
-- Say it is an implementation of the Example specified in Article xyz
(include the URL).
-- Say why the WebWorkn implementation is better/simple than that in the
Article.

This way, you kill 2 birds with one stone.

Edwin

-----Original Message-----
From: Rickard Oberg [mailto:ri...@jb...]
Sent: Sunday, December 03, 2000 8:28 AM
To: Edwin DeSouza; web...@li...
Subject: Re: [Webwork-user] Localization i18n


> Rickard,
> Has there been any explicit effort/thought/desing to handle construction
of
> multilingual websites?  Maybe a example that can "on-the-fly" change
between
> Swedish, English, and a couple of other languages?
>
> Here is a relevant articles:
> http://www.javaworld.com/javaworld/jw-03-2000/jw-03-ssj-jsp_p.html

Incredibly complicated way of doing it IMHO. You can do that shop in WebWork
with much less effort, by employing the guidelines I have outlined in
previous posts.

> Here is an interesting post at Enhydra:
> http://www.enhydra.org/community/mailingLists/i18n-group/msg00034.html

Here we see an occurrence where the push MVC model of XMLC becomes
difficult. As outlined in previous posts, all of these problems go away
trivially in WebWork, simply because of how it has been designed to handle
these things (or rather, it hasn't been designed to handle these things, but
a direct side-effect of its design is its ability to handle i18n well :-)

/Rickard