on 2/9/01 2:20 AM, "ingo schuster" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Today, it is not easy to build a multi-lingual web application with turbine
> (apart from having a set of screens for each language). If different users
> are to be served responses in different languages, then it's currently up
> to the output producing modules to detect the requested language.
> I'd find it very useful if RunData could hold information about the
> preferred language for the response. As default the it could be set to the
> browsers preferred language information and the application could override
> this setting if it knows better.
>
> Are you interrested in this enhancment? I'd develop patches.
>
> ingo.
-1. I like Sean's approach (however, it doesn't look thread safe) and this
is also what the LocalizationService is for, which is a nice wrapper around
Java's localization stuff.
The addition that needs to be made to Turbine Template Service is to allow
the templates to be localized by file extension as well.
thanks,
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
