forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [issues] New comment: (FOR-18) support mulitple languages
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: Konstantin Piroumian
    Created: Mon, 20 Jan 2003 3:10 AM
       Body:
Absolutely agree with Steven.

For multilingual content its possible to use locale-sensitive sitemap aggregation, so the
body part of the document could be in the selected language.

I've been thinking about either a i18n protocol or an input module to be used to detect if
a file exists for the given locale using the same scheme as used to retrieve the message catalogues,
e.g.:
Given
  locale - en_US
  requested - index[.xml]
Result
  index_en_US.xml, if not found then
  index_en.xml, if not found then
  index.xml, if not found then 404 error
or
  /en/US/index.xml
  /en/index.xml
  index.xml

something like this.

It'd be fine if we could invent some mechanism for this kind of things, e.g.:

  <map:generate src="i18n:file:/{1}" /> or better via an input module
  <map:generate src="{i18n:file/{1}}" /> - but this is not possible currently.

(You know, I have a trigger acting on 'i18n', 'multilingual' words etc. ;))
 
  
---------------------------------------------------------------------
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


Mime
View raw message