On 03/11/11 00:13, Andras Timar wrote:
2011/11/2 Michael Stahl<mstahl@redhat.com>:
On 02/11/11 11:34, Andras Timar wrote:
Hi,
I developed a small feature. Now localization tools can extract
extension name and description from description.xml of our bundled
extensions (dictionaries, PDF Import, etc.). Translators will
translate them, so they will be localized in Extension Manager window.
For dmake modules I tweaked the makefiles so merging of translations
work. But I have never worked with gnu make makefiles and two modules
(swext and scripting) are using them.
I would appreciate, if someone could help and could write the gnu make
rules for this.
i can take a look at it tomorrow...
forgot to say that i did this last week, please try it out:
http://cgit.freedesktop.org/libreoffice/core/commit/?id=fddb39b14df1e3dcb6e42c206547b095cc65853e
btw, i have also added a description for the python extension:
http://cgit.freedesktop.org/libreoffice/core/commit/?id=4570fe5875d539aa92eee0e8f247862b7ad97636
does anything special need to be done when changing/adding UI strings,
or is that stuff done automagically nowadays?
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.