[ http://issues.apache.org/jira/browse/FOR-18?page=all ]
Juan Jose Pablos closed FOR-18:
-------------------------------
Fix Version: 0.7-dev
Resolution: Fixed
Close this issue as forrest has i18n support. most of the information reflected
here is not longer to do with the resolution of this issue.
> support multiple languages (i18n)
> ---------------------------------
>
> Key: FOR-18
> URL: http://issues.apache.org/jira/browse/FOR-18
> Project: Forrest
> Type: New Feature
> Components: Core operations
> Reporter: Ralf Hauser
> Assignee: Juan Jose Pablos
> Priority: Critical
> Fix For: 0.7-dev
> Attachments: multLang.zip
>
> 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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
