[Plone-i18n] Re: Some minors in PasswordResetTool

[Hanno S. <pl...@ha...>]

Hi Jean-Paul, all :)

Jean-Paul Ladage wrote:
> Hi Hanno, all,
> 
> I took the liberty of recreating the pot files today. All products
> except cmfpw are succesfully updated.

Usually this would be really appreciated but the rebuilding of pot files
is slightly more complicated as it sounds. There are various
undocumented manual task to do, which I regularly do, but you couldn't
have known about. This goes from manually excluding certain files from
the 2.1 plone skins (the old edit forms for non-atct-based content
types), removing some stupid 'false positives' from pot files (like
msgid "archetypes") to rescuing translations for literal msgid's where
the original text has only been spell-fixed.

So while I appreciate your work, it would have been nice if you would
have asked me first to spare us some work ;)

> Also the po files are synced. So all translators please update your po
> files for the upcoming release 2.1.3

Now I resynced them again and they should be ready for consumption.

> Another thing that crossed my mind during the rebuilds is the fact that
> trunk of PloneTranslations now "supports" Plone 2.5 and 2.1.3 which in
> my opinion in not entirely true. 2.5 uses Archetypes 1.4 for example. If
> some msgids are removed in AT1.4, we would miss those in plone-2.1.3.
> 
> To prevent such issues I suggest to branch up PloneTranslations and sync
> the versioning with Plone. Are there any objection or other thoughts
> about this?

Well right now I cope with this manually by rebuilding the pot files
under both Plone versions and diffing them into one that is valid for
both versions.

So far there has been no real conflicts between both versions and as
long as this is the case, I would like to stick to the simple plan. My
reason here is, as already argued, that I do not want to make
translating Plone more difficult as it has to be. Subversion branches
are some added complexity I would like to avoid as long as it is possible.

I guess this won't be the case for too long anymore as I expect some of
the UI folks to start tweaking things in 2.5 soon, as the infrastructure
is nearly finished now. But as I cannot foretell the future I would like
to wait with the branching once this happens. Ideally we would see a
2.1.3 and a 2.5-beta2 release with shared translations before.

Best wishes,
Hanno