You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@forrest.apache.org by is...@cocoondev.org on 2003/01/18 13:26:16 UTC

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

The following comment has been added to this issue:

Author: Jeff Turner
Created: Sat, 18 Jan 2003 6:26 AM
Body:
I think you could implement this Cocoon's XInclude transformer (http://xml.apache.org/cocoon/userdocs/transformers/xinclude-transformer.html), which allows

So index.en.html would have:

<html>
<body>

<xi:include href="index-layout.xml"/>
Blimey, .en content.
</body>
</html>

The Cocoon caching system will handle 'dependencies'. Eg, if index-layout.xml changes, then the next request for index.en.html will include those changes.

With the xpointer() scheme, the XInclude would be able to address specific nodes in a sitedefs file. A bit horrible though.. there was a long thread on how best to do a 'sitedefs' file in Forrest:

http://marc.theaimsgroup.com/?l=forrest-dev&m=104099654113176&w=2

Any real-life examples you could provide would be interesting.

--Jeff

---------------------------------------------------------------------
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: Sat, 11 Jan 2003 2:27 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