ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Epub broken
Date: Thu, 5 Jul 2018 18:45:23 -0400	[thread overview]
Message-ID: <ba3a2976-98e8-2a5e-c1dd-8ae6b9ced694@rik.users.panix.com> (raw)
In-Reply-To: <8b752d1a-7e38-a98f-b055-a0cfe8c438d3@xs4all.nl>

On 7/5/2018 17:18, Hans Hagen wrote:
> On 7/5/2018 4:47 PM, Rik Kabel wrote:
>> 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:
> new beta
>
Thank you, Hans, for the quick repair.

I understand that ePub is not a priority 
(https://www.mail-archive.com/ntg-context@ntg.nl/msg87829.html) but I 
would like to make a request to put into the queue. Currently references 
(via \reference or \definelabel[xyz] ... \xyz, perhaps other mechanisms 
as well) do not generate ID attributes where they are created, and so 
references to them (which do generate href=#...) link to nothing. Even 
creating an empty div with an appropriate class (labelname, 
enumerationname, reference?) and the id attribute would help. Currently 
there is no placeholder in the html file to locate the proper place to 
insert this information with an external filter.

Of course, once that is done, there are lots more. So it goes.

-- 
Rik


___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2018-07-05 22:45 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
2018-07-05 21:18     ` Hans Hagen
2018-07-05 22:45       ` Rik Kabel [this message]
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=ba3a2976-98e8-2a5e-c1dd-8ae6b9ced694@rik.users.panix.com \
    --to=context@rik.users.panix.com \
    --cc=j.hagen@xs4all.nl \
    --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).