On Sat, 2005-04-06 at 23:49 +0200, Thorsten Scherler wrote:
> On Sat, 2005-06-04 at 21:36 +0100, Ross Gardler wrote:
> > Pedro I. Sanchez wrote:
> > > On Sat, 2005-04-06 at 06:06 +0200, Thorsten Scherler (JIRA) wrote:
> > > 
> > >>    [ 
> > >> http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12312612
> > >>  ] 
> > >>
> > >>Thorsten Scherler commented on FOR-506:
> > >>---------------------------------------
> > >>
> > 
> > ...
> > 
> > >>So what we need is that 
> > >>1) we surround all captions with <i18n:text /> tags
> > >>2) add this keys to the catalogue
> > > 
> > > 
> > > Where is the catalogue where I need to add the keys/values to?
> > 
> > They are attached to the issue in the patch that Thorsten uploaded.
> > 
> > Ross
> 
> In revision 180026 I added (I applied the patch to trunk):
> main/webapp/skins/common/messages/CommonMessages_es.xml
> main/webapp/skins/common/messages/CommonMessages_de.xml
> main/webapp/skins/common/messages/CommonMessages_us.xml
> 
> That are the catalogues.
> 
> I guess the work should start in creating one master 
> main/webapp/skins/common/messages/CommonMessages_us.xml
> and add all skin keys to it. Then
> cp main/webapp/skins/common/messages/CommonMessages_us.xml
> main/webapp/skins/common/messages/CommonMessages_{language_country_variant}.xml
> 
> and translate the keys.
> 
> HTH
> 
> salu2

My version of the Spanish messages would be the following:

<catalogue>
  <message key="Font size:">Tamaño del texto:</message>
  <message key="Last Published:">Fecha de publicación:</message>
  <message key="Search">Buscar</message>
  <message key="Search the site with">Buscar en</message>
</catalogue>

Now, how do i specify the desired language? The i18n doc talks about
specifying the locale in the transform, I guess in a map file. Ideally
it should be specified forrest.properties, or even better at the command
line, like:

$ LANG=de_DE forrest

How is it done now?

One other comment: You are placing the catalogues under common/messages,
which is probably fine for the default skin. But I believe that skins
should come with their own catalogues because each can have an entirely
different set of labels to be translated. Is this being accommodated by
the skins "plugin" thing?

-- 
Pedro
 


There's a couple of things

Reply via email to