Not recognized changes in (Polish) translation

l10n
#1

Hey

Today member of my team discovered a few new and unexpected changes in
translation. For instance:

- "All" means "Wszystkie" but something changed translation on "Dla
wszystkich".
- "Number" means "Liczba" but something changed translation on "Ilość".

These changes affected only with LO 4.1. Version 4.0 still contains old
(correct written) words.

All:
4.0 -
https://translations.documentfoundation.org/pl/libo40x_ui/translate.html#unit=36090217
4.1 -
https://translations.documentfoundation.org/pl/libo_ui/translate.html#unit=40165460

Number:
4.0 -
https://translations.documentfoundation.org/pl/libo40x_ui/translate.html#unit=36090220
4.1 -
https://translations.documentfoundation.org/pl/libo_ui/translate.html#unit=40165390

Non of us did not implement any changes, so someone did it without our
permission and knowledge (or is bot guilty of it?)

And the second. I got bug report that EDATE function doesn't work properly.
The reason is error in description.

<item type="input">=EDATE(3.31.2001;-1)</item> returns 2.28.2001.
<item type="input">=NR.SER.DATY(31.3.2001;-1)</item> zwraca 28.02.2001.

source:
https://translations.documentfoundation.org/pl/libo_help/translate.html#unit=31990219

There are lack of quotation marks. Correct version is:

=EDATE<font size="3">("3.31.2001";-1)</font>

We made mistake during translating because of typo in original sentence.
Please verify this case and correct English version.

Moreover, the outcome is not date but serial number so description should
sound like:

=EDATE("3.31.2001";-1) returns the serial number 36950. Formatted as a
date, this is 2.28.2001

#2

Hi,

Moreover, the outcome is not date but serial number so description should
sound like:

=EDATE("3.31.2001";-1) returns the serial number 36950. Formatted as a
date, this is 2.28.2001

you are right, I pushed your suggestion for Gerrit review: https://gerrit.libreoffice.org/#/c/6239/
Thanks for reporting this!

Generally speaking, it would be very appreciated if someone could review (especially in terms of proofreading) these Gerrit patches related to local help content (the list of all reviews in progress can be found at https://gerrit.libreoffice.org/#/q/status:open+project:help,n,z). It's a pity that help improvements are submitted unnoticed by documentation or translation teams... Thanks in advance to everyone who will get involved.

Regards,
Stanislav

#3

Glad to hear that, Stanislav.

Anyway, could someone explain me why our translations are mechanically
changed?

#4

Hi Mateusz, all,

Things like this have also happened to Estonian translation on Pootle. I
don't remember concrete examples anymore, though.
My impression is that it has happened after updating from templates of a
new branch for the first time, i.e. when (say) 4.0 translations are set as
4.1 translations and updated from 4.1 templates, then something goes wrong
for some strings.

Best regards,
Mihkel
Estonian team

#5

So how can we prevent our work from this updates? One word could have 3
different translations and if updating concern all files, there could
appears many new errors. Perspective of eternal correcting the same words
isn't motivating to work.

How can we an mass and repeatedly compare files from LO 4.0 with 4.1
version?

#6

I don't have any One Good Solution.

Perhaps you/someone could write a script that downloads files for desired
branches (say, 4.0 and 4.1) from Pootle, then runs a local update (from 4.1
templates) on the 4.0 files and compares those with 4.1 files downloaded
from Pootle. An immediate problem with this is that strings that have been
moved to new files will probably appear lost.

Another way would be to work on a local copy (using software with
translation memory and a hopefully more reliable update mechanism than
Pootle), update the files from templates yourself, and upload the
translated files to Pootle as needed. Admittedly that approach could be
difficult for larger teams where people have different roles, like
translator, reviewer, manager, etc.

Of course ideally, someone who can should just fix Pootle...