[ANN] pootle downtime to create 4.3 translation project 20:00 UTC → tomorrow evening (probably, maybe longer)

l10n
#1

Hi *,

I'll start migrating the libo_ui/help projects to be 4.3 working-files
today and will put pootle into maintenance mode during this time (i.e.
no webbased translation possible during that time.

As the process will take a long time, the downtime will last at least
until tomorrow evening.

The downtime will start in a little less than two hours (20:00 UTC, 22:00 CEST)

ciao
Christian

#2

Hi *

I'll start migrating the libo_ui/help projects to be 4.3 working-files
today and will put pootle into maintenance mode during this time (i.e.
no webbased translation possible during that time.

The conversion is finished, and pootle is available again.

ciao
Christian

#3

Hi Sérgio, *,

What happened with 4.2 release? I had it on 100 % and now I have 20 words
needing attention.

Come on, don't make life so hard for admins. At least state the
language or better give concrete example.
So I have to guess it is pt project or dig in old emails to find reference.

pt 42 UI project has 30 words / 10 strings that need attention, so
that doesn't match your 20, so I'm not sure whether I'm looking at the
correct thing in the first place.
And of course if you retranslated stuff in the meantime that makes it
even harder for me to check for differences.

Can you check what went wrong. Or is this intended?

I'd love to check what went wrong, but in order to do so having a
concrete file/string that I can compare to the backup I took before
conversion is of course much easier than having to guess.

And no, there should be no change in translations. But you might have
missed one update against templates or similar. Could as well be that
there was an inconsistency in pootle's db that now showed up after
reindexing. Anyway:

for example one of the untranslated strings:
https://translations.documentfoundation.org/pt/libo42_ui/translate/scaddins/source/pricing.po#search=yxV78&sfields=notes

If I compare the pricing.po before and after the backup I can see no
difference apart from the removal of the obsolete strings that were
removed from the po file. In other words: The string wasn't translated
before copying over the po files.

Also not checked in to the sourcecode, i.e. not part of LibreOffice either:
https://gerrit.libreoffice.org/gitweb?p=translations.git;a=blob;f=source/pt/scaddins/source/pricing.po;hb=libreoffice-4.2.4.2#l352

(there is a second string with identical wording for
RID_PRICING_FUNCTION_DESCRIPTIONS.PRICING_FUNCDESC_OptBarrier that is
translated in both pootle and the sources though:
https://gerrit.libreoffice.org/gitweb?p=translations.git;a=blob;f=source/pt/scaddins/source/pricing.po;hb=libreoffice-4.2.4.2#l109
https://translations.documentfoundation.org/pt/libo42_ui/translate/scaddins/source/pricing.po#search=gp6G8&sfields=notes
)

So from what I can tell by this sample (from which I don't know
whether I'm looking at the correct thing since you didn't provide
details):
Nothing went wrong during the conversion. If libo42_ui project for pt
language was displayed as 100% translated, then this was an
inconsistency in pootle.

As https://translations.documentfoundation.org/pt/libo42_ui/translate/scaddins/source/pricing.po#search=jCwnu&sfields=notes

also is untranslated, it is a stroooooooooooooong indication that pt
project didn't run the update_against_templates after I updated
updated templates for 4.2.0rc1 - aka string freeze.

Those two strings had typo-fixes (and thus ID changes):
-#. uRahb
+#. yxV78
-msgid "Fime to maturity of the option in years"
+msgid "Time to maturity of the option in years"

and
-#. JzCxQ
+#. jCwnu
-msgid "Tower barrier (set to 0 for no lower barrier)"
+msgid "Lower barrier (set to 0 for no lower barrier)"

so again no problem with the conversion done now. When there was a
problem, then it was with the the old installation/that the update
against templates for 42 UI project after the string-freeze update did
fail/was incomplete/was not done at all.

ciao
Christian

#4

Hi Mihkel, *,

2014-05-16 0:51 GMT+03:00 Christian Lohmaier
<lohmaier+ooofuture@googlemail.com>:

One thing that caught my eye, though: are there REALLY over 7000 words'
worth of new strings compared to 4.2, or is it again in large part trivial
stuff like ~ vs. _ (a.k.a. Glade conversion) that could -- and should! -- be
fixed by a script for all translations?

I did run a script over 43 help that did cover the changed hids (i.e.
xml-attributes), but did not run other automated converstion stuff.

And with UI dialog conversion any automatic conversion would very
likely not work. (in the sense of creating the mapping of old → new is
very hard to do automatically). I.e. it would need hours to look
through the diff and identify the old dialog string and the new dialog
string (and their location/identifieres) to create a mapping. I.e. the
source moves to a different file that makes the context-attributes
change, and as UI strings are short and appear in various contexts,
creating such a mapping is not trivial.

Even for help-xml attributes where it is relatively easy (as the order
in the po file doesn't change much, the po file and the
message-context stays the same), it still requires lots of manual
checking to account for added/removed lines/IDs that otherwise would
mix up the mapping.

ciao
Christian

#5

Hi *,

also is untranslated, it is a stroooooooooooooong indication that pt
project didn't run the update_against_templates after I updated
updated templates for 4.2.0rc1 - aka string freeze.

Nope, actually correcting myself here:
As the strings are already present (but untranslated) in the old po
files it means that update_against_templates was run. So that leaves
pootle's statistics display/untranslated string count being wrong for
whatever reason.

ciao
Christian