forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [issues] New comment: (FOR-18) support mulitple languages
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: Raymond Penners
    Created: Mon, 1 Sep 2003 2:40 PM
I am a Forrest novice, but would really like to use it for our web site (
For this purpose, Forrest would need to generate a static, multi-lingugal web site, that will
be served by Apache using content negotiation.

Is this currently possible? 

I found some references to the i18n:translator, but I could not find a proper example of how
to set this up.

View the issue:

Here is an overview of the issue:
        Key: FOR-18
    Summary: support mulitple languages
       Type: New Feature

     Status: Unassigned
   Priority: Critical

    Project: Forrest
  Component: None

   Reporter: Ralf Hauser

    Created: Sat, 11 Jan 2003 2:27 AM
    Updated: Mon, 20 Jan 2003 8:12 AM

In my current environment to develop static mulitlingual web-sites, I use an ant build.xml
and the m4 macro preprocessor to achieve the following (sample):
1) index.en.m4 gets converted to index.en.html
The *.en.m4 contains all language dependent text (similarly *.de.m4 for German) and includes
index.m4 that contains the page's content layout.
[(^\.)+].m4 includes sitedef.m4 where I define all global parts of the website (e.g. navigation
structure, unique content e.g. phone numbers, filenames, etc.). This in turn includes a sitedefs.en
or, ... respectively for global, language dependent definitions.
2) Dependencies 
a) upon change of [(^\.)+].m4, all depending *.*LANG*.html get rebuilt
b) upon change of sitedef.m4, build.xml, and alike all *.html gets rebuilt
c) upon change of sitedefs.en all *.en.html get rebuilt.

Obviously, I could use the exact same approach to create .xml whereever I created .html before,
but my long-term goal is to get rid of m4. Has anybody already put some thought into how this
would be done with forrest?

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message