From: Tassilo Horn <tassilo@member.fsf.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Re: DocView now supports OpenDocument & MS Office formats
Date: Fri, 06 May 2011 18:09:35 +0200 [thread overview]
Message-ID: <871v0bkdz4.fsf@member.fsf.org> (raw)
In-Reply-To: <81iptn4zik.fsf@gmail.com> (Jambunathan K.'s message of "Fri, 06 May 2011 21:00:59 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
Hi Jambunathan,
> I am wondering whether it would be possible to *not* make the unoconv
> the default converter.
>
> Speaking for myself, I had troubling getting unoconv-0.4 to work on my
> Windows box right from the way go - mostly due to limited patience and
> ignorance of python runtime. But I had better luck with using
> OpenOffice.Org's Basic macros to convert my odt files to pdf [1].
I have no experience with OO macros, but if that works then it's clearly
better than requiring an external tool with python dependencies.
Does that macro work for all files supported by OO.org/LibreOffice or is
it only for OOWriter? (Your script calls oowriter and the macro
ConvertWordToPDF...)
> So, may I propose following minor changes to doc-view.el?
>
> Make doc-view-unoconv-program to be either an executable (as is now)
> or a function pointer with the same signature as (defun
> doc-view-odf->pdf (odf callback) ...) with one another argument that
> says where the resulting pdf file need to be produced.
Yes, please go ahead. Thereby, doc-view-unoconv-program should be
renamed to doc-view-odf-converter or something like that.
Bye,
Tassilo
next prev parent reply other threads:[~2011-05-06 16:09 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 14:07 DocView now supports OpenDocument & MS Office formats Tassilo Horn
2010-12-30 14:30 ` Drew Adams
2010-12-30 14:50 ` Tassilo Horn
2010-12-30 15:40 ` Stefan Monnier
2010-12-30 15:48 ` Tassilo Horn
2010-12-30 16:04 ` Stefan Monnier
2010-12-30 18:10 ` Tassilo Horn
2011-05-06 15:30 ` Jambunathan K
2011-05-06 16:09 ` Tassilo Horn [this message]
2010-12-30 15:22 ` Tassilo Horn
2010-12-30 16:02 ` Stefan Monnier
2010-12-30 17:20 ` Tassilo Horn
-- strict thread matches above, loose matches on Subject: below --
2010-12-30 22:32 MON KEY
2010-12-30 22:59 ` Jason Rumney
2010-12-31 2:12 ` MON KEY
2010-12-31 8:35 ` Tassilo Horn
2010-12-31 9:25 ` Eli Zaretskii
2010-12-31 11:33 ` Tassilo Horn
2011-01-02 0:33 ` Richard Stallman
2011-01-02 7:29 ` MON KEY
2011-01-02 22:11 ` Richard Stallman
2011-01-03 4:14 ` Stephen J. Turnbull
2011-01-04 4:08 ` Richard Stallman
2011-01-04 4:35 ` Drew Adams
2011-01-04 5:33 ` Stephen J. Turnbull
2011-01-03 8:25 ` MON KEY
2011-01-04 4:08 ` Richard Stallman
2011-01-03 8:42 ` Tassilo Horn
2011-01-04 4:08 ` Richard Stallman
2011-01-04 7:38 ` Tassilo Horn
2011-01-04 8:18 ` Eli Zaretskii
2011-01-04 9:00 ` Tassilo Horn
2011-01-04 11:58 ` Eli Zaretskii
2011-01-05 19:42 ` Eduard Wiebe
2011-01-06 18:42 ` Richard Stallman
2011-01-07 11:18 ` Eli Zaretskii
2011-01-08 21:54 ` Eduard Wiebe
2011-01-09 4:02 ` Eli Zaretskii
2011-01-09 20:00 ` Richard Stallman
2011-01-09 20:13 ` Eduard Wiebe
2011-01-04 20:36 ` Richard Stallman
2011-01-04 21:07 ` Jambunathan K
2011-01-05 15:04 ` Tom Tromey
2011-01-04 21:17 ` Tassilo Horn
2011-01-05 2:02 ` Stephen J. Turnbull
2011-01-05 7:38 ` Tassilo Horn
2011-01-05 12:11 ` Stephen J. Turnbull
2011-01-20 7:32 ` Kevin Rodgers
2011-05-06 12:53 ` Jambunathan K
2011-01-05 23:37 ` Richard Stallman
2011-01-06 7:19 ` Tassilo Horn
2011-01-04 21:52 ` Lennart Borgman
2011-01-05 5:23 ` Miles Bader
2011-01-05 7:40 ` Tassilo Horn
2011-05-06 14:01 ` Jambunathan K
2011-01-03 13:04 ` CHENG Gao
2011-01-03 14:14 ` Tassilo Horn
2011-01-04 4:07 ` Richard Stallman
2011-01-02 22:11 ` Richard Stallman
2010-12-31 8:08 ` Tassilo Horn
2010-12-31 16:43 ` Stefan Monnier
2011-01-01 0:06 ` MON KEY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871v0bkdz4.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).