Hello,

This is a message to everyone working on or committing .po files in the
repository.

Now you have to check that unit tests pass on your .po files before
committing them.

Since we recently have an automated i18n coverage report
http://www.cps-project.org/sections/development/i18n
you cannot simply modify strings in .po files. You have to check that
your additions or modifications don't break the quality of the CPS
.po files.

Also to the nice translation contributors: please make sure that you are
improving the latest versions of the .po files. Don't base your work on
old .po files (that is for example more than 1 week old). The latest
version of .po can always be found at
http://svn.nuxeo.org/trac/pub/browser/

And if someone want to contribute a new language, please ask a CPS
developer to create .po files for you that you will then be able to
improve.

Thanks for your attention,

--
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

Reply via email to