Return-Path: 
 <dev-return-24207-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-dev-archive@www.apache.org
Received: (qmail 54183 invoked from network); 19 May 2006 02:40:40 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 19 May 2006 02:40:40 -0000
Received: (qmail 18175 invoked by uid 500); 19 May 2006 02:40:39 -0000
Delivered-To: apmail-forrest-dev-archive@forrest.apache.org
Received: (qmail 17996 invoked by uid 500); 19 May 2006 02:40:38 -0000
Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@forrest.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@forrest.apache.org>
List-Post: <mailto:dev@forrest.apache.org>
Reply-To: dev@forrest.apache.org
List-Id: <dev.forrest.apache.org>
Delivered-To: mailing list dev@forrest.apache.org
Received: (qmail 17980 invoked by uid 99); 19 May 2006 02:40:38 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 May 2006 19:40:38 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 May 2006 19:40:37 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 300A27142AE
	for <dev@forrest.apache.org>; Fri, 19 May 2006 02:40:06 +0000 (GMT)
Message-ID: <21734877.1148006406173.JavaMail.jira@brutus>
Date: Fri, 19 May 2006 02:40:06 +0000 (GMT+00:00)
From: "Brian Dube (JIRA)" <jira@apache.org>
To: dev@forrest.apache.org
Subject: [jira] Commented: (FOR-883) i18n broken: perhaps locationmap
In-Reply-To: <28308763.1148000047682.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

    [ 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