public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: ThomasH <therch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: auto_identifiers in asciidoc output
Date: Sun, 14 May 2023 04:40:27 -0700 (PDT)	[thread overview]
Message-ID: <864059a2-0536-4fd5-9599-cb15e6947eafn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1341 bytes --]

 I have a strange phenomenon:

I'm translating from html to asciidoc, and would like to have 
auto_identifiers with headers in the output.

The html reader seems to enable auto_identifiers by default, as I can see 
those when I choose native as the output format (and don't assume 'native' 
will add them by itself).

In the asciidoc output though, the identifiers are only retained when I 
have an image as part of the header. I tried several alternative headers, 
and the identifiers only show in the output when the header contains an 
image.

Luckily, I can force consistent auto identifiers for all headings when 
using `-t asciidoc-auto_identifiers` on the command line (but mind the 
`-auto_...` instead of `+auto_...` to enable it!). But without that, why 
would the asciidoc writer automatically output the auto identifiers only 
for headers with an image? Is there some kind of complexity metrics 
involved?

Thanks, T.

-- 
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/864059a2-0536-4fd5-9599-cb15e6947eafn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1781 bytes --]

             reply	other threads:[~2023-05-14 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14 11:40 ThomasH [this message]
     [not found] ` <864059a2-0536-4fd5-9599-cb15e6947eafn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-15 17: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=864059a2-0536-4fd5-9599-cb15e6947eafn@googlegroups.com \
    --to=therch-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).