public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jim <james.benstead-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Retaining headings when converting to PDF
Date: Sun, 23 Aug 2020 07:06:51 -0700 (PDT)	[thread overview]
Message-ID: <0eff3ef9-cd3d-4154-8dfe-976238704547n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1202 bytes --]

I'm producing a series of PDFs that are going to be read with a 
screenreader. The screenreader lets the user skip through a document by 
jumping to the next header. I've created documents in both Word and 
Markdown that include headers, but when I use pandoc to convert these 
documents to PDFs the headers are not included. The text that is defined as 
a header has a different visual style, but it isn't a header from the point 
of view of the screenreader.

I am able to produce a PDF with headers if I "Save As" from word and then 
create a PDF using Microsoft's own PDF creation tools. I'd really like to 
use pandoc for this, though, as it would offer me a ton more flexibility.

Is there a particular command I need to use in order for pandoc to retain 
headers when creating a PDF?

-- 
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/0eff3ef9-cd3d-4154-8dfe-976238704547n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1526 bytes --]

             reply	other threads:[~2020-08-23 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 14:06 Jim [this message]
     [not found] ` <0eff3ef9-cd3d-4154-8dfe-976238704547n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-23 15:36   ` Leonard Rosenthol
     [not found]     ` <CALu=v3JHcqWFaAmjTMds=3kZ4tEPktwpikG-HeoqZqX8c1tR9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-23 15:51       ` Håkon Wium Lie
     [not found]         ` <24386.36964.121997.392581-4mDQ13Tdud8Jw5R7aSpS0dP8p4LwMBBS@public.gmane.org>
2020-08-23 17:26           ` mb21
     [not found]             ` <f6e14085-7e59-4772-aa8e-f8928661bfb7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-23 17:35               ` James Benstead
     [not found]                 ` <CANUYFegTjwmiewYk1TT6t=2FB6xbve2WBWLLxZGckyhRnCq3gg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-24  0:57                   ` Leonard Rosenthol
     [not found]                     ` <CALu=v3JNcjW3O5va0K1duRzs=gd_FxAyooTzorErBpwT88cbcw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-25 12:35                       ` James Benstead
     [not found]                         ` <CANUYFeiNKVSnXD6JUUSx=UiWbrCzep=Dgfb-12KrZHz7eaZ_Ew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-25 12:48                           ` Leonard Rosenthol

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=0eff3ef9-cd3d-4154-8dfe-976238704547n@googlegroups.com \
    --to=james.benstead-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).