![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
Hi L10N Gurus,
Can you upload translation files for all supported extensions. I can
help to collect localizable files for extensions.
Best regards,
KAMI
Hi Kalman,
2010.12.27 20:30, Kálmán „KAMI” Szalai rašė:
Can you upload translation files for all supported extensions. I can
help to collect localizable files for extensions.
sure I can, if someone collects those files. I have no idea where to look for them or time to do that...
Rimas
Started to collect them.
KAMI
2010-12-27 20:14 keltezéssel, Rimas Kudelis írta:
Hi!
Sorry for the delay.
I uploaded the collection of properties files here:
http://ooo.itc.hu/libreoffice/localization/extension_translation_20110122_1.zip
Please put it into the Pootle, and if it possible I would like to get
access for Hungarian parts.
Thank you in advance!
KAMI
2010-12-29 10:03 keltezéssel, Kálmán „KAMI” Szalai írta:
Hi all,
the shipped extensions are now ready for online localization in Pootle. If anything got broken during the process (e.g. your translation of NLPSolver was erased), please inform me about it, and I apologise in advance. It shouldn't be the case though, unless you translated NLPSolver today.
If your language is missing in the list, but you want to localize translations, please ping me, and I'll initialize the project for you.
Best regards,
Rimas
2011.01.22 12:52, Kálmán „KAMI” Szalai rašė:
2011.01.23. 20:59 keltezéssel, Rimas Kudelis írta:
Hi all,
the shipped extensions are now ready for online localization in Pootle.
If anything got broken during the process (e.g. your translation of
NLPSolver was erased), please inform me about it, and I apologise in
advance. It shouldn't be the case though, unless you translated
NLPSolver today.
Hi Rimas,
I checked only a few files but they did not look OK.
http://translations.documentfoundation.org/fr/extensions/watchwindow/WWindow_fr.properties/translate/
French is the source language (with wrong encoding) and English is the
target.
http://translations.documentfoundation.org/is/extensions/watchwindow/WWindow-is.properties/translate/
Translation is prefilled with English strings.
http://translations.documentfoundation.org/hu/extensions/watchwindow/WWindow-hu.properties/translate/
Hungarian is the source language and English is the target.
Best regards,
Andras
2011.01.23 22:14, Andras Timar rašė:
2011.01.23. 20:59 keltezéssel, Rimas Kudelis írta:
Hi all,
the shipped extensions are now ready for online localization in Pootle.
If anything got broken during the process (e.g. your translation of
NLPSolver was erased), please inform me about it, and I apologise in
advance. It shouldn't be the case though, unless you translated
NLPSolver today.Hi Rimas,
I checked only a few files but they did not look OK.
http://translations.documentfoundation.org/fr/extensions/watchwindow/WWindow_fr.properties/translate/
French is the source language (with wrong encoding) and English is the
target.http://translations.documentfoundation.org/is/extensions/watchwindow/WWindow-is.properties/translate/
Translation is prefilled with English strings.http://translations.documentfoundation.org/hu/extensions/watchwindow/WWindow-hu.properties/translate/
Hungarian is the source language and English is the target.
Doh, I'll recheck. Sorry.
Rimas
2011.01.23 22:23, Rimas Kudelis rašė:
2011.01.23 22:14, Andras Timar rašė:
2011.01.23. 20:59 keltezéssel, Rimas Kudelis írta:
Hi all,
the shipped extensions are now ready for online localization in Pootle.
If anything got broken during the process (e.g. your translation of
NLPSolver was erased), please inform me about it, and I apologise in
advance. It shouldn't be the case though, unless you translated
NLPSolver today.Hi Rimas,
I checked only a few files but they did not look OK.
French is the source language (with wrong encoding) and English is the
target.Translation is prefilled with English strings.
Hungarian is the source language and English is the target.
Doh, I'll recheck. Sorry.
OK, I deleted the project and created it again. It looks better now.
Note for Sophie: the original watchwindow translation was encoded incorrectly, so all accented French characters are now encoded incorrectly.
Notes to Andras:
Regarding the way .properties files are now encoded: I was told that keeping them unescaped was a very popular feature request. The suggestion was to simply escape them properly during compilation. Would that be possible?
Also, I'd love to see some unity in the way files are named, that is:
* the file in default locale (en-US) should be named file.properties (not file_en_US.properties or file_en.properties).
* localized files should be named file_ll.properties or file_ll_CC.properties, the code should be the same as that of LibO (file_fr.properies, and not file_fr_FR.properties).
Is there any chance to apply this simple principle to all the extensions we're shipping?
Rimas
Hi Rimas,
Could you please initialize eu?
Regards,
Mikel
I see lots of empty strings in the "extensions" project (all languages)
Is that ok?
Should we start translating, or should we wait for any fix?
Mikel
2011.01.24 00:30, Mikel Pascual rašė:
I see lots of empty strings in the "extensions" project (all languages)
Is that ok?
Should we start translating, or should we wait for any fix?
If you are talking about the WatchWindow, there's not much that I can do. Those strings are empty in English. From their identifiers, I assume they are the tooltips appearing above certain UI elements.
Since for the first one, the file comment is shown instead of the identifier, its identifier is: 296.WWindow.HelpText. By the way, you can always download that particular file and translate it offline, or at least keep it as a reference in another window. To do that, you'd go to watchwindow's review tab and click on export.
Rimas
2011.01.23. 22:54 keltezéssel, Rimas Kudelis írta:
Notes to Andras:
Regarding the way .properties files are now encoded: I was told that
keeping them unescaped was a very popular feature request. The
suggestion was to simply escape them properly during compilation. Would
that be possible?
I bet it was a request from Mozilla localizers. However, standard Java
.properties files can be either in Escaped Unicode or in ISO-8859-1.
UTF-8 is not allowed. Nevertheless, I can convert the files.
With regards to compilation: in fact these extensions are external to
LibreOffice source code. I need to check if they are compiled at all.
Maybe some of them are just bundled (not by default!) in the installer.
Also, I'd love to see some unity in the way files are named, that is:
* the file in default locale (en-US) should be named file.properties
(not file_en_US.properties or file_en.properties).
* localized files should be named file_ll.properties or
file_ll_CC.properties, the code should be the same as that of LibO
(file_fr.properies, and not file_fr_FR.properties).Is there any chance to apply this simple principle to all the extensions
we're shipping?
As I wrote above, these extensions are not maintained in the LibreOffice
source tree. Their authors should be contacted.
Please note that except for NLPSolver, these extensions are not shipped
with LibreOffice. They can be configured build time but they are not.
AFAIK only OxygenOffice ships them. LibreOffice may or may not include
them in the future. As LibreOffice tries to get rid of Java dependency,
I would not bet on inclusion of extensions written in Java (e.g.
Diagram, Watch Window, Validator, LanguageTool).
Translation of these extensions are still very useful. Users will like
these extensions in their native language. I just wanted to note that we
cannot easily hack these extensions like we do with the LibreOffice
source code.
Best regards,
Andras
2011.01.24 00:26, Mikel Pascual rašė:
Hi Rimas,
Could you please initialize eu?
Done.
Please not that due to Pootle's glitches, some untranslated strings are actually treated as translated, while indeed your locale is 0% translated so far.
Rimas
2011.01.24 10:37, Andras Timar rašė:
2011.01.23. 22:54 keltezéssel, Rimas Kudelis írta:
Notes to Andras:
Regarding the way .properties files are now encoded: I was told that
keeping them unescaped was a very popular feature request. The
suggestion was to simply escape them properly during compilation. Would
that be possible?I bet it was a request from Mozilla localizers. However, standard Java
.properties files can be either in Escaped Unicode or in ISO-8859-1.
UTF-8 is not allowed. Nevertheless, I can convert the files.
That was my bet too, but apparently, even some Java developers prefer to keep .properties files unescaped in their repositories, and only escape them during compilation (or bundling, whatever).
With regards to compilation: in fact these extensions are external to
LibreOffice source code. I need to check if they are compiled at all.
Maybe some of them are just bundled (not by default!) in the installer.
Again, if there's a step that does SOMETHING with those files, it could be preceded with a step that escapes them first. That's a workflow change, but IMO it's really small, and could be seen as a positive one. Unescaped files are certainly more human-readable than escaped ones.
Also, I'd love to see some unity in the way files are named, that is:
* the file in default locale (en-US) should be named file.properties
(not file_en_US.properties or file_en.properties).
* localized files should be named file_ll.properties or
file_ll_CC.properties, the code should be the same as that of LibO
(file_fr.properies, and not file_fr_FR.properties).Is there any chance to apply this simple principle to all the extensions
we're shipping?As I wrote above, these extensions are not maintained in the LibreOffice
source tree. Their authors should be contacted.Please note that except for NLPSolver, these extensions are not shipped
with LibreOffice. They can be configured build time but they are not.
AFAIK only OxygenOffice ships them. LibreOffice may or may not include
them in the future. As LibreOffice tries to get rid of Java dependency,
I would not bet on inclusion of extensions written in Java (e.g.
Diagram, Watch Window, Validator, LanguageTool).Translation of these extensions are still very useful. Users will like
these extensions in their native language. I just wanted to note that we
cannot easily hack these extensions like we do with the LibreOffice
source code.
Well, I assume that since we're translating those extensions, we're in touch with their authors, no? 
Rimas
Hi all,
Pootle has some really weird bugs (or maybe they're actually my bugs....). I was pretty sure yesterday that when I updated the extensions project from templates, all languages had 22 files to translate, but today I saw smaller numbers.
I've rescanned the templates and updated the project from them again. I hope nothing got broken, but please inform me if I'm wrong.
Rimas
Hi!
2011-01-24 11:12 keltezéssel, Rimas Kudelis írta:
Well, I assume that since we're translating those extensions, we're in
touch with their authors, no?
I keep in touch all developers who related these extensions except
Daniel, the LanguageTool author. He is active around the LibO.
So I am sure every translated lines will find their path to the right
extension.
Also I am planing to add all extension that listed in LibreOffice
extension page.
KAMI
Hi!
2011-01-23 22:54 keltezéssel, Rimas Kudelis írta:
2011.01.23 22:23, Rimas Kudelis rašė:
2011.01.23 22:14, Andras Timar rašė:
2011.01.23. 20:59 keltezéssel, Rimas Kudelis írta:
Hi all,
the shipped extensions are now ready for online localization in
Pootle.
If anything got broken during the process (e.g. your translation of
NLPSolver was erased), please inform me about it, and I apologise in
advance. It shouldn't be the case though, unless you translated
NLPSolver today.Hi Rimas,
I checked only a few files but they did not look OK.
French is the source language (with wrong encoding) and English is the
target.Translation is prefilled with English strings.
Hungarian is the source language and English is the target.
Doh, I'll recheck. Sorry.
OK, I deleted the project and created it again. It looks better now.
Note for Sophie: the original watchwindow translation was encoded
incorrectly, so all accented French characters are now encoded
incorrectly.Notes to Andras:
Regarding the way .properties files are now encoded: I was told that
keeping them unescaped was a very popular feature request. The
suggestion was to simply escape them properly during compilation.
Would that be possible?
However UTF-8 in properties is not standard but very popular. So I hope
this will be standardised for every tool using properties file.
Also, I'd love to see some unity in the way files are named, that is:
* the file in default locale (en-US) should be named file.properties
(not file_en_US.properties or file_en.properties).
file_en_US and in general file_ll-CC is the method how LibreOffice
localizes a window if you use the build in localization mechanism.
* localized files should be named file_ll.properties or
file_ll_CC.properties, the code should be the same as that of LibO
(file_fr.properies, and not file_fr_FR.properties).
I will check files, and ask developer to be more consequent here.
Is there any chance to apply this simple principle to all the
extensions we're shipping?
Rimas
KAMI
Hi KAMI,
2011.01.24 12:34, Kálmán „KAMI” Szalai rašė:
Also, I'd love to see some unity in the way files are named, that is:
* the file in default locale (en-US) should be named file.properties
(not file_en_US.properties or file_en.properties).file_en_US and in general file_ll-CC is the method how LibreOffice
localizes a window if you use the build in localization mechanism.
What I meant here is that since en-US is the base locale, its files should IMO not carry the locale code at all. What I've seen among the extensions you sent me is:
a) some of them do exactly that – have file.properties
b) others have file_en_US.properties and an empty file_en_US.default file
c) others just have file_en_US.properties, without the .default file
I hope we can persuade all extension authors to go with option a)
Thanks for your input and help!
Rimas
Hi all,
AFAIK LanguageTool uses its own translation process, I don't have the link
at hand, but there is a free web translation service/system that hosts it.
So it is probably not OK to duplicate the work here. I guess there could be
a link to stats of that extension/server on the LO Pootle.
Or, if Daniel is OK with it, he can someday move it to the LO Pootle.
Anyway, I would like to reiterate my suggestion - a system like BabelZilla
(for Ff/Th) mixed with extensions.services.openoffice.org - a hosting system
for translations of extensions AND extensions themselves to download,
promote (including downloads and localization of templates) - all under
(L)GPL or other open licenses. The current hosting of those properties files
in LO Pootle can be seen as an interim step in that direction...
It could be called "LibreExtensions" or "LibreAddons" or "LibreTools" or
whatever. The marketing team could come up with an idea. Maybe
tutorials/documentation could be made a part of it.
If LO gets online as a web service someday, this server should be
well-thought-through also in that direction - could the hosted extensions be
activated per user per session/account in the web-service version of LO?
Wow, just got blue screen because of all the possibilities here...
Lp, m.
Hi,
I created po files from properties files.
You can download it from here:
http://ooo.itc.hu/libreoffice/localization/extension_translation_20110129_1.zip
Is it better for us?
KAMI
2011-01-24 15:11 keltezéssel, Martin Srebotnjak írta: