[issues] Updated: (FOR-18) support mulitple languages

[is...@cocoondev.org]

The following issue has been updated:

    Updater: Ralf Hauser (mailto:hauser@acm.org)
       Date: Mon, 20 Jan 2003 8:12 AM
    Comment:
index.xml adapted for en (and in a few minutes, it could provide a "de" version as well if needed).
The "include: doesn't work so far despite having extended my sitemap.xmap with <map:transformer name="xinclude"   src="org.apache.cocoon.transformation.XIncludeTransformer"/>

For setting my variables, I used the velocity syntax - I understand that this is not cocoon-compliant, but I am sure an equivalent syntax for cocoon exists...
    Changes:
[Attachment] [multLang.zip] was added

---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-18&page=history

---------------------------------------------------------------------
View the issue:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-18


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

   Assignee: 
   Reporter: Ralf Hauser

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

Description:
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 sitedef.de, ... 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?


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org/jira//Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira