l10n bugs to fix for LibreOffice 3.5.0 beta3

l10n
#1

Hi,

Today I exported updated po files from Pootle and pushed
them to git to the translations module. The next push will take place
three weeks from, for LibreOffice 3.5.0 beta3. Meanwhile, could you all
please fix bugs in your translations? :slight_smile:

Fatal errors:
de eo eu fi nl pt pt-BR tr vi
I corrected them in git as I could, but please correct them in Pootle, too.

Non-fatal errors:
bg cs da de en-GB eo eu fi ne nl pl pt-BR pt ru sk tr vi

Log files (from all tools) and error files (from gsicheck tool):
http://dev-www.libreoffice.org/l10n/errorlog/

It is also well worth looking at the Review tab in Pootle.
https://translations.documentfoundation.org/xx/libo35x_ui/review.html
https://translations.documentfoundation.org/xx/libo35x_help/review.html
– where xx is your language code. Errors in 'xmltags' or 'variables' can
cause runtime issues.

Best regards,
Andras

#2

Hi, Andras, all.

Non-fatal errors:
ru

Fixed.

#3

fixed

Thanks

Hi,

(snip)

Best regards,
Andras

- --
Olivier Hallot
Founder, Board of Directors Member - The Document Foundation
LibreOffice translation leader for Brazilian Portuguese
+55-21-8822-8812

#4

Hi!

Fatal errors:
de

Fixed.

#5

Hi Andras,
all errors for tr fixed

Best regards,
Ayhan

#6

Fatal errors for eo fixed.

In the reviews what does this mean: "acronyms ... failed"?

Donald

#7

Sorry if I'm asking something that's been answered already but I have been busy with other stuff and not reading my posts carefully.

In short, is there a reason why the ~1500 or so translations that I'd done for 3.5 for gd have suddently disappeared? I'm sure I was at 100%.

Cheers

Michael

#8

Hi Michael, *,

Sorry if I'm asking something that's been answered already but I have been
busy with other stuff and not reading my posts carefully.

In short, is there a reason why the ~1500 or so translations that I'd done
for 3.5 for gd have suddently disappeared? I'm sure I was at 100%.

Those are new/changed strings.

Best regards,
Mihkel

#9

I could have sworn I'd done them but having checked my backup, it seems you're right. My apologies... I need a holiday :slight_smile:

Michael

20/12/2011 01:15, sgrìobh Mihkel Tõnnov:

#10

Fixed.

#11

Non-fatal errors for Danish is corrected.

/Leif

#12

Basque (eu)
Errors shown in the error-log corrected

#13

Hi

Would it be possible to generate these log and err files in utf-8? At present they stuff up the Unicode characters.
For instance, in http://dev-www.libreoffice.org/l10n/errorlog/eo.err:
"vidigi la alŝutitan vikipaĝon"
should be "vidigi la alŝutitan vikipaĝon"

Donald

#14

Hi,

> Hi,
>
> Today I exported updated po files from Pootle and pushed
> them to git to the translations module. The next push will take place
> three weeks from, for LibreOffice 3.5.0 beta3. Meanwhile, could you all
> please fix bugs in your translations? :slight_smile:
>
> Fatal errors:
> de eo eu fi nl pt pt-BR tr vi
> I corrected them in git as I could, but please correct them in Pootle,
too.
>
> Non-fatal errors:
> bg cs da de en-GB eo eu fi ne nl pl pt-BR pt ru sk tr vi
>
> Log files (from all tools) and error files (from gsicheck tool):
> http://dev-www.libreoffice.org/l10n/errorlog/

Hi

Would it be possible to generate these log and err files in utf-8? At
present they stuff up the Unicode characters.
For instance, in http://dev-www.libreoffice.org/l10n/errorlog/eo.err:
"vidigi la alÅ utitan vikipaÄ on"
should be "vidigi la alŝutitan vikipaĝon"

It’s shown correctly here. Your browser/text-editor probably chooses the
wrong encoding -- I got the result you described when I manually set the
encoding to ISO 8859-1 (i.e. Western European), UTF-8 displayed everything
fine.

Best regards,
Mihkel

#15

Hi Donald,

Would it be possible to generate these log and err files in utf-8? At present they stuff up the Unicode characters.

They are.

For instance, in http://dev-www.libreoffice.org/l10n/errorlog/eo.err:
"vidigi la alÅ utitan vikipaÄ on"
should be "vidigi la alŝutitan vikipaĝon"

Make sure your browser uses the UTF-8 charset to display the file.

As it is a plain textfile and no html file, the browser is not told
explicitly what charset to use, so it uses whatever is configured as
the default charset in the browser.

ciao
Christian

#16

Thanks, Mihkel and Christian. I should have thought of that.

Donald

#17

Op Di, 2011-12-20 om 09:27 +1300 skryf Donald Rogers:

Fatal errors for eo fixed.

In the reviews what does this mean: "acronyms ... failed"?

Hallo Donald

It is a test that tries to warn of changed acronyms. It doesn't
necessarily indicate a problem, but might be worth reviewing. More
details here:
http://translate.sourceforge.net/wiki/toolkit/pofilter_tests#acronyms
There are descriptions for all the quality checks. I hope that helps.

Keep well
Friedel