forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juan Jose Pablos <che...@apache.org>
Subject Re: [jira] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
Date Wed, 01 Jun 2005 10:02:58 GMT
Pedro I. Sanchez wrote:
> 
> Anyway, first I verified that setting value="es_ES" in
> main/webapp/sitemap.xmap indeed works. It brings the Spanish strings
> from the right catalogue. I also verified that value="${env.LANG}" does
> *not* work.
> 

are you sure that the $LANG property is set on your system?
if not do an "export LANG=es_ES"

do an echo $LANG before running "forrest site" to verify that the change 
has been made.

> 
> 1) First change
> 
> -#project.i18n=true
> +project.i18n=true
> +project.language=es_ES
> 
> And this alone works just well. The site is generated under
> build/site/es_ES but with English labels. The next step is
> required to get the translations in place.

The i18naction does not know anything about project.language that is why 
  it does not translate


> 
> 2) Second change: Reflecting these changes in the sitemap

> Unfortunately these gives me a null pointer and dies :( But there's tons
> of {project:xxxx} strings used everywhere in the site map! So, what's
> missing to make my newly created "language" property to work?
> forrest.build.xml likes it but sitemap.xmap doesn't.
> 

Well you change the new stuff about a skin i18n aware. There is more 
stuff that needs to change. Still, I think that the main issue that you 
have is that forrest does not get you env.LANG property.

I have change that so it uses {user.language} instead. try to "svn up" 
and report if that is working for you.


Cheers,
cheche

Mime
View raw message