You can create them on the command line using Word, on either Mac or Windows (using the MSOffice) - or Mac, Win or Linux using LibreOffice. Requires a second command, to go Word->PDF but still easy enough. Hakon - yes, thanks for the reminder. On Sun, Aug 23, 2020 at 1:36 PM James Benstead wrote: > Thank you all, that's very helpful. > > mb21: thank you for directing me to the github issue. I'd actually found > that independently, and it led me to try using ConTeXt. As you can see from > my comments at the bottom of the issue, while ConTeXt does add in some > headers, it doesn't allow for any hierarchical depth: i.e., when it > produces a PDF it flattens all headers to level 1. > > Word seems like the best bet for now, so I'll keep using that. I'll keep > an eye on this, though, as it would be great to be able to create tagged > PDFs from the command line, based on Markdown files. > > -- > Too brief? Here's why! http://emailcharter.org > > > On Sun, 23 Aug 2020 at 18:26, mb21 wrote: > >> There is also a corresponding pandoc github issue, where people also >> report success with ConTeXt: >> https://github.com/jgm/pandoc/issues/5409#issuecomment-678782766 >> >> On Sunday, August 23, 2020 at 5:51:11 PM UTC+2 Håkon Wium Lie wrote: >> >>> Also, Prince will happily create tagged PDF from HTML. >>> >>> http://www.princexml.com >>> >>> (I'm on the board of YesLogic, the company behind Prince) >>> >>> Håkon Wium Lie haa...-EO96REbE7qRuMpJDpNschA@public.gmane.org www.wiumlie.no/en >>> >>> Leonard Rosenthol wrote:: >>> >>> > That is because the current PDF creation processes from Pandoc (either >>> via >>> > TeX or HTML) cannot produce a proper Tagged PDF, that is required for >>> > screen reader integration. >>> > >>> > Your current best bets are to produce the PDF from Word/DocX using >>> either >>> > MSWord or LibreOffice, with the option to create Accessible/Tagged PDF >>> > turned on or to produce ICML with Pandoc and use Adobe InDesign to >>> produce >>> > the Tagged PDF. >>> > >>> > I am currently producing Tagged PDFs from Markdown through both of >>> these >>> > paths and they each have their own pros and cons... >>> > >>> > Future looking, Adobe is actively working with (and funding!) work in >>> the >>> > TeX community produce Tagged PDFs - its a ways off, but it will >>> happen. >>> > >>> > And Google just announced that Chrome (and one would assume CEF) can >>> now >>> > produce Tagged PDFs ( >>> https://9to5google.com/2020/07/29/chrome-tagged-pdf/), >>> > so perhaps we'll find an HTML-based path to get there soon as well. >>> > >>> > Leonard >>> > >>> > On Sun, Aug 23, 2020 at 10:06 AM Jim wrote: >>> > >>> > > 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-discus...-/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 >>> > > < >>> https://groups.google.com/d/msgid/pandoc-discuss/0eff3ef9-cd3d-4154-8dfe-976238704547n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> >>> > > . >>> > > >>> > >>> > -- >>> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >>> > To view this discussion on the web visit >>> https://groups.google.com/d/msgid/pandoc-discuss/CALu%3Dv3JHcqWFaAmjTMds%3D3kZ4tEPktwpikG-HeoqZqX8c1tR9g%40mail.gmail.com. >>> >>> >> -- >> 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/f6e14085-7e59-4772-aa8e-f8928661bfb7n%40googlegroups.com >> >> . >> > -- > 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/CANUYFegTjwmiewYk1TT6t%3D2FB6xbve2WBWLLxZGckyhRnCq3gg%40mail.gmail.com > > . > -- 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/CALu%3Dv3JNcjW3O5va0K1duRzs%3Dgd_FxAyooTzorErBpwT88cbcw%40mail.gmail.com.