From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: manipulating headline level
Date: Wed, 29 Jun 2022 14:08:03 +0200 [thread overview]
Message-ID: <87ilojbqsp.fsf@zeitkraut.de> (raw)
In-Reply-To: <YrwNuCa4k0fe9YOb@odysseus>
Dear juh,
"'juh' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:
> Many markdown-files hierarchically ordered in folders.
> Every file starts with the top-level headline mark "#".
>
> I want to convert these files like this:
>
> pandoc $(cat outline.txt) -o target.html
>
> where outline.txt contains the relative pathes to all files.
>
>
> 00.md
> 01/00.md
> 01/01/00.md
> 01/01/01.md
> 01/01/02.md
>
> Is there a way to tell pandoc that it should regard the headline levels
> according to the folder structure?
Pandoc can't do this out of the box, but you could use a custom reader
to correct the headings. The below requires the current dev version
(nightly build), but could be rewritten to work with a released version,
too.
The script
- iterates over all input files,
- parses their contents as a separate document,
- shifts headers in each document by the number of subdirs the
respective file is in, and
- concatenates the individual per-file documents into a single
document that is then returned.
Pass the reader file to pandoc via the `--from` parameter.
``` lua
local format = 'markdown+smart'
function Reader (sources, opts)
local doc = pandoc.Pandoc{}
for _, source in ipairs(sources) do
local path_components = #pandoc.path.split(source.name)
-- last path component is the filename
local depth = path_components - 1
doc = doc .. pandoc.read(source, format, opts):walk {
Header = function (h)
h.level = h.level + depth
return h
end
}
end
return doc
end
```
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2022-06-29 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 8:30 'juh' via pandoc-discuss
2022-06-29 12:08 ` Albert Krewinkel [this message]
[not found] ` <87ilojbqsp.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-29 16:18 ` BPJ
[not found] ` <CADAJKhAWO5D23ChNizSGSuO-ouwOibBFTs0MmyBwJPGpQZYsVg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-30 8:43 ` 'juh' via pandoc-discuss
2022-06-30 12:11 ` Albert Krewinkel
[not found] ` <871qv6bb4n.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-30 14:10 ` 'Jan Ulrich Hasecke' via pandoc-discuss
[not found] ` <edfc1a65-e8ee-7e0e-f953-a4d75b19d8cb-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2022-06-30 14:37 ` 'Jan Ulrich Hasecke' via pandoc-discuss
[not found] ` <da9e1abc-97aa-339f-0eb6-720a5072e653-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2022-06-30 14:43 ` Albert Krewinkel
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=87ilojbqsp.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).