From: Conrad Cunningham <hcc.olemiss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Accessibility of Generated Docx
Date: Tue, 24 Sep 2019 20:54:42 -0700 (PDT) [thread overview]
Message-ID: <dfd7da5b-cded-4cdd-bb12-1cb04512a20d@googlegroups.com> (raw)
In-Reply-To: <b37da1b5-c763-4fc0-9006-d69f2a5a0b64-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]
Thanks.
I tried most of the pdf-engine options on a small test file. The context
engine seemed to work well according to the Tingtun pdf checker, but the
PAVE checker seemed to find more issues. (Any suggestions on free pdf
checkers?)
However, when I processed a couple of longer chapters of my notes that
formatted with Pandoc-flavored Markdown, the tex processor died with an
input error. I am not sure yet what is causing that to occur.
On Sunday, September 22, 2019 at 5:10:24 AM UTC-5, mb21 wrote:
>
> You can try:
>
> pandoc --pdf-engine=context -M pdfa -o output.pdf
>
> see the description of pdfa in
> https://pandoc.org/MANUAL.html#variables-for-context
>
> Maybe the pdfa part is not even needed, since the default pandoc context
> template includes \setuptagging[state=start]
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/dfd7da5b-cded-4cdd-bb12-1cb04512a20d%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2313 bytes --]
prev parent reply other threads:[~2019-09-25 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 21:21 Conrad Cunningham
[not found] ` <677959fb-29b8-4eaa-837f-c53e5ea5ab51-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-12 23:15 ` Devin Prater
2019-09-13 17:31 ` John MacFarlane
[not found] ` <yh480k1rwk6r2b.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-13 20:00 ` BP Jonsson
[not found] ` <CAFC_yuTPDWN5yxYnSObFq3kiRp+Z=Y3Kvd+67g16qz4D+EgeLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-09-20 18:53 ` Conrad Cunningham
[not found] ` <DF338AD1-4D4E-461B-8A66-F30986A9015E-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-09-21 17:54 ` John MacFarlane
[not found] ` <m2lfuh358a.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-22 10:10 ` mb21
[not found] ` <b37da1b5-c763-4fc0-9006-d69f2a5a0b64-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-25 3:54 ` Conrad Cunningham [this message]
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=dfd7da5b-cded-4cdd-bb12-1cb04512a20d@googlegroups.com \
--to=hcc.olemiss-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).