on 12/5/2000 11:02 AM, "Andre Schild" <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> what is the recommended way to localize velocity screens & templates ?
> 
> As possible options I see the following:
> 
> 1. Put Localization.getString calls in the vm templates, so we can use the
> same vm files for all languages
> 2. In the setTemplate use Localization.getString to map to vm-screens with
> different names
> 
> Has anyone experiences what works "best" for velocity ?
> 
> Andre.

Problem is that there isn't a "best" solution yet.

You have some issues:

#1. Will your localization affect your layout? ie: Japanese layout is going
to look at lot different than English.
#2. What content are you trying to localize? Database or just static content
in the page.

If #1 is true and #2 is static content, then the right way to do it would be
to have different template files for each locale and then name them
according to the Java i8n rules. Then you can write a TemplateLoader that
would pay attention to that.

I guess what I'm trying to say is that there is no right way and we also
haven't completed this code in Velocity yet. Welcome to bleeding edge. I
hope you contribute your solutions back to us. :-)

thanks,

-jon



------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to