ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Albert Krewinkel via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Albert Krewinkel <albert+context@zeitkraut.de>
Subject: ConTeXt features in pandoc 3
Date: Fri, 20 Jan 2023 22:00:31 +0100	[thread overview]
Message-ID: <87sfg4lwly.fsf@zeitkraut.de> (raw)

Hello,

a new version of pandoc, the universal document converter, was
released two days ago; pandoc 3 comes with new ConTeXt-related
features on which we've spend a good bit of time:

- *Syntax highlighting*: Pandoc makes use of the syntax
  definitions and styles created by the KDE project to highlight
  source code. This already worked with HTML, LaTeX, and formats
  like docx, and is now also supported for ConTeXt.

- *Inline code*: older versions of pandoc had some weird behavior
  wrt inline code in ConTeXt, switching between `\type` and
  `\mono`, which made it difficult to customize the output. This
  has been fixed.

- *Tagging-focused output*: Calling pandoc with
  `--to=context+tagging` creates markup that is geared towards the
  creation of tagged PDFs. This can be combined with `-V pdfa=3a`
  to produce accessible PDFs from various input sources.

- *Unlisted/unnumbered headings*: Headings with class "unnumbered"
  are not numbered; those with class "unlisted" get omitted from
  the ToC.

- *Figures*: We have improved support for figures considerably,
  and now also support subfigures. This is currently most
  noticeable when converting from HTML to ConTeXt.

Downloads and full changelog:
https://github.com/jgm/pandoc/releases/tag/3.0

I'm grateful for any and all feedback, including tips on how to
improve pandoc further.

Cheers,
Albert

-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2023-01-20 21:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 21:00 Albert Krewinkel via ntg-context [this message]
2023-01-20 23:48 ` Pawel Urbanski via ntg-context
2023-01-22 15:11 ` Saša Janiška via ntg-context
2023-01-23  7:22   ` juh via ntg-context
2023-01-23  8:24     ` luigi scarso via ntg-context
2023-01-24  6:22     ` Saša Janiška via ntg-context

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfg4lwly.fsf@zeitkraut.de \
    --to=ntg-context@ntg.nl \
    --cc=albert+context@zeitkraut.de \
    /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.
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 NNTP newsgroup(s).