M.-A. DARCHE a �crit :
A new version of the update_pos script is available in the CPSI18n
product.
From the CHANGES file, one reads:
New features:
~~~~~~~~~~~~~
- Made the update_pos replace fuzzy translations from po files with
those of the
reference translations (which presently are en and fr). This will both
provide
always correct translations for CPS sites, as well as ease the work of
translator contributors who will only have to update fuzzy
translations with a
translation from their language.
Bug fixes:
~~~~~~~~~~
- Made the update_pos script more user-friendly with updated help messages.
I'm planning to use this new update_pos file on the CPS products that
will be shipped with the CPS 3.3.3 release.
But before doing so I would like some people to test this script on
their own instance and have some reports. I'm especially thinling about
Benoit for this job ;-) since he has strong and good views about how
the i18n process should work: Benoit, can you have a try on it please?
The new update_pos has nicely been reviewed by Anahide, Benoit and
Jean-Marc.
I have fixed the points raised by them, so consider update_pos
to be now stable.
Every CPS developer must use update_pos to add new translations to a
product, even for client products. Modifying translations in final
.po files can indifferently be done with high-level tools such as
KBabel or with low-level tools such as VIM.
Now that update_pos has a nice help message and is easy to use, there is
no excuse not to use it.
All the CPS products which have i18n have been their .po files modified
with the new update_pos. Only CPSSkins has not been processed yet due
to problems on some CPSSkins .po files. I'll check that with Jean-Marc.
Cheers,
--
Marc-Aur�le DARCHE
NUXEO (Paris, France) http://nuxeo.com
Nuxeo Collaborative Portal Server http://www.nuxeo.com/cps
Gestion de contenu web / portail collaboratif / groupware / open source
_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel
