Bugs to fix in translations

l10n
#1

Hi,

Pootle has many checks, but there are cases which are not covered. You
may remember the style name localization issue from last month.
Therefore I wrote a tool which checked three types of translation
errors:

1. Unique style names.
2. Unique spreadsheet function names.
3. Missing trailing '|' in Windows installer translation.

I uploaded the report to
http://dev-www.libreoffice.org/l10n/error-report/report.txt

I checked 4.1.1 sources.

Affected locales are:
af am ast be bn bn-IN bo br brx bs cy da de dgo dz el en-ZA eo es eu
fa fr gl gu he hi hr id it ka kk km kn ko kok ks ku lb lo lt mai mk ml
mn mni mr my nb ne nl nn nr nso oc om or pa-IN pl pt ro rw sa-IN sat
sd si sid sq ss st sv sw-TZ ta tg th tn tr ts tt ug uz ve vi xh zu

You may want to fix these bugs quickly, because they cause runtime
errors. Unfortunately some locales are unmaintaned. We need to fix
those some day. Many times it does not require knowledge of the
particular language.

Best regards,
Andras

#2

I uploaded 4.0 report, too:
http://dev-www.libreoffice.org/l10n/error-report/report-4.0.txt

Affected locales are:
am ast be bn bn-IN bo br brx bs cy de dgo dz el es fa fr gl he hi hr
id it ka kk kok ks ku lo mai mk ml mn mni mr my nb ne nl nn nr nso oc
om or pa-IN pl pt ro rw sa-IN sat sd sq ss st sv ta tg tn tr ts ug uz
ve xh zu

Cheers,
Andras

#3

Hi Andras!

Pootle has many checks, but there are cases which are not covered.
You may remember the style name localization issue from last month.
Therefore I wrote a tool which checked three types of translation
errors:

2. Unique spreadsheet function names.

I uploaded the report to
http://dev-www.libreoffice.org/l10n/error-report/report.txt

I checked 4.1.1 sources.

Affected locales are: [...] de [...]

You may want to fix these bugs quickly, because they cause runtime
errors.

In German you searched out, that two Calc function names are translated
identically, although they are different in English: EFFECT and EFFECTIVE.

In Calc the EFFECT function becomes EFFECT_ADD during the EFFECTIVE
function keeps EFFECTIVE, so theese functions could have the same
translation, since they do the same (only the output number format is
different), and they work properly in 4.0 and 4.1 so far. So I would not
correct anything in German.

Regadrs,
Christian.

#4

Hi,

You marked croatian HR locale as affected, but I don't see any strings in txt file.
I'll correct 4.0 version, forgot to change Heading / Title problem there.

Best regards,
Mihovil

Dana 19.8.2013. 23:27, Andras Timar je napisao:

#5

Thanks for doing that.
You reported that in EO, NESIMETRIECO is duplicated, but Pootle did not
find it (I presume it is the UI of 4.1)
I have grep-ed my local copy of the files for it and not found it.
Where I should look for it?

Regards
Donald

#6

Hi,

Thanks for doing that.
You reported that in EO, NESIMETRIECO is duplicated, but Pootle did not
find it (I presume it is the UI of 4.1)
I have grep-ed my local copy of the files for it and not found it.
Where I should look for it?

https://translations.documentfoundation.org/eo/libo_ui/translate.html#search=NESIMETRIECO&sfields=target

I found that you translated SKEW and SKEWP as NESIMETRIECO.

Cheers,
Andras

#7

thanx Andras for this check, galician arranged.

It's a bit strange because I remember I have fix it long time ago
(talking about translation for «title / heading» names)

#8

Hi,

In German you searched out, that two Calc function names are translated
identically, although they are different in English: EFFECT and EFFECTIVE.

In Calc the EFFECT function becomes EFFECT_ADD during the EFFECTIVE
function keeps EFFECTIVE, so theese functions could have the same
translation, since they do the same (only the output number format is
different), and they work properly in 4.0 and 4.1 so far. So I would not
correct anything in German.

You are right, it was a false alarm. I fixed this bug in pocheck tool.

Best regards,
Andras

#9

Consider adding a check for mismatched terminal newlines. In other
software builds, this type of error can be fatal, not sure about LO.
"newlines" and "endwhitespace" pofilters can catch this, but as a build
killer, a special check might be useful.

#10

Thank you.

Donald

#11

Hi Chris,

Consider adding a check for mismatched terminal newlines. In other software
builds, this type of error can be fatal, not sure about LO. "newlines" and
"endwhitespace" pofilters can catch this, but as a build killer, a special
check might be useful.

Pootle checks for mismatching terminal newlines. I didn't want to
duplicate pofilter/Pootle checks. I don't know any examples when
mismatching newlines/whitespaces can be fatal in LibreOffice. If
anyone knows about such case, or about other type of translation
errors that we should check for, please let me know.

Thanks,
Andras

#12

Fixed issues for ml.

Thanks
Ani

#13

Fixed in ast for 4.1 & 4.0 by changing function name from TIME>HORA to

TIEMPU (conflict with HOUR>HORA)

I also changed related translations, but still have to do a second
pass to make sure I didn't miss something.

Regards

#14

Hi Ousmane,

Hi

Let introduce me Ousmane Faty NDongo, I was introduced by Sophie for
the localization of Wolof. I am writing for my Pootle account rights.
My user is: usu, my local is: wo

Bests regards

Ousmane

Welcome to LibreOffice community. I granted you the necessary rights in
Pootle. You are language admin of Wolof, you can translate/review/add
team members/etc.

Best regards,
Andras

#15

Hi,

Hi,

Pootle has many checks, but there are cases which are not covered. You
may remember the style name localization issue from last month.
Therefore I wrote a tool which checked three types of translation
errors:

1. Unique style names.
2. Unique spreadsheet function names.
3. Missing trailing '|' in Windows installer translation.

Thanks to Zeki, I added a 4th check: Math symbol names (from
symbol.src) must not contain spaces
I updated the reports for 4.0.x and 4.1.x. Please note, I tested files
that are in git not that are in Pootle. So you may have fixed some of
these already. In this case, thank you and please ignore that part of
the report. I updated files in git 2 days ago.

http://dev-www.libreoffice.org/l10n/error-report/report-4.0.txt
http://dev-www.libreoffice.org/l10n/error-report/report-4.1.txt

Let's fix all of these bugs for 4.1.2 and 4.0.6 in the coming 1-2 weeks!

Thanks,
Andras

#16

In data lunedì 19 agosto 2013 23:35:57, Andras Timar ha scritto:

I uploaded 4.0 report, too:
http://dev-www.libreoffice.org/l10n/error-report/report-4.0.txt

Affected locales are:
am ast be bn bn-IN bo br brx bs cy de dgo dz el es fa fr gl he hi hr
id it ka kk kok ks ku lo mai mk ml mn mni mr my nb ne nl nn nr nso oc
om or pa-IN pl pt ro rw sa-IN sat sd sq ss st sv ta tg tn tr ts ug uz
ve xh zu

Done for Italian (it)

Ciao

#17

How should we separate words without space characters? InThisWay?
In_this_way or in-this-one? Are there any guidelines?

Btw. You can find this in Tool > Catalog (Symbol windows) > Special
symbols.

#18

Hi :slight_smile:
I tend to find using a capital letter at the beginning of each word neatly avoids having to use any character at all between words.

ForExample LibreOffice is fairly easy to read as 2 separate words.

I'm not sure what the standard practise is though
Regards from
Tom :slight_smile:

#19

HR all done.

Best regards,
Mihovil

Dana 22.8.2013. 14:08, Andras Timar je napisao:

#20

Hi Tom,

Hi :slight_smile:
I tend to find using a capital letter at the beginning of each word neatly avoids having to use any character at all between words.

ForExample LibreOffice is fairly easy to read as 2 separate words.

I'm not sure what the standard practise is though

That is not. It's a practice in English (all the words in the menus are capitalized in English, but for example in French, it's not accepted) and I'm sure that in several languages the camel style is not accepted. We have to find a way that correspond to the current localization practice in our language.

Kind regards
Sophie