LibreOffice 4.1 translation heads-up

l10n
#1

Hi,

LibreOffice 4.1 is approaching. In order to reduce the amount of
translation work, I would like to smartly migrate 4.0 translations to
4.1 in Pootle. Many source code changes happened, including the
transition from .src format dialogs to .ui format dialogs. Hopefully
old translations can be leveraged in high proportion. That means that
you'll have less to translate and you will not have to translate
things that you already have done.

This will happen sometimes next week. At the same time 3.6
translations will be removed from Pootle in order to save resources.
4.0 and 4.1 will be there.

Best regards,
Andras

#2

That would be awesome.

Please make a post here the day before merge so we don´t do any work that
could be lost.

Regards

#3

That's to be hoped for, but Pootle isn't exactly great at this (mildly
said), so I'm rather sceptical. After being bitten by this several times
(not only with LO), I now keep a local copy of the Pootle files, so in the
worst case I will be able to do my own leveraging.

#4

In data venerdì 17 maggio 2013 09:23:46, Andras Timar ha scritto:

Hi,

LibreOffice 4.1 is approaching. In order to reduce the amount of
translation work, I would like to smartly migrate 4.0 translations to
4.1 in Pootle. Many source code changes happened, including the
transition from .src format dialogs to .ui format dialogs. Hopefully
old translations can be leveraged in high proportion. That means that
you'll have less to translate and you will not have to translate
things that you already have done.

This will happen sometimes next week. At the same time 3.6
translations will be removed from Pootle in order to save resources.
4.0 and 4.1 will be there.

This is a great news!

We are ready :slight_smile:

Ciao

#5

Hi,

Hi,

LibreOffice 4.1 is approaching. In order to reduce the amount of
translation work, I would like to smartly migrate 4.0 translations to
4.1 in Pootle. Many source code changes happened, including the
transition from .src format dialogs to .ui format dialogs. Hopefully
old translations can be leveraged in high proportion. That means that
you'll have less to translate and you will not have to translate
things that you already have done.

This will happen sometimes next week. At the same time 3.6
translations will be removed from Pootle in order to save resources.
4.0 and 4.1 will be there.

Migration is done. Hopefully everything is in order for everyone. I
tested Hungarian and it was fine. There are ~4500 UI words and ~4000
help words that need your attention, if you have 100% translated
4.0.x.

Best regards,
Andras

#6

I´ve found out one string with errors in English:

File:

android/sdremote/res/values.po
Context:

strings.xml wifiAlertMsg string.text
Comments:

mKeEC
This is still an experimental feature. You need to "enable experimental
features" in "Preference"-"LibreOffice"-"Advanced" on your computer. \n
The use over Bluetooth is recommanded.

#7

I’ve found another string with a typo: “_Toolbare” (instead of
“_Toolbars”). It’s in cui/uiconfig/ui.po, and its context is
customize.ui label29 label string.text

Thank you very much for migrating the strings, András!

#8

Thanks for the typo fixes (recommanded, Toolbare), please report them
here, when you find one.

Thanks,
Andras

#9

So from the first look about 50% of missing strings are things that were
already translated. And I have seen missing translations (really missing,
not even marked as fuzzy) where the only difference is a dot at the end of
a sentence, which is both silly and sad. Hurray for pointless work.

#10

Unless you used hidden copy field, you sent this reply only to me, not to
the mailing list, so Andras would not see it. I'm reposting it to fix that.
But the search function is broken anyway, it doesn't find half of the
things even if it's "working" and since it uses really awkward syntax, it
treats some common words/chars as stopwords/keywords (for example 'to',
'or', any kind of parenthesis etc.).

#11

Hello :slight_smile:
A typo :

File: cui/uiconfig/ui.po
Context: customize.ui label26 label string.text
LiberOffice Writer Toolbars
Best regards
Alan

Unless you used hidden copy field, you sent this reply only to me, not to
the mailing list, so Andras would not see it. I'm reposting it to fix that.
But the search function is broken anyway, it doesn't find half of the
things even if it's "working" and since it uses really awkward syntax, it
treats some common words/chars as stopwords/keywords (for example 'to',
'or', any kind of parenthesis etc.).

#12

Hello folks,

2013.05.26 10:05, khagaroth wrote:

But the search function is broken anyway, it doesn't find half of the
things even if it's "working" and since it uses really awkward syntax, it
treats some common words/chars as stopwords/keywords (for example 'to',
'or', any kind of parenthesis etc.).

FTR, this is http://bugs.locamotion.org/show_bug.cgi?id=2870.

Also another problem are simple characters like
"<, >, =, =>, E, N, Y, PDF, comma sign" etc. It should be copied
automatically.

I'm not exactly sure Mateusz was talking about searching. It seems to me he's suggesting some really 'primitive' strings to be translated automatically, but I don't think this would always work for everyone out there.

Rimas

#13

I´ve found another:

File: svx/uiconfig/ui.po

Context: redlineviewpage.ui position label string.text

Comments: FJfA6

"Postion" instead of "Position"

#14

Στις 25/05/2013 02:52 μμ, ο/η Andras Timar έγραψε:

Migration is done. Hopefully everything is in order for everyone. I
tested Hungarian and it was fine. There are ~4500 UI words and ~4000
help words that need your attention, if you have 100% translated
4.0.x.

Thanks for the typo fixes (recommanded, Toolbare), please report them
here, when you find one.

Thanks,
Andras

In colorpage.ui modellb 1 stringlist.text CYMK or CMYK;

#15

Hi :slight_smile:
The order in English is 'always' CMYK (unless people make a mistake).  That is
Cyan ~ Blue
Magenta ~ Red/purple
Yellow
blacK

I think they use K for black to reduce the chance of confusion!!  I'm not sure if that helps at all or whether thsi is going further off-topic.  I hope it helps otherwise just ignore it. 
Regards from
Tom :slight_smile:

#16

Hi Tom,

Hi :slight_smile:

[...]

I think they use K for black to reduce the chance of confusion!!

K stands usually for Key. See:
http://en.wikipedia.org/wiki/CMYK_color_model
Kind regards
Sophie

#17

Hi :slight_smile:
Thanks Sophie!
Regards from
Tom :slight_smile:

#18

Not suer if this is one typo but I guess so.

File:

svx/source/dialog.po
Context:

ucsubset.src RID_SUBSETMAP RID_SUBSETSTR_YIJING_HEXAGRAM_SYMBOLS string.text
Comments:

TACpT

"Yijing Hexagram Ssymbols "

Double Ss

#19

Hi :slight_smile:
Yes, it's almost definitely a typo.  I can't imagine how it would have been meant deliberately.  That sort of typo is more common in txtin, sometimes emailing.

Regards from
Tom :slight_smile:

#20

Hi,

Thank you all for the typo fixes. I think we found them all, because
many were reported multiple times, and no new was found lately. I
updated Pootle, you can click on the "Update against templates" link.
I'll pull translations from Pootle tomorrow, for 4.1 beta2.

Best regards,
Andras