From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Quick question about dual output pdf and epub
Date: Wed, 4 Mar 2020 11:02:46 +0100 [thread overview]
Message-ID: <7630F774-4860-4744-A60D-5817CB16D6DE@fiee.net> (raw)
In-Reply-To: <403eef8f-d5dc-a867-425b-9623d9c927a3@mailbox.org>
Am 2020-03-04 um 08:49 schrieb Jan U. Hasecke <juh+ntg-context@mailbox.org>:
> Am 03.03.20 um 22:04 schrieb Rik Kabel:
>> Instructions for creating the .epub from the export are contained in the
>> log file.
> Has anyone ever got an epub that validates?
Only with a lot of manual corrections.
I use the "raw" XML export, a bunch of XSL templates and a shell script, but still need to put stuff in place manually (i.e. everything that’s just visually formatted like the inner title and imprint).
I’m working on enhancing my workflow to at least succeed with epubcheck. I’ll probably need more than XSLT to e.g. check for image files (since I don’t use the file extension in ConTeXt, the XML processor can’t know if it’s a JPEG, PNG or PDF) etc. Maybe use Python instead of Shell + XSLT.
Our eBook distributor (BookWire) has even higher demands or checks better than the official epubcheck. (There are even example files in the consortiums’s GitHub that don’t validate.)
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-03-04 10:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:48 Christoph Hintermüller
2020-02-28 11:07 ` Hans Hagen
2020-02-28 14:09 ` Henning Hraban Ramm
[not found] ` <136b07463b64fcaa4e9b1850c030527a011570ab.camel@out-world.com>
2020-02-28 21:39 ` Hans Hagen
2020-03-01 13:05 ` Christoph Hintermüller
2020-03-03 18:37 ` Hans van der Meer
2020-03-03 18:47 ` Wolfgang Schuster
2020-03-03 20:58 ` Hans van der Meer
2020-03-03 21:02 ` Wolfgang Schuster
2020-03-03 21:04 ` Rik Kabel
2020-03-04 7:49 ` Jan U. Hasecke
2020-03-04 8:51 ` Hans Hagen
2020-03-04 9:31 ` luigi scarso
2020-03-04 9:46 ` Hans Hagen
2020-03-04 10:02 ` Henning Hraban Ramm [this message]
2020-03-04 12:23 ` epub and pdf not the same Hans van der Meer
2020-03-04 16:30 ` Wolfgang Schuster
2020-02-28 11:07 ` Quick question about dual output pdf and epub Hans Hagen
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=7630F774-4860-4744-A60D-5817CB16D6DE@fiee.net \
--to=texml@fiee.net \
--cc=ntg-context@ntg.nl \
/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).