From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<cjns1989-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc.markdown to epub conversion took just under 4 hours on an average linux laptop
Date: Tue, 27 Oct 2020 17:28:47 -0700 [thread overview]
Message-ID: <m2y2jrurb4.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <22d3d478-357d-464c-b407-aefd2ed81dccn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
"cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <cjns1989-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> With the nightly version (2.11.0.4)
>
> /tmp/pandoc -o epub/test.epub md/title.txt md2/ch*.md
> --css=css/stylesheet.css --epub-embed-font=fonts/*
> --epub-cover-image=images/cover.png
>
> the conversion took seconds.
>
> But pandoc complains that,
>
> [WARNING] This document format requires a nonempty <title> element.
> Defaulting to 'title' as the title.
> To specify a title, use 'title' in metadata or --metadata title="...".
>
> And the epubcheck report the following errors probably related to the above
> warning:
>
> ERROR(RSC-005): epub/test.epub/EPUB/content.opf(9,14): Error while parsing
> file: element "metadata" incomplete; missing required element "dc:title"
> ERROR(RSC-005): epub/test.epub/EPUB/nav.xhtml(11,134): Error while parsing
> file: Anchors within nav elements must contain text
>
> Check finished with errors
> Messages: 0 fatal / 2 errors / 0 warnings / 0 info
>
> epubcheck completed
>
> The title.txt file contains:
>
> % URBAIN DUBOIS
> % La cuisine classique — Volume II
Weird. This SHOULD work. Are you seeing anything
of this in the resulting epub? (I.e. did it get parsed,
but not as metadata? If so, maybe you need a blank line
at the end of title.txt.) (Also, I assume your input
format is pandoc markdown? commonmark_x doesn't include
an extension for this kind of title.)
> When I take a look at the output everything looks good except that the raw
> latex bits are now included verbatim as if they were part of the text/data.
They shouldn't be -- again, is pandoc markdown your input format?
Maybe a sample of how these occur in the markdown file?
--
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/m2y2jrurb4.fsf%40MacBook-Pro.hsd1.ca.comcast.net.
next prev parent reply other threads:[~2020-10-28 0:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 19:22 Chris Jones
[not found] ` <af5fe26b-4d84-4dcb-bdcd-6382469c476ao-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-10-26 21:15 ` John MacFarlane
[not found] ` <m2a6w8ofib.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-10-27 20:34 ` cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <e9e43a84-9ec5-4732-8dec-e6caac2e59ffn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-10-27 21:05 ` John MacFarlane
2020-10-27 21:50 ` cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <22d3d478-357d-464c-b407-aefd2ed81dccn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-10-28 0:28 ` John MacFarlane [this message]
[not found] ` <m2y2jrurb4.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-10-28 18:10 ` cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <824220b2-6c2e-4c60-a935-e908f573a3d7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-10-29 0:04 ` John MacFarlane
[not found] ` <m28sbpucc4.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-10-29 23:35 ` Chris Jones
2020-10-30 10:21 ` BPJ
2020-10-30 16:49 ` John MacFarlane
[not found] ` <m2zh43psk7.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-10-30 22:03 ` cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <20201030220312.GD5998-611mE6nXTcHDOqzlkpFKJg@public.gmane.org>
2020-10-30 22:58 ` cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
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=m2y2jrurb4.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=cjns1989-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).