[Zope-Coders] Proposal: put i18n into 2.6

[Casey Duncan]

Since there is now a 2.6 branch, 2.7 will soon become the HEAD I think, u=
nless=20
things move very quickly. The idea is that not everyone can/will move to=20
Python 2.2.x right now, so 2.6 allows us to continue to support Python 2.=
1.x.

I guess the ideal would be for 2.7 to just support Python2.2 and 2.1, but=
 that=20
would create its own headaches...

I agree that the branching situation is less then ideal, but 2.5.2b1 will=
 be=20
coming out along with (or before) 2.6b1, and I believe once 2.5.2 final i=
s=20
out, backporting to 2.5 not be done very much.

Yes, that still leaves the HEAD, 2.6 branch and (eventually) 2.7 release=20
branch 8^/

-Casey

On Friday 13 September 2002 09:50 am, Andreas Jung wrote:
> I am becoming angry to hear that 2.6 and 2.7 will come out close togeth=
er
> 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.
>=20
> Andreas
>=20
> ----- 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
>=20
>=20
> 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 i=
18n
> comes from Zope 3, it requires Python2.2.
>=20
> Jim's idea is that 2.7 will not differ much feature-wise from 2.6, exce=
pt
> for
> a couple of things backported from Zope 3 (tal i18n being one of them).=
 The
> major difference will be the Python version supported.
>=20
> 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.
>=20
> At the very least the time between 2.6 and 2.7 will be *much* less then=
 from
> 2.5 to 2.6.
>=20
> -Casey
>=20
> 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 int=
o
> > 2.6 right now (before the 2.6 beta), with the following changes:
> >
> >  - do not provide any translation service by default and leave that t=
o
> >    third party products for now,
> >
> >  - provide a very simple framework (=E0 la a simple
> >    registerTranslationService) for third party products to plug in th=
eir
> >    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 i1=
8n
> >    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
> >
>=20
>=20
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders@zope.org
> http://lists.zope.org/mailman/listinfo/zope-coders
>=20
>=20