public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: mf <massifrg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: announce: a Lua filter to recursively include other documents from a master document
Date: Tue, 23 May 2023 17:35:31 +0200	[thread overview]
Message-ID: <4f707c3a-0048-8fbc-a2fe-f33a70204590@gmail.com> (raw)

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

Hello,

I just published a Lua filter for Pandoc that lets you organize a 
document in multiple files in a tree-like fashion, and assemble them later.

You can find it at https://github.com/massifrg/pandoc-include-doc.

The filter supports the inclusion of sub-documents through Div elements, 
whose contents are replaced by the contents (the blocks) of an external 
file imported through pandoc.read().

Those Div elements have a "include-doc" class and must specify the 
source and the format in the "include-src" and "include-format" attributes.

Sub documents inclusion is recursive and the filter detects possible 
circular references in the inclusions' chains.

You could already assemble a list of input files in Pandoc (i.e. see 
--file-scope in the docs), this filter lets you organize your documents 
in a tree-like structure.


Motivation: I wrote this filter because I'm writing a visual editor for 
pandoc types (= documents coded in the internal Pandoc format) based on 
Tiptap/Prosemirror.

Since the editor is browser-based, the size of the documents it can 
handle is much less than the size of the files converted by Pandoc, so 
it makes sense slicing them into smaller units (i.e. chapter, sections, 
etc.)

MF

-- 
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/4f707c3a-0048-8fbc-a2fe-f33a70204590%40gmail.com.

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

             reply	other threads:[~2023-05-23 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 15:35 mf [this message]
     [not found] ` <4f707c3a-0048-8fbc-a2fe-f33a70204590-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-05-25 15:58   ` mf

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=4f707c3a-0048-8fbc-a2fe-f33a70204590@gmail.com \
    --to=massifrg-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).