From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: Lenin Gurusamy <guruleninn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: pdf/A Support
Date: Wed, 30 Nov 2022 11:12:44 +0100 [thread overview]
Message-ID: <874jugoi64.fsf@zeitkraut.de> (raw)
In-Reply-To: <a20ba077-5f7d-4337-849f-d8822959bd86n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Lenin Gurusamy <guruleninn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Does pandoc support pdf/A conversion using LaTeX ?
For PDF/A-3b see
https://twitter.com/pandoc_tips/status/1488912488271855625
For PDF/A-3a you'd have to go via a different PDF engine. I know that
ConTeXt, Prince XML, and the latest version of WeasyPrint support it in
some way or another.
I'm using ConTeXt in a project where we aim for accessible PDF output.
pandoc --pdf-engine=context -V pdfa=3a ...
See also <https://github.com/jgm/pandoc/pull/7885>; for the time being,
I'd recommend to use the above command in combination with this Lua
filter:
function Para(p)
p.content:insert(1, pandoc.RawInline('context', '\\bpar'))
p.content:insert( pandoc.RawInline('context', '\\epar'))
return p
end
HTH,
Albert
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2022-11-30 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 7:41 Lenin Gurusamy
[not found] ` <a20ba077-5f7d-4337-849f-d8822959bd86n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-30 8:25 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <16da090589bb425baffe70d689856f8b-NSENcxR/0n0@public.gmane.org>
2022-11-30 8:40 ` Bastien DUMONT
2022-11-30 10:12 ` Albert Krewinkel [this message]
[not found] ` <874jugoi64.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-30 10:25 ` Albert Krewinkel
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=874jugoi64.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
--cc=guruleninn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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).