[Nuxeo-localizer] [Fwd: [Plone-i18n] Important: i18n status]

[Myroslav Opyr]

 Hi,

Just forward to clarify what is going on in Plone.

m.
-------- Original Message --------
Subject: [Plone-i18n] Important: i18n status
Date: Sun, 8 Sep 2002 04:47:17 +0200
From: Alexander Limi <address@hidden>
To: <address@hidden>
CC: <address@hidden>



Hi,

Did the major check-in of the i18n-id-branch tonight. There are some key points
that should be noted:

- Do not start translating anything just yet. I need lalo's script to build the
master language file that you should all base your translations on. This is
important, we need this to be extremely organized and coordinated in the
beginning here, or else this will end up being a mess.

* The new i18n structure will break the existing translation files. I am very
sorry for this, but we *have* to do it unless we want to continue with sub-par
translations. You can re-use your message strings, so your work has not been
wasted - and it is better to do this now than in two months ;)

* DO NOT check out the existing Plone CVS if you are dependant upon a
translation file right now. (As the only translation being almost 100% was the
portuguese one anyway, I hope this isn't a big problem)

That's the bad news. The good news is that everything is converted to the new
format, the merge was relatively easy, although it took 20 hours to manually
add all the new stuff. But now we're ready for the glorious multi-lingual
future.

As far as I know, no application in the world have the features to match what
we are currently getting in Plone. The i18n ZPT namespace is *extremely*
elegant and flexible, and I would like to give a big thank-you to all the
contributors, both the authors of the original specification, and also the
Brazilian team for their AltTAL implementation.

AltTAL has enabled us to start on a working implementation right away (actually
it caught me totally by surprise, therefore the current situation where we have
to do a clean break with the past), and we are in the extremely advantageous
situation of actually having a stable, clean and working translation framework
ready for when Zope 2.7 will officially support it.

To summarize, what will happen next is this:

* I get the script from lalo to build an initial message catalog from the
source files of Plone
* I check this file for error/inconsistencies done during the previous i18n
branch
* I run the file as an english translation and load all pages to see if any
translations are missing my using the .missing option of AltTAL (this will also
catch variable names that can be translated safely in the interface, like item
type names etc)
* I put the master catalog up for download on plone.org, and will
simultaneously send out a message to the main Zope lists to call for
translators.

Lastly, I have started on a i18n Guidelines document, I want you to read it and
add your comments at the bottom (you need to be logged in). Please to not edit
the actual document yet, it is not finished. I need suggestions, surely there
are a lot more things that should be done to get the best quality translations
possible:

http://plone.org/documentation/InternationalizationGuidelines

I'm looking forward to start on the Norwegian translation of Plone :)


-- Alexander Limi
  http://limi.net
_______________________________________________
Plone-i18n mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/plone-i18n

--
Myroslav Opyr
zope.net.ua <http://zope.net.ua/> ° Ukrainian Zope Hosting
e-mail: address@hidden <mailto:address@hidden>