Tuesday, May 2, 2006, 5:16:31 PM, Balazs Ree wrote:
> On Tue, 02 May 2006 15:16:32 +0200, Daniel Dekany
wrote:
>
>> Tuesday, May 2, 2006, 2:22:20 PM, Hanno Schlichting
wrote:
>>
>>
>>> Balazs Ree wrote:
>>>> The question is very simple. The translator
wishes to develop the
>>>> translation for 2.1 now. On which branch is
he supposes to work?
>>>>
>>>> Hanno, or anyone else please?
>>>
>>> Sorry, I'm still catching up with all my
mail...
>>>
>>> The policy right now is that the trunk is both
for development for Plone
>>> 2.1.3 and 2.5.
>>>
>>> I will reevaluate this this week, as the
assumption was so far that
>>> there are no differences between both versions
(except from some
>>> additional ones in Plone 2.5). This assumption
might not hold true
>>> anymore, but right now it's safe to translate
against trunk.
>>
>> Apart from the additions of new msgid-s, some
msgid-s was slightly
>> *modified* in Plone 2.5, and at least a week ago,
no such msgid changes
>> were made in the Plone 2.1 head, so it seems the
2.1.3 will need the old
>> msgids.
>
> I would rephrase my previous statement.
>
> - New id-s are always put in the .po, with an empty
content
> - old id-s should be kept also, until the become
obsolete when
> (after the old release is not in use any more) they
get purged
OK, this is surely a simpler solution.
> - so it was a problem Hanno deleted the old version,
but otherwise it
> is good that he put in the new one. Instead of mv he
should have done cp.
>
> this means in this case we must put back
"Passwords must match" (without
> an ending dot) and provide the 2.1 translation for it.
We will also have
> a "Passwords must match." - with the ending
dot, that will be the 2.5
> version but since the Hungarian translation has not at
all started on 2.5,
> that will be fine to leave empty for now.
>
>> I think this is just a bagatelle (but annoying)
problem... either the
>> msgid changes should be done in Plone 2.1.3, or
>
> Otherwise we want the translation to follow the product
and not vice
> versa, so let's leave the core developers do whatever
they want and follow
> them up with the translations.
>
>> /PloneTranslations/branches/plone-2.1/ should be
made,
>
> No, as Hanno said there should not be a 2.1 branch of
the translations and
> I agree that work should go on on the trunk.
>
>> and before the
>> 2.1.x releases the latest po files should be
centrally (like by Hanno
>> Schlichting) committed into it, after a script
search-and-replaces all new
>> msgid-s in them with the old msgid-s.
>
> Past releases of 2.1.* will *not* release the latest po
files, because
> they *have been* released already.
I have talked about the future 2.1.* releases of course...
whatever...
> But people will want the fresh
> translation for them. This is the point: everyone can
download the latest
> PloneTranslations product in addition, to get the
freshest version.
> Otherwise, the future releases will already contain the
updates.
>
> Sounds feasible?
As far as I'm concerned, yes.
--
Best regards,
Daniel Dekany
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web
services, security?
Get stuff done quickly with pre-integrated technology to
make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on
Apache Geronimo
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Plone-i18n mailing list
Plone-i18n lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n
|