Return-Path: 
 <forrest-dev-return-6751-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 48305 invoked by uid 500); 25 Aug 2003 10:15:55 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 48291 invoked from network); 25 Aug 2003 10:15:54 -0000
Received: from grunt24.ihug.com.au (203.109.249.144)
  by daedalus.apache.org with SMTP; 25 Aug 2003 10:15:54 -0000
Received: from p183-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.140.183]
	by grunt24.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 19rEO5-00039b-00; Mon, 25 Aug 2003 20:15:50 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 19rEOS-0000Yw-00
	for <forrest-dev@xml.apache.org>; Mon, 25 Aug 2003 20:16:12 +1000
Date: Mon, 25 Aug 2003 20:16:12 +1000
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: Multilanguage sites
Message-ID: <20030825101612.GA346@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <3F436AAA.3090108@savatech.ro>
 <20030823142305.GC2615@expresso.localdomain> <3F49D08D.2090903@savatech.ro>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F49D08D.2090903@savatech.ro>
User-Agent: Mutt/1.5.4i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Mon, Aug 25, 2003 at 12:02:05PM +0300, Corneanu Dan wrote:
> Jeff Turner wrote:
> 
> >How about having separate directories for each language?
> >
> >src/documentation/content/xdocs/en/*.xml
> >src/documentation/content/xdocs/de/*.xml
> >src/documentation/content/xdocs/fr/*.xml
> >...
> > 
> >
> This is a good idea. There is only one thing bothering me and this is 
> having multiple site.xml + tabs.xml files, one in every language folder 
> (src/documentation/content/xdocs/{en|de|fr}/site.xml etc.), all having 
> the same content only some labels being translated. But I think this 
> could be solved by an ant script that will prepare the 
> {en|de|fr}/site.xml + {en|de|fr}/tabs.xml files for every language using 
> a single site.xml + tabs.xml as source (endorsed with some translation 
> information), before actually running forrest.

Instead of having multiple site.xml's, you could have one with multiple
labels:

<site>
  <index href="index.html">
    <label xml:lang="en">Index</label>
    <label xml:lang="fr">l'index</label>
    ...
  </index>

Anything is possible with some XSLT and sitemap hacking.  For example,
RDF:

<rdf:RDF
  xml:base=""
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://apache.org/forrest/metadata/1.0#"
  xmlns:dc="http://purl.org/dc/elements/1.1/#">

  <folder rdf:ID="/" about=".">
    <file rdf:ID="index"
      dc:Source="index.xml"
      dc:Description="Forrest home page"
      dc:Creator="Various"
      dc:Format="text/xml"
      href="index.html">
      <dc:Title>
        <rdf:Alt>
          <rdf:li xml:lang="en">Index</rdf:li>
          <rdf:li xml:lang="de">Das Index :)</rdf:li>
        </rdf:Alt>
      </dc:Title>
    </file>
  </folder>
</rdf:RDF>


--Jeff

> 
> I will try the solution you proposed and see how it feels.
> 
> Also in the meantime I managed to put up a solution
> based on the structure I first proposed and I'm thinking of using the 
> i18n module for menus and tabs translation.
> 
> Dan.
>