Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Wed, 21 Dec 2005 10:46:57 +1100
From: David Crossley <crossley@apache.org>
To: user@forrest.apache.org
Subject: Re: i18n and documentation
Message-ID: <20051220234657.GA23261@igg.indexgeo.com.au>
References: <43A846B5.6080908@greenjaguar.com> <43A84D25.4070906@apache.org>
 <43A84EF6.90006@greenjaguar.com> <43A852F6.20405@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43A852F6.20405@apache.org>
User-Agent: Mutt/1.4i

Ross Gardler wrote:
> Helena Edelson wrote:
> >i am also working on i18n stuff. when i figure it out,
> >i was thinking it might be help ful to write a how to.
> >everything so far seems
> >fractured in terms of the steps to take to implement.
> >there are many if then's and info is everywhere, from
> >docs to jira to cocoon docs..
> 
> Yes, your help in bringing it together into something coherent will be 
> *very* helpful. Most of the i18n stuff has been implemented by Cheche 
> who is still around on the dev lists, but rarely appears here on the 
> user list.
> 
> We need to improve i18n support in Forrest to make use of the new 
> locationmap stuff (one of the major improvements in the 0.8-dev work). 
> However, without a clear understanding of how the current i18n works 
> this is very difficult. even a rough outline of what you know so far 
> would be very useful to both users and devs. Don't worry about it being 
> complete a start is what is needed.

Helena, please ask questions on the mailing list
rather than via the issue tracker. Here are some
notes that might help you ...

Yes, use one catalogue file per language.

The map:serialise is an empty element. The patch
that you looked at was old and has a syntax error
with an extra closing tag for a map:generator.
It has already been applied and has some subsequent
changes which were done prior to 0.7 release.

Anyway you should not need to look at the guts
of Forrest just to use i18n.

Remember that we only maintain the "pelt" skin.
So for the i18n of menus, it might only work for
pelt. The i18n of content should be independent
of the skin.

See the notes in forrest.properties about i18n.

See a 'forrest seed site'.

See Cheche's blog entry. Google: i18n forrest
Beware, some changes have been made since he wrote.

There is some recent discussion about i18n in
the forrest-dev mailing archives. Guess about
three months ago. I tried to explain the processing
to Gav and we fixed a bug which produced invalid
html output (only fixed in trunk at svn r263870
and r264136). The i18n still worked.

Yes we do need to bring it all together
in the forrest docs.

-David