From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Epub broken
Date: Thu, 5 Jul 2018 10:47:38 -0400 [thread overview]
Message-ID: <5904c966-0a98-c82e-7758-72ef2e1af906@rik.users.panix.com> (raw)
In-Reply-To: <fd02017b-aa89-0734-2d92-3f4de0ee079a@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 661 bytes --]
On 7/5/2018 10:27, Hans Hagen wrote:
> On 7/4/2018 3:17 PM, Rik Kabel wrote:
>> The following example fails with recent betas, but not with TL18:
> define fails
Sorry to be so terse in the original note. By failure, I mean that the
generated .epub document is incorrect; parts are out of order, as:
(When one section is removed, the disorder is gone, so a smaller test
file will not exhibit this problem.)
In a larger document, endnotes are scrambled as well, with two index
marks for some and none for others. The generated .pdf (which is a
throw-away when trying to produce epub) does not show the same problems.
The .epub file is attached.
--
RIk
[-- Attachment #1.2.1: Type: text/html, Size: 1257 bytes --]
[-- Attachment #1.2.2: efejfbplkcnfpklo.png --]
[-- Type: image/png, Size: 6388 bytes --]
[-- Attachment #2: test.epub --]
[-- Type: application/epub+zip, Size: 8703 bytes --]
[-- Attachment #3: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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:[~2018-07-05 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 13:17 Rik Kabel
2018-07-05 14:27 ` Hans Hagen
2018-07-05 14:47 ` Rik Kabel [this message]
2018-07-05 21:18 ` Hans Hagen
2018-07-05 22:45 ` Rik Kabel
2018-07-06 9:05 ` 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=5904c966-0a98-c82e-7758-72ef2e1af906@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).