From: Ihor Radchenko <firstname.lastname@example.org>
To: Jason Ross <email@example.com>
Subject: Re: Best way to include METAPOST in ConTeXt exporter
Date: Mon, 04 Oct 2021 16:41:08 +0800 [thread overview]
Message-ID: <87wnmtb2sb.fsf@localhost> (raw)
Jason Ross <firstname.lastname@example.org> writes:
> I'd like to include METAPOST figures in the ConTeXt exporter backend I'm
> developing. However, I don't know of an idiomatic way to add captions and
> references for the figures.
You can use affiliated keywords:
'("CAPTION" "DATA" "HEADER" "HEADERS" "LABEL" "NAME" "PLOT" "RESNAME" "RESULT"
"RESULTS" "SOURCE" "SRCNAME" "TBLNAME")
"List of affiliated keywords as strings.
By default, all keywords setting attributes (e.g., \"ATTR_LATEX\")
are affiliated keywords and need not to be in this list.")
> Currently, I export METAPOST with `#+BEGIN_EXPORT metapost` / `#+END_EXPORT`
> tags. However, this feature seems to be intended for completely "raw"
> with no markup or tagging in the resulting export. I'm interested in
> at least `#+NAME` and `#+CAPTION` keywords for METAPOST figures so that they
> can be referred to in the Org file and also in the exported pdf.
> What are some better ways of doing something like this? Source blocks? How
> a user expect to use a feature like this?
You can use a special block:
#+caption: Sample caption
#+attr_context: :field value
The parsed representation of this element in exporter will be something like:
(special-block (:type "metapost" :begin 292 :end 382 :contents-begin 364 :contents-end 368 :post-blank 0 :post-affiliated 347 :caption (((#("Sample caption" 0 14 (:parent #4))))) :attr_context (":field value")))
next prev parent reply other threads:[~2021-10-04 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 17:53 Best way to include METAPOST in ConTeXt exporter Jason Ross
2021-10-04 8:41 ` Ihor Radchenko [this message]
2021-10-04 15:41 ` Jason Ross
2021-10-04 16:46 ` Ihor Radchenko
2021-10-05 14:40 ` Jason Ross
2021-10-05 19:50 ` Jason Ross
2021-10-13 6:51 ` Ihor Radchenko
2021-10-13 6:54 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).