[Libreoffice-bugs] [Bug 132005] Calc extension fails in LibreOffice (works in Apache OpenOffice)

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=132005

--- Comment #6 from DKG <dkgabi at gmail.com> ---
First, thank you everybody for your input. I tried Julien Nabet’s suggestion,
but it looks like I can’t understand/implement it. Resetting the user profile
partially helped. Indeed, I can see a menu item now, but no toolbar, which
would be great.

I’m the author of the extension. I created the underlying macro in 2015 for use
in conjunction with OmegaT [1], a computer-assisted translation tool [2] (inter
alia, OmegaT is mentioned in the TDF wiki as a tool for LibreOffice
localization [3]) Then, tab-separated text in UTF-8 was the only option for
glossaries that OmegaT could read and still remains the default option for
glossaries that can be amended from within the program. On the other hand,
translators often receive glossaries in spreadsheet files (mainly Excel XLS[X])
requiring export. Exporting to a CSV file may seem to be very easy to the
people here (programmers), but in practice many translators reported (and still
report) problems that appear to be caused by omitting something in the export
options dialog (such as setting nothing for the text delimiter; there is no
such option in the drop-down list, and the user has to manually empty the
respective field, which is not evident). Thus, the idea behind the macro is to
provide a simple tool that can be used by non-experienced users, i. e. with all
the required export options hardcoded. So, if anyone reports a problem with
glossary export, I can say: “Grab the extension and just click on the button
with that nice icon.” (Maybe the icon is not that nice, but I’m not an artist
anyway.)

I tried to pack my macro in an extension. I’m not a programmer and could not
find something like “Idiot’s guide to packaging extensions”, thus, studied
existing extensions and used Basic Addon Builder [4] as an auxiliary tool. I
tested the produced extension (submitted here) to work fine in Apache
OpenOffice and published it in the OmegaT mail group at Yahoo! [5] However, I
could not get it install and run under LibreOffice (it was a fresh install
then). At that time, however, LibreOffice office was too buggy to use anyway,
and I gave up.

I raised this issue here because:
- it is 2020 now, LibreOffice gained wide adoption and I would be happy to see
my extension work in LibreOffice as designed, with a button and a menu item;
- the extension, as mentioned in the initial report, works absolutely fine in
Apache OpenOffice, installs and uninstalls _without any need to reset the user
profile_. Since both Apache OpenOffice and LibreOffice descend from
OpenOffice.org, I thought that the failure of the extension might indicate that
something requires a fix in LibreOffice;
- I was advised by someone more experienced to report the issue [6].

Once again, thank you all for the help. If anyone can give a pointer on how to
enable a custom toolbar, I will be grateful.

[1] https://omegat.org/
[2] https://en.wikipedia.org/wiki/Computer-assisted_translation
[3] https://wiki.documentfoundation.org/Documentation/Development/UsingOmegaT
[4] https://extensions.openoffice.org/project/BasicAddonBuilder
[5] the list moved to SourceForge.net, the respective thread can be found
archived here: https://sourceforge.net/p/omegat/mailman/message/36847659/
[6] https://ask.libreoffice.org/en/question/237500/writer-print-current-page/
(see comments)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200413/3201d64c/attachment-0001.htm>