public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'William Lupton' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Fenced divs rendered as HTML sections, taking h1 ID – how to avoid?
Date: Sun, 29 Jan 2023 22:54:34 +0000	[thread overview]
Message-ID: <CAEe_xxi2U6=tuQErQ7vPzAnWELFyeU90vRWGKc+1PwpPs2Jpyw@mail.gmail.com> (raw)
In-Reply-To: <7db57916-ce25-4e64-a521-24cdf3169af6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2370 bytes --]

One thing that seems to work is to insert an HTML comment (a bit like the
https://pandoc.org/MANUAL.html#ending-a-list trick) like this:

::: {.test}

<!-- separator -->

# Heading 1 {#heading-one}

:::

This generates:

<div class="test">
<!-- separator -->
<h1 id="heading-one">Heading 1</h1>
</div>

(If you've disabled raw HTML then something like \separator might work. At
worst a small filter might be necessary.)

On Sun, 29 Jan 2023 at 00:40, Martin Post <martinpostberlin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:

> I am trying to use fenced DIVs as described
> <https://pandoc.org/MANUAL.html#extension-fenced_divs> in the manual in
> Markdown to HTML conversion. However, I’m getting sections instead of DIVs,
> and the ID from the enclosed level 1 heading is moved to that section.
>
> I have not set --section-divs (and even setting it to false in the YAML
> block has no effect).
>
> So – how can I make the ID stay with the heading?
>
> Source:
>
> ::: {.test}
>
> # Heading 1 {#heading-one}
>
> :::
>
> Result for pandoc -f markdown -t html -s test.md -o test.htm :
>
> <section id="heading-one" class="test">
> <h1>Heading 1</h1>
> </section>
>
> How can I get
>
> <div class="test">
> <h1 id="heading-one">Heading 1</h1>
> </div> ?
>
> Thank you.
>
> (Pandoc 3.0.1)
>
> --
> 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/7db57916-ce25-4e64-a521-24cdf3169af6n%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/7db57916-ce25-4e64-a521-24cdf3169af6n%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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAEe_xxi2U6%3DtuQErQ7vPzAnWELFyeU90vRWGKc%2B1PwpPs2Jpyw%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 3523 bytes --]

      parent reply	other threads:[~2023-01-29 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29  0:40 Martin Post
     [not found] ` <7db57916-ce25-4e64-a521-24cdf3169af6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-29 22:54   ` 'William Lupton' via pandoc-discuss [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='CAEe_xxi2U6=tuQErQ7vPzAnWELFyeU90vRWGKc+1PwpPs2Jpyw@mail.gmail.com' \
    --to=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).