[ http://issues.apache.org/jira/browse/FOR-883?page=comments#action_12412466 ] 

Brian Dube commented on FOR-883:
--------------------------------

Around line 64 in $FORREST_HOME/main/webapp/tabs.xmap is this:

<map:transform src="{lm:transform.i18n}"/>

In $FORREST_HOME/main/webapp/locationmap-i18n.xml this is resolved as:

<match pattern="transform.i18n">
  <location src="{forrest:stylesheets}/i18n.xsl" />
</match>

The stylesheet i18n.xsl does not appear to exist. Commenting out the transformation in tabs.xmap allows the site to render dynamically as well as build statically. Does it fix i18n? I don't know.

> i18n broken: perhaps locationmap
> --------------------------------
>
>          Key: FOR-883
>          URL: http://issues.apache.org/jira/browse/FOR-883
>      Project: Forrest
>         Type: Bug

>   Components: Internationalisation (i18n), Locationmap
>     Versions: 0.8-dev
>     Reporter: David Crossley
>     Priority: Critical
>      Fix For: 0.8-dev

>
> http://marc.theaimsgroup.com/?l=forrest-dev&m=114796698827112
> Message-ID: f767f0600605180842y3720649ag779d9065fcee7524 () mail ! gmail ! com
> Bertrand Delacretaz wrote:
> > David Crossley wrote:
> >
> > >...I gave a general reply on the user list.
> > >http://article.gmane.org/gmane.text.xml.forrest.user/3620..
> >
> > Thanks! I've read it all now.
> >
> > The i18n support seems to work indeed in V0.7, but it's not currently
> > working for me in trunk.
> >
> > Failure scenario:
> > svn up
> > build clean, rebuild
> > run "forrest seed" in an empty directory
> > set project.i18n=true in forrest.properties
> > forrest run
> > request http://localhost:8888/index.html
> >
> > At this point I get an error saying "(my forrest_home)/main/webapp (No
> > such file or directory)". If I switch off project.i18n everything's
> > fine.
> >
> > I have to run now, will have a closer look tomorrow, but if someone
> > could test this and confirm Id' appreciate it.
> >
> > -Bertrand

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira