Hejsan,
so I'm trying to localize a dialog in an extension I'm writing and for some reason it's never being
picked up. Any suggestions would be welcome. As since involves magic files and there is no error
whatsoever this is hard to tackle.
This is the documentation I followed:
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Creating_the_GUI_of_the_Options_Page
http://wiki.services.openoffice.org/wiki/API/Samples/Java/Office/OptionsPageDemo
So this is my checklist for how to do it from how I understood it:
- ConfigDialog.xdl
<dlg:window dlg:id="ConfigDialog"...>...
<dlg:button dlg:id="SaveButton" dlg:value="0.ConfigDialog.SaveButton.Label"...>
- ConfigDialog_en_US.default - empty
- ConfigDialog_en_US.properties
0.ConfigDialog.SaveButton.Label=Save
- ConfigDialog_fr_FR.properties
0.ConfigDialog.SaveButton.Label=Sauvegarder
I made sure to use CamelCase everywhere, just in case that made a difference.
All files install next to each other, relative to the extension root. I tested both installing it
in my personal folder as well as system-wide.
Incidentally I used the Dialog editor to create a reference test file as well, I found no way to
insert local strings, and it crashed on export. Then I manually added strings to the files inside
~/.libreoffice and then I was able to export - it just copied the files anyway. Even worse, I'm
also unable to open my files in the editor...
--
ciao,
Christian
Context
- [Libreoffice] Localization of an extension (dialog) · Christian Dywan
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.