From: "Éric Würbel" <eric.wurbel@univ-amu.fr>
To: emacs-orgmode@gnu.org
Subject: Re: no more tikz -> png génération during HTML export
Date: Tue, 16 Oct 2018 11:46:39 +0200 [thread overview]
Message-ID: <87h8hm6x6o.fsf@univ-amu.fr> (raw)
In-Reply-To: <87muregsgy.fsf@ucl.ac.uk>
Le 16/10/2018 à 09:18 GMT, Eric S Fraga a dit:
> On Tuesday, 16 Oct 2018 at 10:04, Éric Würbel wrote:
>> Hello list,
>>
>> I finally tracked down the problem. It is not related to my use of
>> latexmk. It is an Imagemagick problem. The version installed by xubuntu
>> 18.04 has a restrictive policy on pdf files. I tweaked the
>> '/etc/ImageMagick-6/policy.xml' file which contains the following policy
>> restriction :
>
> Wow! Well done in tracking this down. Why would ubuntu do this? The
> Debian release does not have the restriction. It might be worth adding
> a note to the manual, although I am not entirely sure where because this
> whole aspect of LaTeX fragments and how they are converted is spread
> over several sections and footnotes.
You're welcome !
I think that this problem is very specific to the following case :
- LaTeX SRC block
- needed translation of this block into a png (and perhaps svg) image
- preprocessing with pdflatex, so we end up with a pdf->png conversion.
IMO we should perhaps add a warning in this worg page :
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-LaTeX.html
Except if anyone identify another use case which can lead to the same
problem.
E.
--
Éric Würbel
http://eric.wurbel.perso.luminy.univ-amu.fr/
Enseignement: IUT R&T, directeur des études 1A
Recherche: LIS CNRS, UMR7020 http://www.lis-lab.fr/
next prev parent reply other threads:[~2018-10-16 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 12:26 no more tikz -> png génération during HTML export Éric Würbel
2018-10-14 13:37 ` Jeremie Juste
2018-10-14 21:01 ` Jeremie Juste
2018-10-15 6:29 ` Éric Würbel
2018-10-16 8:04 ` Éric Würbel
2018-10-16 9:18 ` Eric S Fraga
2018-10-16 9:46 ` Éric Würbel [this message]
2018-10-16 11:00 ` Eric S Fraga
2018-10-17 13:02 ` Nicolas Goaziou
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=87h8hm6x6o.fsf@univ-amu.fr \
--to=eric.wurbel@univ-amu.fr \
--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).