From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: on the fragility of export to ODT
Date: Wed, 18 Feb 2015 15:04:52 +0000 [thread overview]
Message-ID: <87vbiz8dm3.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87zj8bpbnk.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 18 Feb 2015 14:55:11 +0100")
On Wednesday, 18 Feb 2015 at 14:55, Nicolas Goaziou wrote:
[...]
> Apparently `org-odt-inline-image-rules' dismisses pdf files as images.
> What happens if you add PDF extension to the list?
Ah ha!
Adding pdf to the list of extensions (using customize, not editing the
code at this point) enables the exporter to run to completion. This is
a great step forward as I can now get a document that I can do something
with.
The exporter seems to be collecting the images: they end up in the
actual ODT file. However, viewing the file in libreoffice shows
placeholders where the images should be but with a "Read-Error"
message. The captions are there but the images are empty. I guess that
libreoffice cannot handle PDF images, which probably shouldn't surprise
me...
Now that I know what the problem is, I can see a way forward: all of my
images are created within the org document using babel and I can have an
alternate target of PNG for odt export.
I would imagine that the easiest change in org would be to simply have
an error message telling the user that PDF files cannot be used as
images?
Alternatively, would it be possible to invoke imagemagick to convert PDF
images to PNG as we do with LaTeX snippets?
Thanks for all your help on this,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-843-ga5f1a3.dirty
prev parent reply other threads:[~2015-02-18 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 17:29 on the fragility of export to ODT Eric S Fraga
2015-02-16 20:20 ` Nicolas Goaziou
2015-02-17 18:08 ` Eric S Fraga
2015-02-17 21:04 ` Nicolas Goaziou
2015-02-18 9:56 ` Eric S Fraga
2015-02-18 13:55 ` Nicolas Goaziou
2015-02-18 15:04 ` Eric S Fraga [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbiz8dm3.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).