From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Emmanuel Charpentier <emm.charpentier@free.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: BUG: the builtin LaTeX/P DF exporter mislabels source blocks as figures.
Date: Tue, 30 Apr 2019 19:05:45 +0200 [thread overview]
Message-ID: <87pnp35spi.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <fd833ebea313c2c61bb95cd9ea1a89e05a92ae31.camel@free.fr> (Emmanuel Charpentier's message of "Tue, 30 Apr 2019 09:18:51 +0200")
Hello,
Emmanuel Charpentier <emm.charpentier@free.fr> writes:
> Whereas the HTML exporter correctly recognize a source block as such,
> the LaTeX/PDF exporter does not.
>
> This can be demonstrated in a (minimal) org file using *only* the
> built-in tools (no external packages), where a source block is labelled
> as such by the HTML exporter but as a figure by the LaTeX exporter.The
> generated LaTeX source shows a suspicious
> "\captionof{figure}{\label{orgf2d4160}" in the export of the source
> block.
>
> Further tests (not shown) show that the proble persists when org-mode
> is set up to use the minted package for LaTeX export of source blocks
> (minted is indeed used, but the block is s still mislabeled).
What LaTeX code do you suggest instead?
> The org source and resulting pdf and html files are available here :
> https://drive.google.com/drive/folders/1bQmaefiztW9ZDRNLcjOD_WbEmTg4d8dG?usp=sharing
Could you send your ECM in the ML without requiring to access Google
Drive?
Thank you.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-04-30 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 7:18 BUG: the builtin LaTeX/P DF exporter mislabels source blocks as figures Emmanuel Charpentier
2019-04-30 17:05 ` Nicolas Goaziou [this message]
2019-04-30 17:39 ` Emmanuel Charpentier
2019-04-30 17:46 ` John Kitchin
2019-04-30 18:05 ` Emmanuel Charpentier
2019-05-01 16:26 ` Nicolas Goaziou
2019-04-30 21:27 ` Correction and addition [Re: BUG: the builtin LaTeX/P DF exporter mislabels source blocks as figures.] Emmanuel Charpentier
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=87pnp35spi.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=emm.charpentier@free.fr \
/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).