Translation setup for plone
schlichting at bakb.net
Wed Aug 31 18:28:47 CDT 2005
Jordi Mallach wrote:
> Hi Hanno,
> I'm sorry about the lack of notice. For some reason I thought the
> requester was a member of the Plone project so this was ok with you
No problem at all. This way I just have to become acquainted with
Rosetta a bit earlier ;)
> Ok, the product is now yours.
> Again, as you prefer: you could use the big po in Rosetta and just have
> one pot file imported, or you could have it split. Another question is
> how you want to manage the different plone modules. Right now, cmfplone
> is a product. I don't know if for example
> https://launchpad.net/products/shellex "belongs" to you guys, but if you
> have many like that one, you might want to create a "Plone project" and
> group all of your products there, as GNOME currently does:
Plone is in fact a project which consist of various products, for
example cmfplone, archetypes, etc. The distinction between Plone the
project and CMFPlone the product is already well established. Therefore
I kindly ask for naming the project 'plone' instead of the current
'cmfplone', which is only the technical name of one product Plone
consists of. The same name change would be appreciated for the
translators group as well.
Speaking of shellex this is only one of a myriad of Plone add-on
products. But we currently have one rather special group of add-on
products hosting their code in our so called 'collective', which is
mainly a SVN repository with shared write access aming a big bunch of
developers. For these products I would like to get a second project
called 'plone-collective' (sharing the plone translators group) so I can
take some of the burden of i18n management for these.
> Please, accept my apologies for jumping the gun like this. We surely
> don't want to force Rosetta on you guys!
> Right now, it's going to be up to your translators to switch to Rosetta
> or continue using their way, as only the people you appoint will be
> granted access to do official Plone translations through Rosetta. If
> some prefer using external tools, they can keep doing it, as far as
> Rosetta is concerned.
No one has to apologize here. This is the spirit of open source, making
things better! And we have to be thankful to be allowed to use such a
great service as Rosetta. *g*
>>So long and thanks for all of Rosetta ;)
> Thanks for managing Plone translations so well. I was quite amazed when
> I packed all the plone-* files and saw that tar.gz was nearly 4 megs.
It is insane, but for another reason, which is due to our current policy
of adding the context of a messages occurrence in the code to the
automatic-comments ('#.') of a message entry. This will be changed
shortly when I have updated our extraction utility ;)
>>P.S. What is this bug you are talking about? Something wrong on our side?
> Nope, probably something rough in the Rosetta side. The tarball got
> imported in the end.
> Oh, before I forget, in the process of uploading stuff, I made some
> changes to make your files digestible for Rosetta:
> I got rid of zh.po, which is identical to zh_CN. AFAIK, there are no
> "Chinese" translations, without a country suffix, because they are quite
> different between them, and I suspect in many cases zh_CN is not a valid
> fallback for zh_HK. The other Chinese files were renamed to the
> ll_CC format, ie zh-cn -> zh_CN. Likewise for pt-br.
> I renamed no.po to nb.po, which is the (not so) new code for Norwegian
> I renamed sr-Latn to sr at Latn.po.
> I got rid of en.po. Why is it in SVN?
Hhm. We are currently not following the ll_CC standard but use language
tags as definied by http://www.ietf.org/rfc/rfc3066.txt. As our i18n
management utils and the translation service doing the real translation
depends on these, changes won't work for us just now. Especially the
@-sign is not allowed and we depend on the naming as 'sr-Latn' according
to http://www.iana.org/assignments/language-tags. Getting rid of
plone-zh.po and the naming change of plone-no.po to plone-nb.po are fine
The file plone-en.po is vital, as not using locales right now we have
put day/week/monthname translations into the po files. As doing this
with literal msgids like 'msgid "May"' isn't working because of not
being able to distinguish the three-letter abbreviation of May and the
fullname, we had to use something like 'msgid "month_may_abbr"' which
needs an english translation of 'msgstr "May"' as definied in plone-en.po.
> I think that was about it. If there's no good reason for these issues (I
> could be missing some python-specific issue with po-files), I suggest
> you make those changes in yuor repos too.
I hope to have explained our reasons for the current layout but hope
these doesn't mean Plone is incompatible with Rosetta?
> Again, sorry for the late night surprise yesterday. I hope you'll find
> Rosetta productive.
I very much like pleasant surprises and this was definitly one of that
Thanks so much Jordi
More information about the rosetta-users