From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: epubcheck errors with Pandoc 2
Date: Mon, 30 Oct 2017 10:24:59 -0700 [thread overview]
Message-ID: <20171030172459.GF38507@protagoras> (raw)
In-Reply-To: <bddc34b4-5b72-49b4-96a4-f02d936fab9d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Please open an issue on the issue tracker with these
points.
Include a small pandoc-generated epub that has these issues,
or alternatively give markdown input and exact command line
to produce an epub that has these issues.
+++ Russ [Oct 30 17 09:17 ]:
> In our tests, we noticed a few errors in epubcheck when compiling books
> with the Pandoc 2.0, these both compiled before without error on the
> previous Pandoc version :
> Validating using EPUB version 2.0.1 rules.
> ERROR(RSC-005): books.epub/EPUB/content.opf(2,181): Error while parsing
> file 'attribute "prefix" not allowed here; expected attribute "id"'.
> ERROR(RSC-007): books.epub/EPUB/cover.xhtml(10,83): Referenced resource
> could not be found in the EPUB.
> 1. Now the first one looks like a problems with `prefix="ibooks:
> http://vocabulary.itunes.apple.com/rdf/ibooks/vocabulary-extensions-1.0
> /"` in content.opf? Is there a way to turn this off or fix the error?
> <package version="2.0" unique-identifier="epub-id-1" prefix="ibooks:
> http://vocabulary.itunes.apple.com/rdf/ibooks/vocabulary-extensions-1.0
> /" xmlns="http://www.idpf.org/2007/opf">
>
> 2. The second one looks like a problem with this line in cover.xhtml,
> capital 'S' for Styles?
>
> <link rel="stylesheet" type="text/css"
> href="../styles/stylesheet1.css"/>
>
> Should it be ?
>
> <link rel="stylesheet" type="text/css"
> href="../Styles/stylesheet1.css"/>
>
> Any advice appreciated.
>
> Russ
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/bddc34b4-5b72-49b4-
> 96a4-f02d936fab9d%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/bddc34b4-5b72-49b4-96a4-f02d936fab9d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-10-30 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 16:17 Russ
[not found] ` <bddc34b4-5b72-49b4-96a4-f02d936fab9d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-30 17:24 ` John MACFARLANE [this message]
2017-10-31 0:04 ` John MACFARLANE
2017-10-31 0:43 ` John MACFARLANE
2017-10-31 7:11 ` Russ
[not found] ` <3c5d257d-6865-4843-83b2-65cfe058aae7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-31 16:58 ` 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=20171030172459.GF38507@protagoras \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).