Translations from Pootle pushed to git (for 3.4 rc2), bugs to fix

l10n
#1

Hi,

On Sunday I exported updated po files from Pootle and I pushed them to
git to the translations module. LibreOffice 3.4 rc2 will contain
these translation updates. According to the plan rc2 will be 3.4.0
final, if all go well. So the next translation update will be for 3.4.1.
I'll do the push next time when a release (3.4.1 rc) is coming.

Please note, however, that there are still bugs in your translations
that need to be fixed ASAP.

Locales with fatal errors:
cs, is, tr, zh-TW

I fixed fatal (build breaker) errors before commit, but you need to fixe
them in Pootle, too.

Locales with bugs:
as, bg, bn, bo, brx, bs, ca, cs, de, dgo, el, eo, fa, gu, he, hi, hr,
id, is, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, my, ne, nl,
nn, nr, nso, oc, om, or, pl, ro, rw, sa-IN, sat, sd, sk, sq, st, sv, ta,
tg, tn, tr, ts, ug, uk, uz, zh-TW

Log files (from all tools) and error files (from gsicheck tool):
http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/

Best regards,
Andras

#2

Andras,

Locales with bugs:

id, is, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, my, ne, nl,

I have fixed kn issues

Cheers

Shankar

#3

24-05-2011 13:47 tarihinde, Andras Timar yazdı:

Hi,

Hi Andras

On Sunday I exported updated po files from Pootle and I pushed them to
git to the translations module. LibreOffice 3.4 rc2 will contain
these translation updates. According to the plan rc2 will be 3.4.0
final, if all go well. So the next translation update will be for 3.4.1.
I'll do the push next time when a release (3.4.1 rc) is coming.

Please note, however, that there are still bugs in your translations
that need to be fixed ASAP.

Locales with fatal errors:
cs, is, tr, zh-TW

I fixed tafal errors for tr

I fixed fatal (build breaker) errors before commit, but you need to fixe
them in Pootle, too.

Locales with bugs:
as, bg, bn, bo, brx, bs, ca, cs, de, dgo, el, eo, fa, gu, he, hi, hr,
id, is, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, my, ne, nl,
nn, nr, nso, oc, om, or, pl, ro, rw, sa-IN, sat, sd, sk, sq, st, sv, ta,
tg, tn, tr, ts, ug, uk, uz, zh-TW

Log files (from all tools) and error files (from gsicheck tool):
http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/

I fixed errors for tr

Best regards,
Andras

Best regards,
Ayhan

#4

zh-TW should be fixed. Andras, would you please check it again for me?

#5

Hi,

Hi!

On Sunday I exported updated po files from Pootle and I pushed them to
git to the translations module. LibreOffice 3.4 rc2 will contain
these translation updates. According to the plan rc2 will be 3.4.0
final, if all go well. So the next translation update will be for 3.4.1.
I'll do the push next time when a release (3.4.1 rc) is coming.

Please note, however, that there are still bugs in your translations
that need to be fixed ASAP.

Locales with fatal errors:
cs, is, tr, zh-TW

I fixed fatal (build breaker) errors before commit, but you need to fixe
them in Pootle, too.

Locales with bugs:
as, bg, bn, bo, brx, bs, ca, cs, de, dgo, el, eo, fa, gu, he, hi, hr,
id, is, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, my, ne, nl,
nn, nr, nso, oc, om, or, pl, ro, rw, sa-IN, sat, sd, sk, sq, st, sv, ta,
tg, tn, tr, ts, ug, uk, uz, zh-TW

Log files (from all tools) and error files (from gsicheck tool):
http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/

In Pootle seems everything is ok for my locale. Maybe I didn't get the point for the bug. May You explain please?
http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/uk.log

#6

Hi *,

[...]
In Pootle seems everything is ok for my locale. Maybe I didn't get the point
for the bug. May You explain please?
http://ftp.fsf.hu/LibreOffice/3.4-rc2-l10nbugs/uk.log

The problem that you have the exact same string in the location for
two items that can then be easily confused in the UI and might even
break functionality (when you for example assign the same name to two
different functions in Calc).
Заголовок is used for both heading and title
If you cannot find a different word for title, use something that then
corresponds to "main heading" or something like that.

ciao
Christian

#7

Hi all,

I've fixed 'ca' bugs.

Regards,

Joan Montané

#8

Now I got it. It's fixed. Thanks for information!

#9

Hi Andras,

Thanks to Ayhan he fixed the fatal errors and other errors.

On Sunday I exported updated po files from Pootle and I pushed them to
git to the translations module. LibreOffice 3.4 rc2 will contain
these translation updates. According to the plan rc2 will be 3.4.0
final, if all go well. So the next translation update will be for 3.4.1.
I'll do the push next time when a release (3.4.1 rc) is coming.

I understand that the this was the last push befor 3.4 stable relase,
so rc2 translations will be in 3.4?
However, we just managed to achieve %100 percent on 3.4 UI
translations today :frowning: . Is it possible to update Turkish UI files.
It is very important for our campaign to present LibreOffice as it has
a %100 Turkish User Interface.

We gathered a good localization team and thing are getting quite well.
Turkish translations in Help files are not very good and we have lots
of work to do. We hope to achieve this ratios in Help files as soon as
possible.

Best regards,
Zeki

#10

Hi Zeki,

I understand that the this was the last push befor 3.4 stable relase,
so rc2 translations will be in 3.4?
However, we just managed to achieve %100 percent on 3.4 UI
translations today :frowning: . Is it possible to update Turkish UI files.
It is very important for our campaign to present LibreOffice as it has
a %100 Turkish User Interface.

The tree was tagged for release yesterday. I can't change that. If
there will be another rc, then your translations can be updated in
git, otherwise you have to wait one month until 3.4.1. You can still
advertise your translation as 100% complete as it is 100% in Pootle.
In the application there are still bugs that prevent 100% localization
anyway. Some of them are unresolved even in master.

Last time in OpenOffice.org project, for version 3.3 the last l10n
bugfix submission date was 30th September 2010. OpenOffice.org 3.3 was
released on 26th January 2011. So final translation deadline was 4
month before release. With LibreOffice we managed to make
significantly shorter turnarounds. Deadline is 1-2 days before tagging
which means ~1 week before release. I don't think it's possible to
make it shorter. Translations regularly break the build. We need time
to test them and correct the errors.

Best regards,
Andras