More Pootle news: NLPSolver localization enabled for ru, oc, ko, en_GB, ja; libo33_test project deleted

l10n
#1

Hello,

I took liberty to enable translating the NLPSolver extension for a few more languages: ru, oc, ko, en_GB, ja. All these languages belong to the top 10 in libo33 project, and all except ja have libo33 translated fully. Note that this does not mean you necessarily have to translate the extension, but I just thought that maybe you would, upon seeing new translatable content. :wink:

Also, to help avoid confusion, I decided to remove the libo33_test project from Pootle. All its files are backed up, just in case, but it won't be visible and translatable in Pootle anymore.

Best regards,
Rimas

#2

Thanks Rimas, but I don't seem to have translate permissions for the en-GB extensions!

Stuart

#3

Hi Rimas, all,

Hello,

I took liberty to enable translating the NLPSolver extension for a few
more languages: ru, oc, ko, en_GB, ja.

ah! welcome to the very strange world of the NLP solver :slight_smile:

All these languages belong to the

top 10 in libo33 project, and all except ja have libo33 translated
fully. Note that this does not mean you necessarily have to translate
the extension, but I just thought that maybe you would, upon seeing new
translatable content. :wink:

thanks, I find it always motivating to have red bars on Pootle :wink:

Also, to help avoid confusion, I decided to remove the libo33_test
project from Pootle. All its files are backed up, just in case, but it
won't be visible and translatable in Pootle anymore.

It's a really good idea, we do not need these files any more. Thanks again for taking care :slight_smile:

Kind regards
Sophie

#4

Hi Stuart,

2010.12.26 20:11, Stuart Swales rašė:

Thanks Rimas, but I don't seem to have translate permissions for the en-GB extensions!

Stuart

Whoops! It's fixed now. I made you the admin for en_GB itself, not just for a particular project.

Rimas

#5

Hi Sophie,

2010.12.26 20:35, Sophie Gautier rašė:

All these languages belong to the top 10 in libo33 project, and all except ja have libo33 translated
fully. Note that this does not mean you necessarily have to translate
the extension, but I just thought that maybe you would, upon seeing new
translatable content. :wink:

thanks, I find it always motivating to have red bars on Pootle :wink:

Yep, that's exactly my point! :slight_smile:

Also, to help avoid confusion, I decided to remove the libo33_test
project from Pootle. All its files are backed up, just in case, but it
won't be visible and translatable in Pootle anymore.

It's a really good idea, we do not need these files any more. Thanks again for taking care :slight_smile:

My pleasure. :slight_smile:

Rimas

#6

NLPSolver extension is fully translated on Russian now. Please somebody
commit files from pootle.

And little question: Is "LibO 3.3 Documentation (TESTING)" need for
translate?

#7

Hi,

2011.01.21 00:11, Aidsoid rašė:

NLPSolver extension is fully translated on Russian now. Please somebody
commit files from pootle.

Andras will do it, I suppose.
Andras, please check the naming though. I didn't notice when initializing languages through Pootle's interface that the files were initialized as *-lang.properties instead of *_lang.properties.

And little question: Is "LibO 3.3 Documentation (TESTING)" need for
translate?

It is what it says it i – a testing project. As we've already figured out, translating it in Pootle is not possible due to the lack of proper XLIFF support in Pootle. You may however download the files and translate them offline using one of the tools that work well with XLIFF, e.g. Virtaal (btw I heard a new version of it is on its way to be released).

Sophie, do you want to add anything?

Rimas

#8

Yeah, I noticed it. See
http://cgit.freedesktop.org/libreoffice/extensions/tree/nlpsolver/locale?h=libreoffice-3-3
There is another odd thing. You updated Pootle to a newer version, if
I remember correctly. After this update, .properties files are
exported as utf-8 instead of ascii escaped unicode. Not a big deal, I
reconverted the files. I'm not sure, if Java can process utf-8 encoded
properties (it's not Mozilla :)).
I'll add new translations of course.

Best regards,
Andras