[Zope-Coders] Proposal: put i18n into 2.6

[Andreas Jung]

I am becoming angry to hear that 2.6 and 2.7 will come out close together
and that are only some differences between both versions. From the
maintenance point of view it is hard to keep an overview over
at for different code lines (2.5.X, 2.6, 2.7, HEAD). Fixing bugs
and backporting fixes to other branches will become more complex
and requires more time.  I would like to see the number of different
active branches as low as possible.

Andreas

----- Original Message -----
From: "Casey Duncan" <casey@zope.com>
To: "Florent Guillaume" <fg@nuxeo.com>; <zope-coders@zope.org>
Sent: Friday, September 13, 2002 6:35 AM
Subject: Re: [Zope-Coders] Proposal: put i18n into 2.6


I believe the plan is for 2.7 and 2.6 to come out very close together. 2.7
will require Python 2.2.x, whereas 2.6 still runs on 2.1.x. Since tal i18n
comes from Zope 3, it requires Python2.2.

Jim's idea is that 2.7 will not differ much feature-wise from 2.6, except
for
a couple of things backported from Zope 3 (tal i18n being one of them). The
major difference will be the Python version supported.

If this proves true, the effort to get tal i18n in Zope 2.6 wouldn't be
fruitful, unless you were bound to Python 2.1.x for some other reason.

At the very least the time between 2.6 and 2.7 will be *much* less then from
2.5 to 2.6.

-Casey

On Friday 13 September 2002 09:04 am, Florent Guillaume wrote:
> I'm aware that this probably is going to get shot down, but I feel it is
> important:
>
> I'd like to propose including the _current_ 2.7 TAL+ZPT i18n code into
> 2.6 right now (before the 2.6 beta), with the following changes:
>
>  - do not provide any translation service by default and leave that to
>    third party products for now,
>
>  - provide a very simple framework (à la a simple
>    registerTranslationService) for third party products to plug in their
>    translation service.
>
> The rationale for that proposal is:
>
>  - the code in 2.7 is functional enough (I'm using it in a manner
>    described above) and implements most of the spec,
>
>  - there is (and there has been for a long time) a _huge_ need for i18n
>    in core Zope, why wait when we have something that works,
>
>  - it doesn't impact people not using i18n tags at all,
>
>  - people using i18n tags but without an external translation service
>    wouldn't see any change from current 2.6.
>
> Risks:
>
>  - speed hit in the TAL code itself (negligible I believe)
>
>  - bugs in the current i18n code
>
> I'm volunteering to do the small code integration needed during the
> weekend on a branch off Zope-2_6-branch.
>
> Florent
> --
> Florent Guillaume, Nuxeo (Paris, France)
> +33 1 40 33 79 87  http://nuxeo.com  mailto:fg@nuxeo.com
>
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders@zope.org
> http://lists.zope.org/mailman/listinfo/zope-coders
>


_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://lists.zope.org/mailman/listinfo/zope-coders