public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to process chunkedhtml output with Lua
Date: Wed, 25 Jan 2023 16:50:16 -0800	[thread overview]
Message-ID: <3F114306-007A-47CB-A067-3F7EE07900B0@gmail.com> (raw)
In-Reply-To: <84b97b97-8fe6-fb71-7d97-6ee0733b5763-4SSc53hpTiu9TMao6EloiEEOCMrvLtNR@public.gmane.org>



> Thanks. I'm making some progress with this. A couple more questions:
> 
> 1) pandoc.structure.split_into_chunks takes an opts parameter that has a path_template value. Is there a way to get the path_template that will be used by the chunked html writer?

It is "%s-%i.html"

> 2) The pandoc.structure.table_of_contents function returns a BulletList with the toc entries, but they are unnumbered even when --number-sections is true. I am calling
>     pandoc.structure.table_of_contents(chunkeddoc, PANDOC_WRITER_OPTIONS)
> where chunkeddoc is the output of split_into_chunks.  I have verified that PANDOC_WRITER_OPTIONS.number_sections = true. Am I missing something? Is this a bug?

Yes, we produce an unnumbered list. The numbers will be part of the content of the list items. (This is because the numbering scheme might not match up what is generated for an ordered list.)  In HTML you’d want to use some CSS to suppress the bullet.

> 3) Is there a simple way to get a list of files (including the image files) that will be included in the chunked html output folder? Maybe I can generate this from the ChunkedDoc, but it's going to take some parsing.

It should be easy to get the non-image files from the ChunkedDoc.  Then there’s index.json.  Image files, not so easy. 

-- 
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/3F114306-007A-47CB-A067-3F7EE07900B0%40gmail.com.


  parent reply	other threads:[~2023-01-26  0:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21 13:42 ChrisD
     [not found] ` <35211aad-9b34-1c74-b25f-c2c3777da632-4SSc53hpTiu9TMao6EloiEEOCMrvLtNR@public.gmane.org>
2023-01-21 22:23   ` John MacFarlane
     [not found]     ` <F03F5F72-A9B2-4AFB-92D7-DFA722BE5361-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-01-25 17:17       ` ChrisD
     [not found]         ` <84b97b97-8fe6-fb71-7d97-6ee0733b5763-4SSc53hpTiu9TMao6EloiEEOCMrvLtNR@public.gmane.org>
2023-01-26  0:50           ` John MacFarlane [this message]
     [not found]             ` <3F114306-007A-47CB-A067-3F7EE07900B0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-01-26 17:41               ` ChrisD
     [not found]                 ` <621a843e-049e-1a2b-1c60-df3158b6dc2e-4SSc53hpTiu9TMao6EloiEEOCMrvLtNR@public.gmane.org>
2023-01-26 21:57                   ` John MacFarlane
2023-01-27 10:42                   ` BPJ

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=3F114306-007A-47CB-A067-3F7EE07900B0@gmail.com \
    --to=fiddlosopher-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).