Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 76931 invoked by uid 500); 14 Aug 2003 14:42:37 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 76880 invoked from network); 14 Aug 2003 14:42:36 -0000 Received: from smtp.hotbox.ru (80.68.244.50) by daedalus.apache.org with SMTP; 14 Aug 2003 14:42:36 -0000 Received: from kot (clusterfw.beelinegprs.ru [217.118.66.232]) (authenticated bits=0) by smtp.hotbox.ru (8.12.9/8.12.9) with ESMTP id h7EETBCe072750 for ; Thu, 14 Aug 2003 18:29:23 +0400 (MSD) (envelope-from kpiroumian@apache.org) Message-ID: <000601c36272$2b30fb50$f34513ac@kot> From: "Konstantin Piroumian" To: References: <3F3A6416.40405@anyware-tech.com> <1060792655.14866.232.camel@yum.ot> <3F3A6C58.1030708@anyware-tech.com> <3F3AA5BA.401@anyware-tech.com> <1060809542.14864.289.camel@yum.ot> <3F3AB19C.80809@gmx.de> <3F3B2CF8.5010004@anyware-tech.com> Subject: Re: Official i18n namespace (was Re: I18nTransformer : differences between 2.1 and 2.0) Date: Thu, 14 Aug 2003 18:40:42 +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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N My trigger on i18n was late this time as I am on vacation, but I'd like to explain why the namespace was changed. A quot from changes list: Extended implementation of i18n transformer to allow markup in translations, inline translations (conditional processing) and named parameters. Now i18n transformer is cachable, this will affect on dynamic markup, e.g. i18n:date-time. WARN: The namespace of i18n markup is changed to "http://apache.org/cocoon/i18n/2.1". i18n samples are updated to demonstrate the new features. (KP) Thanks to Matthieu Sozeau. Also, there are minor changes in syntax for number formatting in translation parameters (don't remember details). What is the most important thing is that 2.1 version is cached, while 2.0 is not. In any case, I am +1 for adding support for both namespaces. Another solution could be to add a stylesheet and an Ant target for migrating 2.0 to 2.1 markup. I should add that I am agree with all you decide, guys, cause it seems that you are more interested in i18n than I am ATM. Regards, Konstantin From: "Sylvain Wallez" > Joerg Heinicke wrote: > > Bruno Dumon wrote: > > > >>> This makes me think... > >>> > >>> What about reverting the "official" i18n namespace to ".../i18n/2.0" > >>> as it was before ? This would allow warning-less compatibility of > >>> 2.0 applications and avoid breaking lots of docs, books, articles, etc. > >>> > >>> Of course, we should provide "legacy" support for the "../i18n/2.1" > >>> namespace as it has been released (damn, wish I did this a few days > >>> before). > >>> > >>> What do you think ? > >> > >> > >> How about making them synonyms, i.e. giving them an equals status? > > > > > > +1 > > > Ok. This simply means removing the warning when encountering a "2.0" > namespace. > > >> The new namespace is already in Cocoon 2.1 for a very long time, and > >> I think many people started to depend on it. > > > > > > Sylvain does not want to remove 2.1 support, but only make 2.0 the > > official one. But even this is a bit strange to explain to users :-) > > > Makes sense. So let's just say that the official namespace is 2.1 but > that 2.0 compatibility is ensured. This should make everybody happy ;-) > > Sylvain > > -- > Sylvain Wallez Anyware Technologies > http://www.apache.org/~sylvain http://www.anyware-tech.com > { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } > Orixo, the opensource XML business alliance - http://www.orixo.com > > >