From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Dmitriy Krasilnikov
<dmitriy.krasilnikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Top level header lost
Date: Tue, 25 Feb 2020 10:08:00 -0800 [thread overview]
Message-ID: <m2sgiytu9r.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <120c0525-969a-495b-a031-a0bb8fdd26ba-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
It's the title field in the metadata. See the docs on
lua scripts for how to access the metadata.
Dmitriy Krasilnikov <dmitriy.krasilnikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Thanks for clarification.
>
> How can this top-level document title be accessed with Lua script?
>
> пятница, 21 февраля 2020 г., 20:42:44 UTC+3 пользователь John MacFarlane
> написал:
>>
>>
>> This is because it's a convention in rST that the top-level
>> heading is the document title:
>>
>>
>> https://docutils.sourceforge.io/docs/user/rst/quickstart.html#document-title-subtitle
>> <https://www.google.com/url?q=https%3A%2F%2Fdocutils.sourceforge.io%2Fdocs%2Fuser%2Frst%2Fquickstart.html%23document-title-subtitle&sa=D&sntz=1&usg=AFQjCNEZH9joZkO4IkzazpAZrKigOPD9mA>
>>
>> If you add `-s` to your `-t json` you'll see the difference.
>>
>> So why the difference with docx output? It's because pandoc
>> automatically enables standalone when you have a non-text format
>> for output (docx, pdf, etc.).
>>
>>
>> Dmitriy Krasilnikov <dmitriy.k...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes:
>>
>> > I'm trying to bind Header_1 to some docx style.
>> >
>> > This sample Lua filter function should output a header level each time
>> it
>> > finds one:
>> >
>> > function Header(el)
>> > print(el.level)
>> > end
>> >
>> > The source reStructured text code:
>> > ***************
>> > Header 1 sample
>> > ***************
>> >
>> > Text
>> >
>> > Header 2 sample
>> > ===============
>> >
>> > Text2
>> >
>> >
>> > Header 2 sample
>> > ===============
>> >
>> > Text2
>> >
>> > In a command line this should print 1, 2, 2:
>> > pandoc --lua-filter=rst2docxHead.lua -f rst -t json test.rst
>> >
>> > 1
>> > 2
>> > 2
>> > {"blocks":[{"t":"Header","c":[1,["header-1-sample",[],[]
>> >
>> > So, let's see how in converts to docx…
>> >
>> > $ pandoc --lua-filter=rst2docxHead.lua -f rst -t docx -o test.docx
>> test.rst
>> > 1
>> > 1
>> >
>> > For some reason in this configuration the top level header is not
>> processed
>> > and seems to be directly passed to docx output as a document title.
>> >
>> > --
>> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pandoc-discuss/a9db644a-43b0-4b2b-9b80-7f34cb9694ba%40googlegroups.com.
>>
>>
>
> --
> 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/120c0525-969a-495b-a031-a0bb8fdd26ba%40googlegroups.com.
--
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/m2sgiytu9r.fsf%40johnmacfarlane.net.
prev parent reply other threads:[~2020-02-25 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 13:57 Dmitriy Krasilnikov
[not found] ` <a9db644a-43b0-4b2b-9b80-7f34cb9694ba-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-02-21 17:42 ` John MacFarlane
[not found] ` <m2sgj3x2f2.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-02-25 16:04 ` Dmitriy Krasilnikov
[not found] ` <120c0525-969a-495b-a031-a0bb8fdd26ba-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-02-25 18:08 ` John MacFarlane [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=m2sgiytu9r.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=dmitriy.krasilnikov-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).