I think there is no need to try to tell that (2) is a better choice in most
of cases. (1) may be better only in the case when amount of locale-dependent
content is very small.
> 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.
fedor.
_______________________________________________________
Tired of slow Internet? Get @Home Broadband Internet
http://www.home.com/xinbox/signup.html
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
