On 11/30/2011 09:27 AM, Leif Lodahl wrote:
Thanks Andrew,
Please send me your ideas and examples.
I sent you a full copy of the source used to create an extension,
complete with the extension as well. Notice all the bits and pieces. To
build it, extract the TAR file into a directory and then open the ODT
file. The ODT file contains things to drive the creation. Also, look in
Module1 of the Standard module.
This contains numerous things including menus for different locales.
There is also a dialog, and you can see bits and pieces of files used
for the localization in the tar file.
When you are ready to build, simply run module1 from the Standard
library and it will create the OXT file.
My idea is also to use it in an extension.
I have upload my ides of an extension here
http://blog.magenta-aps.dk/wp-content/uploads/2011/11/Review.oxt .
The extension creates a new toolbar called Review. The right most icon
starts a macro with a dialog that is localized (so far only English and
Danish is included). All localization stuff is in the module "Localization".
Problems so faris:
- When I read the DialogStrings_xx_YY.properties i have some problems
with encoding. Only files created on the same platform shows right (Danish
language consist of some non-ascii characters æ, ø and å.
Currently this reads with wrong encoding on Windows (use Danish version
to see the problem).
How can that be solved?
- Effectiveness. I'm not sure this is the most effective way and I'm
affraid that with many strings it will run slow. I haven't tried with more
than these very few strings.
Ahhh, I can perhaps take a look, but it is already 3:00 AM and I must be
up early for work.
Missing work to be done (not problems)
- Error handling
- Better way to load only relevant strings (only partly implemented so
far)
- Default language should be from DialogString_xx_YY.default and not
hardcoded
- Script to generate Addons.xcu and /Office/UI/XYZWindowState.xcu
Feel free to tell me what you think of my solution.
Cheers,
Leif Lodahl
The Danish Team
2011/11/30 Andrew Douglas Pitonyak<andrew@pitonyak.org>
On 11/29/2011 03:37 AM, Leif Lodahl wrote:
Hi all,
I often need to have text strings other that dialog labels. This can be
error messages, status line messages and msgbox() text.
Does anyone here has experience with developing localizable macros?
It is possible to localize dialogs, the but is there a some kind of best
practice method to access these strings from a Basic macro?
I have found a way to do it, but if there is an official way of doing it,
I
would like to hear about it.
Cheers,
Leif Lodahl
I have only done this in extensions. I can send you an example if you
desire..... But... I need to take a dog out to go to the bathroom.
--
Andrew Pitonyak
My Macro Document:
http://www.pitonyak.org/**AndrewMacro.odt<http://www.pitonyak.org/AndrewMacro.odt>
Info: http://www.pitonyak.org/oo.php
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.**
org<users%2Bhelp@global.libreoffice.org>
Problems? http://www.libreoffice.org/**get-help/mailing-lists/how-to-**
unsubscribe/<http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/>
Posting guidelines + more: http://wiki.**documentfoundation.org/**
Netiquette<http://wiki.documentfoundation.org/Netiquette>
List archive:
http://listarchives.**libreoffice.org/global/users/<http://listarchives.libreoffice.org/global/users/>
All messages sent to this list will be publicly archived and cannot be
deleted
--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
Info: http://www.pitonyak.org/oo.php
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-users] Localization of macros (continued)
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.