Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


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


--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.