You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by 9902468 <vi...@cerion.fi> on 2008/09/18 10:40:53 UTC
[T5] Component library common I18N file
Hi,
We have a component library that could really benefit from common library
wide properties file, that would contain all messages that are common to all
(or many) components.
Can this be done? (I hope that I'm just temporarily blind and cannot see the
solution. :) )
- 99
--
View this message in context: http://www.nabble.com/-T5--Component-library-common-I18N-file-tp19548497p19548497.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [T5] Component library common I18N file
Posted by "Filip S. Adamsen" <fs...@fsadev.com>.
Hi,
You want to use an Application Message Catalog:
http://tapestry.apache.org/tapestry5/guide/localization.html
-Filip
Neeme Praks wrote ..
> I'm not sure if it is the same, but I'm also interested if there is a
> way to centralize ALL i18n strings into a single messages file. By ALL
> i18n strings I mean all texts from components, pages and layouts combined.
>
> So when I need to add a new language to my T5-based webapp, I can take
> that one file, give it to translators, add translated file to my webapp
> and - voila, it works! Maybe that is already now possible and I have
> just overlooked something?
>
> Rgds,
> Neeme
Re: [T5] Component library common I18N file
Posted by Neeme Praks <ne...@apache.org>.
I'm not sure if it is the same, but I'm also interested if there is a
way to centralize ALL i18n strings into a single messages file. By ALL
i18n strings I mean all texts from components, pages and layouts combined.
So when I need to add a new language to my T5-based webapp, I can take
that one file, give it to translators, add translated file to my webapp
and - voila, it works! Maybe that is already now possible and I have
just overlooked something?
Rgds,
Neeme
9902468 wrote:
> Hi,
>
> We have a component library that could really benefit from common library
> wide properties file, that would contain all messages that are common to all
> (or many) components.
>
> Can this be done? (I hope that I'm just temporarily blind and cannot see the
> solution. :) )
>
> - 99
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org