Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Stefan Monnier]

> committer: Tassilo Horn <tsdh@gnu.org>
> branch nick: trunk
> timestamp: Sat 2013-02-09 10:58:48 +0100
> message:
>   * doc-view.el: Use (and prefer) soffice as default ODF->PDF
>   converter (Bug#13622).  Patch provided by Jambunathan K
>   <kjambunathan@gmail.com>.
>   (doc-view-unoconv-program): Make obsolete variable.
>   (doc-view-odf->pdf-converter-program): New variable.
>   (doc-view-odf->pdf-converter-function): New variable.
>   (doc-view-mode-p): Use it.
>   (doc-view-odf->pdf-converter-unoconv): Rename from
>   `doc-view-odf->pdf-converter-unoconv'.
>   (doc-view-odf->pdf-converter-soffice): New function.
>   (doc-view-convert-current-doc): Use
>   `doc-view-odf->pdf-converter-function'.
> modified:
>   lisp/ChangeLog
>   lisp/doc-view.el

> === modified file 'lisp/ChangeLog'
> --- a/lisp/ChangeLog	2013-02-09 05:52:20 +0000
> +++ b/lisp/ChangeLog	2013-02-09 09:58:48 +0000
> @@ -1,3 +1,18 @@
> +2013-02-09  Tassilo Horn  <tsdh@gnu.org>
> +
> +	* doc-view.el: Use (and prefer) soffice as default ODF->PDF
> +	converter (Bug#13622).  Patch provided by Jambunathan K
> +	<kjambunathan@gmail.com>.
> +	(doc-view-unoconv-program): Make obsolete variable.
> +	(doc-view-odf->pdf-converter-program): New variable.
> +	(doc-view-odf->pdf-converter-function): New variable.
> +	(doc-view-mode-p): Use it.
> +	(doc-view-odf->pdf-converter-unoconv): Rename from
> +	`doc-view-odf->pdf-converter-unoconv'.
> +	(doc-view-odf->pdf-converter-soffice): New function.
> +	(doc-view-convert-current-doc): Use
> +	`doc-view-odf->pdf-converter-function'.

This change log is wrong, since it says you're the author.
It should instead start with

    2013-02-09  Jambunathan K  <kjambunathan@gmail.com>

This said, I have another question: assuming both soffice and unoconv
are installed.  Which of the two is preferable and why (e.g. faster or
gives better output)?


        Stefan

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Glenn Morris]

Stefan Monnier wrote:

> This said, I have another question: assuming both soffice and unoconv
> are installed.  Which of the two is preferable and why (e.g. faster or
> gives better output)?

IIUC, unoconv depends on soffice and is a small utility whose sole
purpose is to convert file formats. So if someone has installed it, they
probably want to use it for that.

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Glenn Morris]

Glenn Morris wrote:

> IIUC, unoconv depends on soffice and is a small utility whose sole
> purpose is to convert file formats. So if someone has installed it, they
> probably want to use it for that.

PS I think it's impossible to have unoconv without soffice, so this
change amounts to "always use soffice".

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Bastien]

Glenn Morris <rgm@gnu.org> writes:

> Glenn Morris wrote:
>
>> IIUC, unoconv depends on soffice and is a small utility whose sole
>> purpose is to convert file formats. So if someone has installed it, they
>> probably want to use it for that.
>
> PS I think it's impossible to have unoconv without soffice, so this
> change amounts to "always use soffice".

I'm not sure I get the logic here: you need to have soffice installed
if you want to use unoconv, but being able to use unoconv instead of
soffice is good.  So as I understand it, the change does not amount
to "always use soffice", does it?

-- 
 Bastien

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Glenn Morris]

Bastien wrote:

>> PS I think it's impossible to have unoconv without soffice, so this
>> change amounts to "always use soffice".
>
> I'm not sure I get the logic here: you need to have soffice installed
> if you want to use unoconv, but being able to use unoconv instead of
> soffice is good.  So as I understand it, the change does not amount
> to "always use soffice", does it?

(cond
   ((executable-find "soffice") "soffice")
   ((executable-find "unoconv") "unoconv")
   (t "soffice"))

It is impossible for this to return anything but "soffice".
IMO it should be:

(or (executable-find "unoconv") "soffice")

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Jambunathan K]

Glenn Morris <rgm@gnu.org> writes:

> Bastien wrote:
>
>>> PS I think it's impossible to have unoconv without soffice, so this
>>> change amounts to "always use soffice".
>>
>> I'm not sure I get the logic here: you need to have soffice installed
>> if you want to use unoconv, but being able to use unoconv instead of
>> soffice is good.  So as I understand it, the change does not amount
>> to "always use soffice", does it?
>
> (cond
>    ((executable-find "soffice") "soffice")
>    ((executable-find "unoconv") "unoconv")
>    (t "soffice"))
>
> It is impossible for this to return anything but "soffice".
> IMO it should be:
>
> (or (executable-find "unoconv") "soffice")

I didn't put deliberate thought in what the order should be.

My patch WILL require tweaks on a case-by-case basis. My immediate focus
was to get the functionality in.  I invite people with commit access to
fix "minor issues" without much ado.

soffice comes from libreoffice-common
    ,----
    | kjambunathan@debian-6:~$ dpkg -S /usr/bin/soffice
    | libreoffice-common: /usr/bin/soffice
    `----

unoconv does NOT depend on libreoffice-common
    ,----
    | kjambunathan@debian-6:~$ apt-rdepends unoconv | grep libre
    | Reading package lists... Done
    | Building dependency tree       
    | Reading state information... Done
    |   Depends: libreadline6 (>= 6.0)
    | libreadline6
    `----

unoconv instread depends on openoffice.org packages
    ,----
    | kjambunathan@debian-6:~$ apt-rdepends unoconv | grep office
    | Reading package lists... Done
    | Building dependency tree       
    | Reading state information... Done
    |   Depends: openoffice.org-core (= 1:3.2.1-11+squeeze7)
    | openoffice.org-core
    |   Depends: openoffice.org-common (>> 1:3.2.1)
    | openoffice.org-common
    |   Depends: openoffice.org-style
    |   Depends: openoffice.org-style-default
    | openoffice.org-style
    | openoffice.org-style-default
    `----

I see an soffice.sh in /etc/openoffice/soffice.sh

    ,----
    | kjambunathan@debian-6:~$ dpkg -L openoffice.org-common
    | /etc
    | /etc/bash_completion.d
    | /etc/bash_completion.d/ooffice.sh
    | /etc/openoffice
    | /etc/openoffice/sofficerc
    | /etc/openoffice/psprint.conf
    | /etc/openoffice/soffice.sh
    | kjambunathan@debian-6:~$ 
    `----




>
>

-- 

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Stephen J. Turnbull]

From the unoconv home page:

    Requirements
    unoconv is written in python. It needs a recent LibreOffice or
    OpenOffice with UNO bindings.

For what it's worth, Jambunathan K writes:

 > unoconv does NOT depend on libreoffice-common

Always cross-check what a package manager tells you for this kind of
information.  Package managers have completely different model of the
world from humans.

 > >> I'm not sure I get the logic here: you need to have soffice
 > >> installed if you want to use unoconv, but being able to use
 > >> unoconv instead of soffice is good.

That's true for the *user* at the command line, but for Emacs it
depends on how unoconv is being used.  If the UI provides a Swiss Army
knife able to convert any given format to any other by delegating the
format grokking to unoconv, yes, it's sort of good, assuming that
Emacs will never pass incorrect arguments to unoconv.[1]  In that case
unoconv (and any other "universal converters") should be tried only
after specific converters that do a better job are tried.[2]

If in fact what happens is that Emacs parses the formats and only
handles formats that it recognizes, unoconv is useless to Emacs.  (I
suspect this is rarely what most users want[3], but I prefer it.  If
Emacs can't do a good job automatically, it should leave it up to me!)

Footnotes: 
[1]  It's OK if Emacs passes arguments that unoconv *can't* convert;
what I'm referring to here is a situation where unoconv could convert
if given certain information that Emacs does know in the correct
format, but because Emacs's "generic" invocation of unoconv either
fails to provide the information, or fails to invoke the command with
correct syntax, the command fails.

[2]  There may be none.  Seems unlikely to me though, given how
horribly unreliable even Microsoft Office software is for producing
high-quality output across platforms.

[3]  IME most users will accept any garbage that comes out as long as
a program has generated it because they're happy to blame the program
if somebody bitches about poor quality.

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Tassilo Horn]

"Stephen J. Turnbull" <stephen@xemacs.org> writes:

>  > >> I'm not sure I get the logic here: you need to have soffice
>  > >> installed if you want to use unoconv, but being able to use
>  > >> unoconv instead of soffice is good.
>
> That's true for the *user* at the command line, but for Emacs it
> depends on how unoconv is being used.  If the UI provides a Swiss Army
> knife able to convert any given format to any other by delegating the
> format grokking to unoconv, yes, it's sort of good, assuming that
> Emacs will never pass incorrect arguments to unoconv.[1] In that case
> unoconv (and any other "universal converters") should be tried only
> after specific converters that do a better job are tried.[2]
>
> If in fact what happens is that Emacs parses the formats and only
> handles formats that it recognizes, unoconv is useless to Emacs.  (I
> suspect this is rarely what most users want[3], but I prefer it.  If
> Emacs can't do a good job automatically, it should leave it up to me!)

Ok, to clear up the situation a bit: unoconv is probably more powerful
than soffice.  For example, it is possible to run it as a server that
accepts conversion requests from multiple clients.  doc-view doesn't
need that.

doc-view just uses either unoconv or soffice to convert OpenDocument or
Microsoft Office documents to PDF.  Both tools can do that just fine,
and they use the same LibreOffice/OpenOffice internal APIs for the job.

I've converted some example documents with both of them, and the output
is almost identical: identically displayed, identical with respect to
file size of the generated PDF, but diff says they differ nonetheless.

However, soffice is appoximately 2.5 to 7 times faster.  It seems that
unoconv has some significant startup overhead compared to soffice.  I
hadn't expected that, but in the end it justifies that soffice is picked
up by default when both soffice and unoconv are installed on a system.

Bye,
Tassilo

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Tassilo Horn]

Tassilo Horn <tsdh@gnu.org> writes:

> Ok, to clear up the situation a bit: unoconv is probably more powerful
> than soffice.  For example, it is possible to run it as a server that
> accepts conversion requests from multiple clients.  doc-view doesn't
> need that.
>
> doc-view just uses either unoconv or soffice to convert OpenDocument
> or Microsoft Office documents to PDF.  Both tools can do that just
> fine, ...

Now I've found a more serious issue with soffice.  It doesn't work when
there's already a running LibreOffice instance.  In that case, it simply
finishes successfully without doing anything.  That's already reported
as a bug:

    https://bugs.freedesktop.org/show_bug.cgi?id=37531

Reading that report, it doesn't seem likely to be fixed anytime soon,
and even then it'll take time until the buggy versions won't be used
anymore.

Fortunately, there's also a workaround.  By default, LibreOffice use the
directory ~/.config/libreoffice/<major-version>/ for storing
customizations, scripts, settings, etc.  This can be overridden using
the undocumented -env:UserInstallation option, and when using separate
UserInstallation directories per invocation, it works just fine.

I've just committed a change that adds the option

    -env:UserInstallation=file:///tmp/libreoffice-docview<tmp-suffix>

to the options passed to soffice.  This seems to add about 0.5 seconds
to the ODF->PDF conversion time, but that's still much faster than
unoconv.

These temporary directories are deleted immediately after the conversion
has finished in order not to clutter the filesystem with lots of 1.7MB
dirs.

Bye,
Tassilo

Re: [Emacs-diffs] /srv/bzr/emacs/trunk r111707: * doc-view.el: Use (and prefer) soffice as default ODF->PDF

[Tassilo Horn]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> +	* doc-view.el: Use (and prefer) soffice as default ODF->PDF
>> +	converter (Bug#13622).  Patch provided by Jambunathan K
>> +	<kjambunathan@gmail.com>.
>
> This change log is wrong, since it says you're the author.
> It should instead start with
>
>     2013-02-09  Jambunathan K  <kjambunathan@gmail.com>

Thanks for fixing that.

> This said, I have another question: assuming both soffice and unoconv
> are installed.  Which of the two is preferable and why (e.g. faster or
> gives better output)?

Both use the same Libreoffice internal conversion facilities, so their
output and speed are the same.  The only difference is that soffice is
part of every LibreOffice installation whereas unoconv is some external
utility that probably almost nobody has installed.

Bye,
Tassilo