From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: LaTeX alt text (was: ANN: pandoc 2.10)
Date: Tue, 30 Jun 2020 21:07:40 +0200 [thread overview]
Message-ID: <87r1twtls3.fsf@zeitkraut.de> (raw)
In-Reply-To: <7c2e96b3-53e2-402d-b5c6-dfb462a56760n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Thank you for your question. This does not seem directly related to the
latest release, a separate thread would have been preferable.
To answer your question: see https://github.com/jgm/pandoc/issues/5409
TL;DR: not a solved problem. Till then, use `-t context -M pdfa` when
producing PDFs.
'andre...-32lpuo7BZBA@public.gmane.org' via pandoc-discuss writes:
> Thanks
> Any plans to add native support for "alt text" when converting markdwon to
> pdf?
> Currently, i either have to learn another language (Lua) or convert to word
> first, then to pdf.
> Neither of which are optimal
> cheers
>
> On Tuesday, June 30, 2020 at 1:22:28 AM UTC-4 John MacFarlane wrote:
>
>>
>> I'm pleased to announce the release of pandoc 2.10,
>> available in the usual places:
>>
>> Binary packages & changelog:
>> https://github.com/jgm/pandoc/releases/tag/2.10
>>
>> Source & API documentation:
>> http://hackage.haskell.org/package/pandoc-2.10
>>
>> Some highlights:
>>
>> * Pandoc can now be compiled with ghc 8.10.
>>
>> * A native Underline constructor for Inline (#6277, Vaibhav Sagar)
>> and more consistent treatment of underlined text in readers
>> and writers.
>>
>> * More expressive types for tables (#1024, Christian Despres).
>> Tables can now take attributes; and rowspans and colspans,
>> column headers, multiple row headers, table head and foot
>> can all be represented. (Note, however, that reader and
>> writer support for these features is still lacking, so
>> most users won't see any differences in table conversion
>> yet. These changes just lay the foundation for further
>> improvements.)
>>
>> * Templates can now use the pipes `first`, `rest`, `last`, and
>> `allbutlast` on arrays.
>>
>> * A new `--no-check-certificate` option to disable certificate
>> validation when resources are fetched by HTTP (#6156, Cédric Couralet,
>> Cécile Chemin, Juliette Fourcot).
>>
>> * Boolean fields now work in metadata within defaults files
>> (Nikolay Yakimov, #6328).
>>
>> * The `implicit_figures` extension now works with commonmark
>> and gfm (#6350).
>>
>> * We now target version 4.x of reveal.js. File locations have
>> changed, so if you are using pandoc-produced reveal.js files
>> with a local copy of reveal.js, you will need to upgrade.
>>
>> * epub.css has changed to wrap overlong lines in highlighted code
>> blocks (#6242). This fixes a problem in iBooks v2.4 with our earlier
>> horizontally scrolling code blocks. The problem seems to
>> be a bug in iBooks, not pandoc, but since iBooks is a major
>> target we're changing pandoc's default behavior so that
>> pandoc-produced epubs work on that platform.
>>
>> * Many other bug fixes and small improvements (see the changelog
>> for details).
>>
>> API changes:
>>
>> * New Underline constructor for Inline and new Table types for Block.
>>
>> * Use new type PandocLua for all pandoc Lua operations.
>>
>> * Use PandocError for exceptions in Lua subsystem.
>>
>> Thanks to everyone who contributed, and especially Christian Despres for
>> creating the new table types and modifying the whole code base to use it,
>> Vaibhav Sagar for implenting the Underline constructor, Mathieu Boespflug
>> for
>> improving the DocBook reader, Joseph C. Sible for many code improvements
>> and
>> some important fixes to Text.Pandoc.UUID, and Albert Krewinkel for work on
>> the
>> lua subsystem, Jira reader and writer, Org reader and writer, and JATS
>> reader.
>> Thanks, as well, to those who have raised issues, participated in
>> discussions,
>> and helped to triage bugs.
>>
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
--
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/87r1twtls3.fsf%40zeitkraut.de.
next prev parent reply other threads:[~2020-06-30 19:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 5:22 ANN: pandoc 2.10 John MacFarlane
[not found] ` <m2366db01o.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-06-30 13:18 ` 'andre...-32lpuo7BZBA@public.gmane.org' via pandoc-discuss
[not found] ` <7c2e96b3-53e2-402d-b5c6-dfb462a56760n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-06-30 19:07 ` Albert Krewinkel [this message]
2020-06-30 20:50 ` John MacFarlane
2020-07-01 1:34 ` Lloyd R. Prentice
2020-07-01 7:52 ` Axel Kielhorn
[not found] ` <117937E5-2D23-4738-AC38-566BD144AAC5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-01 17:53 ` John MacFarlane
[not found] ` <m2mu4ji0ld.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-07-02 4:15 ` Axel Kielhorn
[not found] ` <4EC8C949-C4D8-44AB-A1D4-0D0C3656C970-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-02 16:29 ` John MacFarlane
[not found] ` <m2k0zlhocm.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-07-02 17:46 ` Axel Kielhorn
2020-07-02 1:12 ` Kolen Cheung
2020-07-02 13:26 ` jiewuza
[not found] ` <m27dvmgi93.fsf-9Onoh4P/yGk@public.gmane.org>
2020-07-02 16:31 ` John MacFarlane
[not found] ` <m2h7upho8z.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-07-02 23:52 ` Kolen Cheung
[not found] ` <1d38ad14-28f2-4d35-b54c-44cdbeadff42o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-07-02 23:55 ` Kolen Cheung
2020-07-03 4:47 ` John MacFarlane
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=87r1twtls3.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).