string freeze has been broken in libreoffice-4-1

l10n
#1

Hi,

I noticed, that a recent commit broke string freeze in libreoffice-4-1
branch: b350dc2e1e4c3ac7cb722569d462c95dbb3cbbda
First I wanted to simply revert it. Then I noticed that there were
more string changing commits in stable branch.
In core:
b350dc2e1e4c3ac7cb722569d462c95dbb3cbbda
38f11fdb08249a6cf7140ee74016cd69f28e289a
In help:
0d8b37cd9e0b89d1136b09a81671c88fc91fee3e
d78c3cb249a11ea45542d340754e960d47a35fa6
472620fd6f95163f400ba8a88c6f7edc11d6c967 (I did this one today as the
correction of d78c3cb)

So, probably the best would be to update Pootle with the changed pot
files, and catch up with translations by 4.1.4. These are the changed
files:
helpcontent2/source/text/sbasic/shared.pot
helpcontent2/source/text/shared/01.pot
officecfg/registry/data/org/openoffice/Office/UI.pot
sd/source/ui/slideshow.pot

Cheers,
Andras

#2

Hello Andras

When do you plan to upload the new templates?

Cheers

Hi,

I noticed, that a recent commit broke string freeze in libreoffice-4-1
branch: b350dc2e1e4c3ac7cb722569d462c95dbb3cbbda
First I wanted to simply revert it. Then I noticed that there were
more string changing commits in stable branch.
In core:
b350dc2e1e4c3ac7cb722569d462c95dbb3cbbda
38f11fdb08249a6cf7140ee74016cd69f28e289a
In help:
0d8b37cd9e0b89d1136b09a81671c88fc91fee3e
d78c3cb249a11ea45542d340754e960d47a35fa6
472620fd6f95163f400ba8a88c6f7edc11d6c967 (I did this one today as the
correction of d78c3cb)

So, probably the best would be to update Pootle with the changed pot
files, and catch up with translations by 4.1.4. These are the changed
files:
helpcontent2/source/text/sbasic/shared.pot
helpcontent2/source/text/shared/01.pot
officecfg/registry/data/org/openoffice/Office/UI.pot
sd/source/ui/slideshow.pot

Cheers,
Andras
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

- --
Olivier Hallot
Founder, Board of Directors Member - The Document Foundation
The Document Foundation, Kurfürstendamm 188, 10707 - Berlin, Germany
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint
LibreOffice translation leader for Brazilian Portuguese
+55-21-8822-8812

#3

Cloph will do that soon.

Cheers,
Andras

#4

Hi Andras,

I´ve run "Update from templates" and now I have 205 words in sbasic and 470
in shared. Is this ok?

These are to many changes from a brach that it is supposed to be freezed.

Regards

#5

Hi *,

I noticed, that a recent commit broke string freeze in libreoffice-4-1
branch: b350dc2e1e4c3ac7cb722569d462c95dbb3cbbda
First I wanted to simply revert it. Then I noticed that there were
more string changing commits in stable branch.

Thanks for having an eye on that.

So, probably the best would be to update Pootle with the changed pot
files, and catch up with translations by 4.1.4. These are the changed
files:
helpcontent2/source/text/sbasic/shared.pot
helpcontent2/source/text/shared/01.pot
officecfg/registry/data/org/openoffice/Office/UI.pot
sd/source/ui/slideshow.pot

I update the templates on pootle and also already triggered the update
for UI for all languages[1], as there are only two changes (and one
removed string):

* One added context-menu entry "Edit presentation" (slideshow.pot)
http://cgit.freedesktop.org/libreoffice/core/commit/?id=38f11fdb08249a6cf7140ee74016cd69f28e289a
"fdo#45233 Allow editing pps/ppsx Autoplay Presentations"

* one changed string Text → Character (UI.pot)
http://cgit.freedesktop.org/libreoffice/core/commit/?id=b350dc2e1e4c3ac7cb722569d462c95dbb3cbbda
"fdo#68414: SIDEBAR: property's Text named incorrectly"

For help, please trigger the Update from templates yourself.
I'll run the update this weekend

The changes there are mostly changing the attributes of the ahelp
tags, but also new documentation for the date/time related functions.

Thanks again to Andras for noticing & notifying and all translators
for their efforts

ciao
Christian
[1] still running, so don't panic if you don't see the changed strings
yet when your language-code is in the second half of the alphabet

#6

Hi Sérgio,

Hi Andras,

I´ve run "Update from templates" and now I have 205 words in sbasic
and 470 in shared. Is this ok?

These are to many changes from a brach that it is supposed to be freezed.

Well, we could have avoided re-translating the 470 words in shared,
because the translatable strings have not changed, only identifiers.
That's a pity. If only Pootle were more intelligent, and distinguished
tags from text... The 205 words in sbasic are the help of the new
Date/Time functions in Basic. It was exceptional that an API change
happened in stable branch.

Best regards,
Andras

#7

Ok. Thanks

#8

Can you elaborate on this issue?

Regards,
Khaled

#9

2013.11.06 15:10, Andras Timar rašė:

Hi Sérgio,

Hi Andras,

I´ve run "Update from templates" and now I have 205 words in sbasic
and 470 in shared. Is this ok?

These are to many changes from a brach that it is supposed to be freezed.

Well, we could have avoided re-translating the 470 words in shared,
because the translatable strings have not changed, only identifiers.
That's a pity. If only Pootle were more intelligent, and distinguished
tags from text...

And why were the identifiers changed?

Rimas

#10

The translate-toolkit which I suppose is used in Pootle, is intelligent enough to migrate the content based on the combination of msgid and identifier (in msgcomment), but not intelligent to pass on the result as a 'sure thing', only as a fuzzy hit. You'd still have to go through the fuzzies manually and 'approve'. Still takes time but no big problem.

But when identifiers change, there is nothing sensible at all translate-toolkit might do, and you've got to work manually through lots of 'best guesses', re-translating, sort of.

-Yury

#11

Hi Khaled,

Well, we could have avoided re-translating the 470 words in shared,
because the translatable strings have not changed, only identifiers.
That's a pity. If only Pootle were more intelligent, and distinguished
tags from text...

Can you elaborate on this issue?

For example:

Old English string:
<ahelp hid="HID_ALIGNMENT">Sets the alignment options for the contents
of the current cell, or the selected cells.</ahelp>

New English string:
<ahelp hid="cui/ui/cellalignment/CellsAlignPage">Sets the alignment
options for the contents of the current cell, or the selected
cells.</ahelp>

Only the hid attribute of ahelp tag changed, which is not localizable
anyway. Yet, upon update the old translation is not even offered as
fuzzy, because fuzzy matching algorithm does not distinguish tags from
text. Tags in segments are usually invariable. It would make sense to
take this into account, when you build a local TM and/or eveluate
matches from the local TM.

Best regards,
Andras

#12

Hi Khaled,

>> Well, we could have avoided re-translating the 470 words in shared,
>> because the translatable strings have not changed, only identifiers.
>> That's a pity. If only Pootle were more intelligent, and distinguished
>> tags from text...
>
> Can you elaborate on this issue?
>

For example:

Old English string:
<ahelp hid="HID_ALIGNMENT">Sets the alignment options for the contents
of the current cell, or the selected cells.</ahelp>

New English string:
<ahelp hid="cui/ui/cellalignment/CellsAlignPage">Sets the alignment
options for the contents of the current cell, or the selected
cells.</ahelp>

Only the hid attribute of ahelp tag changed, which is not localizable
anyway. Yet, upon update the old translation is not even offered as
fuzzy, because fuzzy matching algorithm does not distinguish tags from
text. Tags in segments are usually invariable.

Is the <ahelp> tag almost alway a top level one? If yes, then I think
the best way is for PO extraction tool to strip the tags completely and
use the hid as msgctx (the PO to help converter will have to be updated,
too).

It would make sense to take this into account, when you build a local
TM and/or eveluate matches from the local TM.

I think the fuzzy matching in translate toolkit is pretty simplistic, it
probably uses Levenshtein distance and don't do any parsing of the text.

We have some ideas on how to improve this, but nothing implemented yet.

You can try to experiment with pomigrate2 tool from translate toolkit
with or without -p option and see if it gives you better results (with
-p option it will use the same logic used by Pootle).

Regards,
Khaled

#13

Unfortunately it's not, that's why it is part of the segment after
all. And there are other "internal" tags apart from <ahelp>, e.g.
<image> and <link> which also have non-translatable (and sometimes
changing) attributes.

Best regards,
Andras