From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Alejandro Talaminos
<talaminos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: epub:type attribute in epub2
Date: Fri, 24 Sep 2021 09:13:51 -0700 [thread overview]
Message-ID: <m2czoy0x4w.fsf@Johns-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <f23f4199-30c2-4434-8b25-d1c50e30424cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
That sounds like a bug. Can you open an issue at
https://github.com/jgm/pandoc/issues
ideally linking to some documentation that these attributes
are not valid in epub2? We can then fix it.
Alejandro Talaminos <talaminos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hello,
>
> I am exporting my book to epub2 format. However, pandoc sets the epub:type
> attribute in body tag, when in fact this attribute is not compatible with
> epub2. Is there any way to prevent pandoc from setting this attribute on
> every chapter? Thank you.
>
> Regards,
> Alejandro
>
> --
> 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/f23f4199-30c2-4434-8b25-d1c50e30424cn%40googlegroups.com.
prev parent reply other threads:[~2021-09-24 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 7:39 Alejandro Talaminos
[not found] ` <f23f4199-30c2-4434-8b25-d1c50e30424cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-24 16:13 ` 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=m2czoy0x4w.fsf@Johns-Air.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=talaminos-Re5JQEeQqe8AvxtiuMwx3w@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).