public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Erik Rask <lifeunleaded-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Behaviour change in docbook reader
Date: Mon, 7 Nov 2022 08:43:23 +0100	[thread overview]
Message-ID: <CAMXDC9+w_75mDebPvJ-RyuUyJkd7x0QTbqUe7ZT1mwuWj_wZqA@mail.gmail.com> (raw)

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

Hello,
I went ahead and upgraded parts of the toolchain since the pandoc version
there was too old (all the way from 2.7.3 to 2.19.2). After that, the
conversion results from docbook to docx were different (granted, I am aware
it's a huge version change). Tracing this, I found one tangible example
that seems to occur in the docbook reader: A <note> element was previously
put into a blockquote pandoc object, now it is a div with an identifying
class.

I am trawling the changelogs for the releases between those two, but would
like to ask the community if you recognize the change offhand and know of
an extension or parameter that lets me revert to the old behaviour while I
identify all those changes and put together some Lua to address it?

docbook:
<note><para>Here is a note without a title</para></note>

Pandoc (-t native) 2.7.3:
BlockQuote
 [Para [Strong [Str "Note"]]
 ,Para [Str "Here",Space,Str "is",Space,Str "a",Space,Str "note",Space,Str
"without",Space,Str "a",Space,Str "title"]]

2.19.2:
Div
    ( "" , [ "note" ] , [] )
    [ Para [ Str "Here", Space, Str "is", Space, Str "a", Space, Str
"note", Space, Str "without", Space
        , Str "a", Space, Str "title"
        ]
    ]

Regards,
Erik Rask
-- 
Hurrying will get you nowhere faster.

-- 
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/CAMXDC9%2Bw_75mDebPvJ-RyuUyJkd7x0QTbqUe7ZT1mwuWj_wZqA%40mail.gmail.com.

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

             reply	other threads:[~2022-11-07  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  7:43 Erik Rask [this message]
     [not found] ` <CAMXDC9+w_75mDebPvJ-RyuUyJkd7x0QTbqUe7ZT1mwuWj_wZqA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-08 23:17   ` 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=CAMXDC9+w_75mDebPvJ-RyuUyJkd7x0QTbqUe7ZT1mwuWj_wZqA@mail.gmail.com \
    --to=lifeunleaded-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).