From: Gwern Branwen <gwern-v26ZT+9V8bxeoWH0uzbU5w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc 2.19 "flattens" text in table of contents, no more <span> — workaround?
Date: Tue, 11 Oct 2022 15:38:13 -0400 [thread overview]
Message-ID: <CAMwO0gzcxrMGX0=F2Dw_CZvAi1w0RjQYP8+wAsx-cemU65NgDw@mail.gmail.com> (raw)
In-Reply-To: <a9663214-8b54-4f70-8dcf-8b726ac9b121n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Spans were removed by https://github.com/jgm/pandoc/issues/8020
Adding the triangle to the header text is working as it should. (It's
a strange use of <span>s which was not documented nor was it intended,
and you shouldn't've been relying on it.) There would seem to be many
more natural and less error-prone ways to decorate headers with a "▴".
Most obviously, why don't you use a CSS ::after pseudo-element, when
this sort of link annotation is their most common use and avoids
apparent problems with your original approach? (For example, if you
are injecting the triangle as a text literal, isn't it going to
pollute copy-paste?) Or if that doesn't work for something, why not
just wrap the triangle in a real span with a meaningful class, and
then just hide it in the ToC like '#toc span.return-marker { display:
none; }', something like that?
--
gwern
--
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/CAMwO0gzcxrMGX0%3DF2Dw_CZvAi1w0RjQYP8%2BwAsx-cemU65NgDw%40mail.gmail.com.
prev parent reply other threads:[~2022-10-11 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 18:55 szho...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <a9663214-8b54-4f70-8dcf-8b726ac9b121n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-11 19:38 ` Gwern Branwen [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='CAMwO0gzcxrMGX0=F2Dw_CZvAi1w0RjQYP8+wAsx-cemU65NgDw@mail.gmail.com' \
--to=gwern-v26zt+9v8bxeowh0uzbu5w@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).