Comment 5 for bug 889735

On Mon, 14 Nov 2011, John Pye wrote:

> Further followup: I found that if I already have LibreOffice running, I
> don't get these errors. Seems that unoconv is invoking a headless
> version of libreoffice, then closing it if no longer needed. When I have
> open documents, it doesn't close (or open) a new LO hence no error.
>
> My script is just a Python script that invokes 'unoconv' over and over
> with different files, outputting each as text to stdout.

Hi,

I am the author of unoconv.

LibreOffice changed the options (from short options to long options)
recently and while completely innocent (because they provided backward
compatibility) it is at least annoying to see it complain about this. I
can not surpress this because it might as well be outputting an important
warning or fatal error to the user.

The real problem is that there is no good/simple solution. Either I
support only the latest LibreOffice versions, or you get this error.

There is one possible work-around, since unoconv already has the UNO
bindings loaded, there might be a way to retrieve the exact version from
UNO (without needing LibreOffice/OpenOffice). I need to investigate if
that is at all possible.

Pull-requests are appreciated at:

     http://github.com/dagwieers/unoconv

;-)
--
-- dag wieers, <email address hidden>, http://dag.wieers.com/
-- dagit linux solutions, <email address hidden>, http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]