emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Éric Würbel" <eric.wurbel@univ-amu.fr>
To: emacs-orgmode@gnu.org
Cc: "Éric Würbel" <eric.wurbel@univ-amu.fr>
Subject: Re: no more tikz -> png génération during HTML export
Date: Tue, 16 Oct 2018 10:04:03 +0200	[thread overview]
Message-ID: <87in2271xo.fsf@univ-amu.fr> (raw)
In-Reply-To: <87murgp9dd.fsf@gmail.com>


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 :

<policy domain="coder" rights="none" pattern="PDF" />

Which I rewrote into :

<policy domain="coder" rights="read|write" pattern="PDF" />

And now everything works fine with my original code.

E.

Le 14/10/2018 à 21:01 GMT, Jeremie Juste a dit:

> Hello
>
> With the following in your .emacs file 
>
> #+BEGIN_SRC 
>   (setq org-babel-latex-htlatex "htlatex")
>   (defmacro by-backend (&rest body)
>     `(case org-export-current-backend ,@body))
> #+END_SRC
>
> I can put back #+BEGIN_SRC around the tikz and it seems to work.
>
> #+header: :file (by-backend (html "images/graphic2.png") (t 'nil))
> #+header: :imagemagick
> #+header: :results (by-backend (pdf "latex") (t "raw"))
> #+BEGIN_SRC latex
> \begin{figure}[ht]
> \centering
> \begin{tikzpicture}[xscale=0.5]
>     % draw the sets
>     \filldraw[fill=none, draw] (-1.5,0) circle (1cm);
>     \filldraw[fill=none, draw] (1.5,0) circle (1cm);
>
>     % the texts
>     \node at (-1.5,1.5) {$E$};
>     \node at (1.5,1.5) {$F$};
>
>     % the points in the sets (here I just create nodes to use them later on to position
>     % the circles and the arrows
>     \node (a) at (-1.5,0.7) {$a$};
>     \node (b) at (-1.5,0.1) {$b$};
>     \node (c) at (-1.5,-0.4) {$c$};
>     \node (1) at (1.5,0.7) {$1$};
>     \node (2) at (1.5,0.1) {$2$};
>     \node (3) at (1.5,-0.4) {$3$};
>
>     % draw the arrows
>     \draw[->] (a) -- (2);
>     \draw[->] (c) -- (2);
>     \draw[->] (b) -- (1);
> \end{tikzpicture}
> \end{figure}
> #+END_SRC
>
> Best regards,
>
> Jeremie


-- 
É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/

  parent reply	other threads:[~2018-10-16  8:04 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 [this message]
2018-10-16  9:18       ` Eric S Fraga
2018-10-16  9:46         ` Éric Würbel
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=87in2271xo.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).