[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: general roadmap [was: Re: [Nuxeo-localizer] ZWiki internationalizati
From: |
Juan David Ibáñez Palomar |
Subject: |
Re: general roadmap [was: Re: [Nuxeo-localizer] ZWiki internationalization] |
Date: |
Mon, 25 Feb 2002 10:28:19 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020214 |
Hi Myroslav,
I agree with you. However this case is a bit different, because Simon is who
has written ZWiki. So there would be one and only one multilingual version
of ZWiki, the job would be done only once.
About Zope 3, there's already an effort to internationalize it:
http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/Zope3Internationalization
The project page was set up after a i18n "sprint" in the ZC
headquarters, where
Stephan (the creator of ZBabel) and myself attended as invitees.
Right now, there's few activity, I guess everybody is busy.
The problem is, what happens if you need or want your product to be
multilingual
now and can't wait for Zope 3? Then you've to choose a tool.
This raises another question, what will happen if you internationalize a
product
using Localizer now, and then Zope 3 is released?
First, I hope to release Localizer 1.0 before Zope 3.0 is released.
Second, even if
Zope 3.0 is multilingual, there will still be a Localizer product,
because it provides
services that Zope 3 won't provide. Finally, Localizer for Zope 3 will
maintain
full compatibility with Localizer 1.0 for a looong time, so you will be
able to move
your multilingual product from Zope 2 to Zope 3 without worrying about the
i18n stuff.
Regards,
PS: the message isn't redundant, these questions are very important and
concern
everybody working on i18n with Zope.
Myroslav Opyr wrote:
Juan David Ibáñez Palomar wrote:
Hi all, and specially to Simon, who is considering to use Localizer
to internationalize ZWiki.
Hi,
I'm erlativrly new to this maillist but some questions I'd like to
clear from the very beginning...
Modifications of .py code, which is partr of Zope or part of Products
involves extremely uneffective use of human resources.
I.1) Someone modifies .py code to make it i18nable.
I.2) Someone localizes messages.
II) Someone do the same because he urgently need localized product
III) Another one is localizing set of products because his company
want to have them for dispozal in close future.
In short time new version of product appeas ZWiki 1.0.
And those who need extra features of 1.0 are repeating i18n again.
Isn't it waste of resources. What is EuroZope opinion about this? If
Zope includes some generic interface to internationalization itself
then our life would become just simple. We should push it as a
component into their Component Architecture. i18n of Zope itself could
be done by ZC easily. And i18n contributions to Products (such as
ZWiki) would become a part of CVS really soon. Then everyone will
benefit from that efforts. If somone want to use ZBabel - let him do
that. If Localizer - excellent, but this should be transparent. And
thus I see contacting EuroZope and ZC really important. Sorry if all
this was proposed before and this message is redundant. Then I'd ask
you to give me some dirtections (URLs) to discussions regarding the
issue.
With best regards,
Myroslav
--
J. David Ib??ez, Nuxeo.com
Debian user (http://www.debian.org)