Why pootle has incomplete translation and where to get complete POT/PO?

l10n
#1

Hi,

there is something strange in translating process.

Pootle says, that 4.3 ui (RU) completed at 100%, so there are no
untranslated items here:
https://translations.documentfoundation.org/ru/libo43_ui

It seems ok and nothing to translate, isnt't it?

So start LO4.3 Draw, select Russian ui, choose
Format - Area - Gradients tab
Формат - Область - Градиеты (in Russian)

and see bunch of untranslated items:

Tango Green
Subtle Tango Green
Tangi Purple
and more...

Now try to find one of these items in 4.3 ui pootle:
https://translations.documentfoundation.org/ru/libo43_ui/translate/#search=Tango%20Green&sfields=source,target&soptions=exact

No results found.

Now try to find one of these items in git:
http://cgit.freedesktop.org/libreoffice/translations/tree/source/ru/svx/source/dialog.po

Bingo!!! There are

#: sdstring.src
msgctxt ""
"sdstring.src\n"
"RID_SVXSTR_GRDT70\n"
"string.text"
msgid "Tango Green"
msgstr ""

#: sdstring.src
msgctxt ""
"sdstring.src\n"
"RID_SVXSTR_GRDT71\n"
"string.text"
msgid "Subtle Tango Green"
msgstr ""

#: sdstring.src
msgctxt ""
"sdstring.src\n"
"RID_SVXSTR_GRDT72\n"
"string.text"
msgid "Tango Purple"
msgstr ""

and so on. And yes, they are untranslated.

Thanks all reading here.

And now one simple question:
Where to get actual PO/POT bundle for translation and where to send
translated bundle so complete translation has no untranslated items?

Thanks once more.

PS. Our translation team works primary offline and merges translations
to pootle before releases.

#2

Hi Serg, *,

Pootle says, that 4.3 ui (RU) completed at 100%, so there are no
untranslated items here:
[...]
and see bunch of untranslated items:

Tango Green
Subtle Tango Green
Tangi Purple
and more...

Now try to find one of these items in 4.3 ui pootle:
[...]
No results found.

Now try to find one of these items in git:
http://cgit.freedesktop.org/libreoffice/translations/tree/source/ru/svx/source/dialog.po

Bingo!!! There are

but that displays master tree (i.e. the state of 4.4 before it
branched-off), so irrelevant for 4.3 translations.

https://github.com/LibreOffice/translations/blob/libreoffice-4-3-6/source/ru/svx/source/dialog.po
is the translation as of now in the 4.3.6 one. (i.e. the most current
in the 4-3 line)

[cgit.fdo is also pretty slow when working with the translation repo,
so I suggest to use the github mirror for inspection instead (see also
Sophie's mail from a short while ago)]

Those strings were not flagged as translatable in the 4.3 branch. only

http://cgit.freedesktop.org/libreoffice/core/commit/?id=927a869b9ac0e8a36de08f160a0c9a42452ef3aa

made them translatable.

The 100% refers to what is in the po file templates/what is flagged as
translatable. The value might be off sometimes because some stats are
not updated immediately, but in this case the 100% is correct. You
cannot translate more in 4.3. Even if you added the strings to the
pofile, they wouldn't be used by LibreOffice.

Making those strings translatable for LO 4.4 didn't please all
translators either. There were rants about that useless change, yadda
yadda... You cannot please everyone I guess..

long story short: Those strings are not translatable in 4.3, what you
see in pootle is all you can translate.

ciao
Christian

#3

Hi Christian, All,

Thanks for clarification.

Those strings were not flagged as translatable in the 4.3 branch. only

http://cgit.freedesktop.org/libreoffice/core/commit/?id=927a869b9ac0e8a36de08f160a0c9a42452ef3aa

made them translatable.

This commit made on 2014-09-03. Is it good time now to merge the
commit in 4.3 branch and update Pootle?
This doesn't make things worse but it can make localized versions better a bit.

Can anyone make these changes please?

#4

I don’t think it’s worth the hassle at this point in the release
cycle. There’s only one version left to release in that branch, 4.3.7.

#5

Hi Serg, Adolfo, *,

This commit made on 2014-09-03. Is it good time now to merge the
commit in 4.3 branch and update Pootle?
This doesn't make things worse but it can make localized versions better a bit.

I don’t think it’s worth the hassle at this point in the release
cycle. There’s only one version left to release in that branch, 4.3.7.

Indeed, and furthermore this would arguably be a UI/string change and
those aren't "allowed" at that point of a release.
And since people did complain loudly the first time the strings were
made translatable in the first place, I won't touch that area, not to
mention that I don't know how much effort it would be to actually port
that change over. Dialogs might have changed, etc.

Too risky with little benefit, and gradient's labels aren't that
critical I'd say (also given that you're the first to notice/bring it
to the list)...

ciao
Christian

#6

Hi all,

Hi Serg, Adolfo, *,

This commit made on 2014-09-03. Is it good time now to merge the
commit in 4.3 branch and update Pootle?
This doesn't make things worse but it can make localized versions better a bit.

I don’t think it’s worth the hassle at this point in the release
cycle. There’s only one version left to release in that branch, 4.3.7.

Indeed, and furthermore this would arguably be a UI/string change and
those aren't "allowed" at that point of a release.

No.
The strings (untranslatable) was added some time ago, allowed or not.
They are in UI already. And yes, they are untranslated now. What this
UI/string freeze rule for? Seems to me it prevents untranslated
strings. So why this simple rule works against translating?

As for me, 4.3.{6,7} will be in use after 4.4.{1,2,3...} because of
regressions :frowning: