public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Dmitriy Krasilnikov <dmitriy.krasilnikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Top level header lost
Date: Fri, 21 Feb 2020 05:57:05 -0800 (PST)	[thread overview]
Message-ID: <a9db644a-43b0-4b2b-9b80-7f34cb9694ba@googlegroups.com> (raw)


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

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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a9db644a-43b0-4b2b-9b80-7f34cb9694ba%40googlegroups.com.

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

             reply	other threads:[~2020-02-21 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 13:57 Dmitriy Krasilnikov [this message]
     [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

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=a9db644a-43b0-4b2b-9b80-7f34cb9694ba@googlegroups.com \
    --to=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).