public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Ottinger <dreamreal-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: NOTE and WARNING in DocBook -> Word conversions
Date: Fri, 6 Jan 2023 11:57:18 -0800 (PST)	[thread overview]
Message-ID: <f05af404-d529-4e22-8334-3a637bc98efcn@googlegroups.com> (raw)


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

Hi. I have a book written with asciidoctor, from which I generate DocBook, 
and that's fed into pandoc to generate Word output.

However, WARNING and NOTE types aren't rendered very well, I *think* - or 
it's entirely possible that they are rendered according to paragraph type 
and I just can't tell.

In the AST, WARNING and NOTE generate XML:

<note><simpara /></note> <!-- for NOTE types, obviously -->

When AsciiDoctor generates HTML, it annotates the content with NOTE: and a 
paragraph with the contents of the note. In Word, generated from DocBook, 
this annotation (the "NOTE:") is lost. That's sort of understandable, 
but... how would one replicate the behavior from the HTML backend? The 
DocBook *has* the types; the AST in Pandoc contains a DIV with a class that 
maps to NOTE or WARNING, so the context is there, but I have no idea how 
I'd update the Word output to reflect the NOTE or WARNING type.

-- 
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/f05af404-d529-4e22-8334-3a637bc98efcn%40googlegroups.com.

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

             reply	other threads:[~2023-01-06 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 19:57 Joseph Ottinger [this message]
     [not found] ` <f05af404-d529-4e22-8334-3a637bc98efcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-06 22:32   ` BPJ

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=f05af404-d529-4e22-8334-3a637bc98efcn@googlegroups.com \
    --to=dreamreal-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).