From: "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Syntax for <mark>?
Date: Thu, 21 Jul 2022 06:13:51 -0700 (PDT) [thread overview]
Message-ID: <860e29b8-0e75-4a89-92c5-205b7b5a48den@googlegroups.com> (raw)
In-Reply-To: <87h73ad3lk.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1196 bytes --]
I took a stab at this. PR #8191.
On Thursday, 21 July 2022 at 08:58:55 UTC-4 Albert Krewinkel wrote:
> William Lupton <wlu...-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org> writes:
>
> > Albert, is .mark documented in the manual? I didn't see it. Presumably
> > it could/should have a short section near the existing underline and
> > smallcaps sections. Tx, W.
>
> I believe the only mention is in the changelog of version 2.8:
>
> > Render a Span with class mark using the <mark> element (Florian
> > Beeres, #5797).
>
> You are probably right about having this documented, although the line
> between feature and implementation detail is a bit blurry here. Would
> you like to create a PR?
>
> --
> 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/860e29b8-0e75-4a89-92c5-205b7b5a48den%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1799 bytes --]
next prev parent reply other threads:[~2022-07-21 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 11:26 name name
[not found] ` <282ad19d-eac8-40d0-a741-7f7ae41a7b20n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-21 11:29 ` Albert Krewinkel
[not found] ` <87pmhyd7lv.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-07-21 11:59 ` William Lupton
[not found] ` <CAEe_xxhSMiL13qZ3Y_xc8uYR-kxQQ-f8V+VzSSpgM1=Zsq74gg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-21 12:57 ` Albert Krewinkel
[not found] ` <87h73ad3lk.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-07-21 13:13 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
[not found] ` <860e29b8-0e75-4a89-92c5-205b7b5a48den-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-21 13:37 ` William Lupton
[not found] ` <CAEe_xxi5QbA__V0JVFptVCpdkgjRr8jhSq0VBfkfPNZKB8Xwag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-22 10:17 ` BPJ
[not found] ` <CADAJKhAuoU2Oh_Fp_Wu=8oQ35CcAYsxMSkd_1gpwRNFgnM0KUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-22 11:53 ` William Lupton
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=860e29b8-0e75-4a89-92c5-205b7b5a48den@googlegroups.com \
--to=jmuccigr-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).