forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pedro I. Sanchez" <>
Subject Re: [jira] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
Date Fri, 10 Jun 2005 03:11:39 GMT
On Thu, 2005-09-06 at 12:56 +0200, Juan Jose Pablos wrote:
> Pedro I. Sanchez wrote:
> > The string $(env.LANG} works well inside main/ It was
> > the default before you made changes to the trunk. But the same string is
> > ignored when you use it inside webapp/sitemap.xmap (skin labels are
> > looked up in the English dictionary, even if LANG=es_ES).
> > 
> are you talking about tabs and menus or are you talking about "Last 
> Published:"
Last Published:

> > 
> > I don't believe what you did is right, sorry if I misunderstand :|
> > You replaced my 'project.language' with 'user.language' but you are not
> > defining 'user.language' in So it does nothing when I
> > use it in my site's ''.
> > 
> is using the default language for the JVM. In the case of the windows 
> machines, that will work much better. This change only affect the 
> creation of a directory base on the language..
> This way you can run "export LANG=en" "forrest site" "export LANG=es" 
> "forrest site"
> so diferent languages goes to diferent directories.
As I said that used to work before your changes; it doesn't work now for
me. You removed the reference to $(env.LANG} in favour of user.language
(which I believe is doing nothing).



With your changes:


> > 
> > 
> > So, let me rephrase my understanding of this issue so far. Before you
> > made changes to trunk this was the behaviour:
> > 
> > 1. Forrest seed; forrest would generate the static site in English,
> > regardless of your LANG env.
> > 
> sure. There is not implementation to seed a project with examples in 
> spanish..
> > 2. Setting project.i18n=true in and running forrest
> > again would generate your site in build/site/xx, where xx is determined
> > by the LANG env. BUT, the generated static site is still all in English;
> > no look up into the language-specific catalogues ever takes place.
> > 
> I can not reproduce this. "Forrest site" works for me.
Are you on Linux or Windows?
I don't understand. How can it work for you?
This line in sitemap.xmap is the one that determines the catalogue to
use and as you can see it is not connected at all with the LANG
environment variable.

<map:parameter name="locale" value="{request:locale}"/>

It is connected instead to the language selection of your browser which
doesn't help much with a static site.

> > My goal for a static site is to be able to issue the command
> > 
> > $ LANG=es_ES forrest
> > 
> have you try to issue "export LANG=es" ??????? I think that I told you 
> before.
It's the same. In both cases the execution environment has the variable
LANG set to the proper value. Anyhow, I tested using the "export" with
the same results.

Can you explain why you think 'user.language' does anything when it is
not defined in


View raw message