Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 56378 invoked by uid 500); 18 Jan 2003 13:47:19 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 56363 invoked from network); 18 Jan 2003 13:47:19 -0000 Received: from cocoondev.org (209.15.201.32) by daedalus.apache.org with SMTP; 18 Jan 2003 13:47:19 -0000 Received: (qmail 21663 invoked from network); 18 Jan 2003 13:47:20 -0000 Received: from unknown (HELO cocoondev.org) (jira?admin@127.0.0.1) by cocoondev.org with SMTP; 18 Jan 2003 13:47:20 -0000 Message-ID: <22633901.1042897640869.JavaMail.jira_admin@cocoondev.org> From: issues@cocoondev.org To: forrest-dev@xml.apache.org Subject: [issues] New comment: (FOR-18) support mulitple languages Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N The following comment has been added to this issue: Author: Konstantin Piroumian Created: Sat, 18 Jan 2003 7:47 AM Body: It's possible to use i18n transformer (from Cocoon 2.1-dev) to generate all the menu labels and other navigation/site parts using multilingual dictionaries. As for the content of the documents it's possble to use either XInclude/CInclude capabilities to include content in the needed language or use latest i18n markup extensions: English content Русское содержание {Some other content} Also, it's possible to use LocaleAction (or better an input module) to obtain locale information in the sitemap and aggregate document's contents based on the selected locale. --------------------------------------------------------------------- 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