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: Steven Noels
    Created: Sat, 18 Jan 2003 8:14 AM
We had this discussion before, and in other places as well. Adding i18n on navigation labels
would be interesting, if supported by the site.xml scheme (an argument to switch to name/value
pairs IMHO).

i18n content is something different however. I believe multilingual versions shouldn't be
handled inside one document, for a number of reasons:

* it is confusing to the document editor
* there's a good chance not everything is translated in very language
* typically, the verbosity between language variants can be different

so I would be +1 on navigation i18n, as we did for xreporter too, but not for document content:
different languages will reside in parallel URI spaces and should be edited accordingly (i.e.

All IMHO, of course. Konstantin is our i18n master.
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: Sat, 11 Jan 2003 2:27 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