The following comment has been added to this issue:
Author: Juan Jose Pablos
Created: Tue, 22 Feb 2005 6:02 PM
Body:
I have commit the adaptation with org.apache.cocoon.matching.LocaleMatcher.
but this adaptation requiered to use index.lang.xml instead of index_lang.xml
---------------------------------------------------------------------
View this comment:
http://issues.cocoondev.org//browse/FOR-18?page=comments#action_12079
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org//browse/FOR-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-18
Summary: support multiple languages (i18n)
Type: New Feature
Status: Open
Priority: Critical
Project: Forrest
Components:
Core operations
Assignee: Juan Jose Pablos
Reporter: Ralf Hauser
Created: Sat, 11 Jan 2003 2:27 AM
Updated: Tue, 22 Feb 2005 6:02 PM
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//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
