yeah, but isnt that what resource bundles
do in a way?
i was thinking about an approach with
different templates for each language.
on the one hand this doubles production effort
for the people building the templates,
but it makes it fairly easy to get along
with interface elements, which are not plain text.
(i.e. images)
on the velocity side you could go with
a superclass, which figures out the locale and
offers the right template for each request.
these get cached anyway.
i am a little afraid that the way you described,
or the use of resources bundles might put to much
load on the machines, especialy when you have really
complex pages.
regards,
heiko
On Wed, 15 Aug 2001, Emile Kok wrote:
> Hi guys,
>
> I'd suggest having a set of global IDs (with matching descriptions) for
> languages. Use those IDs in a child table (item_translate or something)
> along with the item ID as the composite PK and join this [translate] table
> to the item table on item ID for each query. This obviously means fiddling
> with the object constructor classes.
>
> PS I have not tried this in Turbine, but use this principle on other systems.
>
> regards
> Emile
>
> At 07:36 PM 8/15/01 +0100, Heiko Braun wrote:
>
> >hi albi,
> >
> >i am currently on a project with similar requirements
> >and it would help a lot, if you could offer some hints
> >on using the build in Localisation.
> >
> >regards,
> >
> > --
> > heiko braun, fork unstable media
> > http://www.unstablemedia.com
> >
> >
> >On Wed, 15 Aug 2001, Albrecht F. Leiprecht wrote:
> >
> > > > Does anyone have any good tips or tricks on how to implement turbine
> > > > applications that have to display their web pages in multiple languages?
> > > > I have a requirement to build a simple application that can display its
> > > > interface in Dutch (ugh! =;o) ) or English, and I'm sure somebody out
> > > > there must have run into similar problems and has already come up with a
> > > > nifty solution.
> > >
> > > We are currently working on a site with multilanguage support, where we use
> > > Turbine's built in Localization service.
> > >
> > > We are currently using german and english based on the browserlanguage...
> > >
> > > is it that what you need ?? If so, I will try to guide you. It's quite easy
> > > :)
> > >
> > > rgds
> > > albi
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
