From: Aidan Reilly <aireilly-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Docbook > markdown conversion: orderedlist title gets swallowed by pandoc
Date: Thu, 17 Nov 2022 05:25:24 -0800 (PST) [thread overview]
Message-ID: <90142851-e8e8-46e7-a9c8-c9367683bed0n@googlegroups.com> (raw)
In-Reply-To: <87a64q55el.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]
Done. Thank you!
https://github.com/pandoc/lua-filters/issues/253
On Thursday, November 17, 2022 at 8:52:58 AM UTC Albert Krewinkel wrote:
> Aidan Reilly <aire...-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:
>
> > When I try the following conversion, the <title/> element gets
> > swallowed by the pandoc conversion. I don't see anything in the
> > output. Is this a limitation of the docbook reader?
>
> Yes, and I believe that there isn't an easy workaround either. Would you
> create a feature request in pandoc's issue tracker for this?
>
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
--
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/90142851-e8e8-46e7-a9c8-c9367683bed0n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1676 bytes --]
prev parent reply other threads:[~2022-11-17 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 17:20 Aidan Reilly
[not found] ` <6f2094f7-d632-47df-8211-e2971ee4e40an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-17 8:50 ` Albert Krewinkel
[not found] ` <87a64q55el.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-17 13:25 ` Aidan Reilly [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=90142851-e8e8-46e7-a9c8-c9367683bed0n@googlegroups.com \
--to=aireilly-h+wxahxf7alqt0dzr+alfa@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).