Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 98215 invoked from network); 4 Sep 2003 10:33:06 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Sep 2003 10:33:06 -0000 Received: (qmail 57479 invoked by uid 500); 4 Sep 2003 10:33:02 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 57409 invoked by uid 500); 4 Sep 2003 10:33:00 -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 57389 invoked from network); 4 Sep 2003 10:33:00 -0000 Received: from unknown (HELO office.oilspace.com) (213.219.58.70) by daedalus.apache.org with SMTP; 4 Sep 2003 10:33:00 -0000 Received: from kpiroumian (ns.informtek.com.ru [195.239.59.130]) by office.oilspace.com (Postfix) with SMTP id 7C4386D37C for ; Thu, 4 Sep 2003 11:29:47 +0100 (BST) Message-ID: <006001c372cf$95cb47f0$d767a8c0@kpiroumian> From: "Konstantin Piroumian" To: References: <20030831084524.GA1497@dotsphinx.dyndns.org> <3F568619.8070301@che-che.com> <3F56F6BA.5000303@dotsphinx.com> Subject: Re: Multi-lingual static web site Date: Thu, 4 Sep 2003 14:30:38 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N From: "Raymond Penners" > Juan Jose Pablos wrote: > > >> I have searched the mailinglist archives and found some references to > >> the Cocoon i18n translator. What I couldn't find was how to integrate > >> this with a clean out-of-the-box Forrest installation? > > > > > > I18n is to translate a Translate this within a xml > > document. It would be added possibly after 0.5 release, but I think > > that is not what are you looking for. > > > The i18n translator approach to translate bits of text from XML > documents would suffice for now. I understand that there are other > options, like translating documents as a a whole. Yes, i18n transformer is fine for menus, titles, navbars, etc., but not for documents. Though, it's possible to use it for document translation, e.g. by paragraph:

. Just ask if you need more details on how to use it. > > Still, is the i18n translator approach something that can already be > made to work with the current version of Forrest, e.g. by tweaking some > XML files. Or, is this future functionality? > > I have tried using some i18n tags but that did not seem to work. I am > also wondering how Forrest would be able to generate a static site using > this approach. For example, how does it know that it has to generate > document.en.html and document.nl.html, given document.xml ? You should modify the pipelines that generate contents for menus and add something like: you should specify the locale to use. For that you can use URLs like /en/index.html and modify the matcher to extract the locale part and pass it to the i18n trasformer. Not sure if it's possible to use request parameters for static site generation. Also, you should make sure that i18n transformer component is defined. Seems that this requires quite good knowledge of Cocoon. -- Konstantin > > Thanks, > > -- > Raymond Penners -*- raymond@dotsphinx.com -*- www.dotsphinx.com > > >