Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3F3AA5BA.401@anyware-tech.com>
Date: Wed, 13 Aug 2003 22:55:22 +0200
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Official i18n namespace (was Re: I18nTransformer : differences
 between
 2.1 and 2.0)
References: <3F3A6416.40405@anyware-tech.com>
 <1060792655.14866.232.camel@yum.ot> <3F3A6C58.1030708@anyware-tech.com>
In-Reply-To: <3F3A6C58.1030708@anyware-tech.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sylvain Wallez wrote:

> Bruno Dumon wrote:
>
>> On Wed, 2003-08-13 at 18:15, Sylvain Wallez wrote:
>>  
>>
>>> Hi mates,
>>>
>>> I'm currently porting an i18nized application from 2.0 to 2.1 and 
>>> hit an incompatible change due to the namespace change between the 
>>> two versions.
>>>
>>> Browsing the docs, I can't see any change in the i18n markup. The 
>>> changes seem only to be in the component's configuration which now 
>>> accept several catalogues.
>>>
>>> Did I miss some other important changes (I mean incompatible ones) ?
>>>   
>>
>>
>> We had this discussion some time ago, and nobody seemed to remember 
>> why it changed, but it changed.
>>
>> There have been features added but I don't know if (and don't think 
>> that) compatibility of existing features was broken.
>>  
>>
>>> If not, why doesn't this transformer accept a "legacy" mode with the 
>>> old namespace and configuration ? This would allow for immediate 
>>> back compatibility.
>>
>>
>> Seems ok to me. If we tried this before the 2.1 release I would even 
>> have been in favor of dropping the 2.1 namespace alltogether, but now 
>> it's a bit too late for that.
>
>
> Yep, too late. Too bad :-(
>
>> BTW, the old sitemap configuration (before multi-catalogue support) 
>> is still supported.
>>
>
> I just finished "legacy" support in the I18nTransformer, and the old 
> application seems to run just fine.


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 ?

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