In moving to LO3.3 I understood that writer2latex would be incorporated,
but the export options on OSX that would be available are not included
(in fact there are only two export format options as compared to the
extensive list I am used to under OOo)
In any event, I had changed the <vendor> java tag in my OSX 3.3
installation so that zotero plugin worked (it still works under 3.3.1)
and then upgraded via overlay install to 3.3.1
I then download the current extension package for writer2latex and
mistakenly added its zip to LO (as I recall this feature - adding from
zip as opposed to oxt - worked in OOo) however, apparently the zip is
not just a zip of an oxt and at this point a) I can't remove that zip
from the extension manager, and b) I now get a java error when trying to
add the oxt files ([Java framework] Error in function getPluginLibrary
Newer installs show up as in extension manager but not working and they
can be removed, but I can't fully install any oxt files and the
writer2latex zip still can't be removed....
Can someone tell me what I can do to manually delete and rebuild the
listing or otherwise clean the extension list, and resolve the java
error b arring the install of new oxt files...
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
Context
- [libreoffice-users] writer2latex and java errors on LO 3.3.1 on OSX 10.6 · Marc Grober
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.