2010/11/6 KAMI911 KAMI911 <kami911@gmail.com>
Hi!
It is not easy to steamlined the extension that comes from outside
(downloadable oxt). Maybe we can put po files to Pootle then the
translators
can can do their tasks easily. We can convert it back to properties file
and
send it to the developer or directly inject to the oxt (zip files).
Right.
Or there is another way. We can ask the developers to join their code into
the LO codebase/tree, so other developers can improve their extensions etc.
and thus the localization of these extensions becomes a part of LO
translation process.
Even better: since the mixture of truly open and commercial extensions on
the extensions.services.openoffice.org site was a concern for the promotors
of open source, LO should in the long run offer a platform like that for
open source only extensions, but could additionally offer also the code
repository and a UI localization interface just like the one at Babelzilla
for Mozilla extensions. That would be best in my opinion.
LP, m.
--
E-mail to l10n+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/l10n/
All messages you send to this list will be publicly archived and cannot be deleted
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.