public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Connor Patrick Jackson
	<cpjackson-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: <article> rather than <section> in HTML5 output
Date: Sun, 18 Jul 2021 11:44:53 -0700	[thread overview]
Message-ID: <m2fswblavu.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <3ceb7519-ed4b-4118-a214-6c4b63e07c21n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Connor Patrick Jackson <cpjackson-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:

> Sounds good to me! I've got half of a filter set up to do this, if someone 
> could just point me in the right direction. Is there a way to hook into the 
> HTML writer and tell it which tag to use for the div/section? Or would I 
> have to go the route of just adding the tags manually as RawInline and 
> removing the Section class? (or some third, better approach that I'm not 
> seeing because this is the first time I've written a filter)? Thanks!

Exactly, you'd have to add the tags manually.


  parent reply	other threads:[~2021-07-18 18:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 17:56 Connor Patrick Jackson
     [not found] ` <c07ed5ea-b466-4b33-b9dc-9917c2983f7an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-17  2:57   ` John MacFarlane
     [not found]     ` <m28s25pryw.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-07-17 18:42       ` Connor Patrick Jackson
     [not found]         ` <3ceb7519-ed4b-4118-a214-6c4b63e07c21n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-18 18:44           ` John MacFarlane [this message]
     [not found]             ` <m2fswblavu.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-07-22 14:20               ` Connor Patrick Jackson
     [not found]                 ` <cdcdbebe-d19a-4d8f-96dc-5e03a2977bc2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-22 18:41                   ` John MacFarlane
     [not found]                     ` <yh480keebq42e9.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-07-22 19:24                       ` Connor Patrick Jackson
     [not found]                         ` <39dfd03d-544d-46b1-8492-f517a5b3e652n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-22 20:25                           ` John MacFarlane
2021-07-24 17:08                           ` BPJ
     [not found]                             ` <CADAJKhDe9nzpyXzB2pWO=bme-A5TBZEH6xncmnGnEQQ7jB78-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-07-24 20:08                               ` Connor Patrick Jackson
     [not found]                                 ` <54d50be7-9ffa-44a3-8a31-9988a60bb831n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-25  1:17                                   ` Connor Patrick Jackson

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=m2fswblavu.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=cpjackson-TVLZxgkOlNX2fBVCVOL8/A@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).