From: Hans van der Meer <havdmeer@ziggo.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: unwanted <break/> with epub
Date: Thu, 5 Mar 2020 10:32:28 +0100 [thread overview]
Message-ID: <1E2917FB-B69D-42FB-B2B4-13AE46997DEB@ziggo.nl> (raw)
In-Reply-To: <06D0437C-A06A-49F0-B62B-FB8D43BDA321@ziggo.nl>
[-- Attachment #1.1: Type: text/plain, Size: 678 bytes --]
I was wrong. The \penalty is not the culprit, but it turns out to be the \Word macro that introduces the <break/> through a parfillskip_code in the internal list.
dr. Hans van der Meer
> On 5 Mar 2020, at 09:33, Hans van der Meer <havdmeer@ziggo.nl> wrote:
>
> Found the cause in my case: a \penalty0 statement.
>
> dr. Hans van der Meer
> On 3/3/2020 16:51, Hans van der Meer wrote:
>> In producing epub <break/>s are appearing (on the -raw.xml file) that are unwanted and seem spurious to me. For example aftersome macro's.
>> Can someone tell me what triggers a <break/>? In the pdf output such breaks are absent.
>>
>> dr. Hans van der Meer
>>
[-- Attachment #1.2: Type: text/html, Size: 5659 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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
___________________________________________________________________________________
prev parent reply other threads:[~2020-03-05 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 21:51 Hans van der Meer
2020-03-05 2:08 ` Rik Kabel
2020-03-05 8:33 ` Hans van der Meer
2020-03-05 9:32 ` Hans van der Meer [this message]
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=1E2917FB-B69D-42FB-B2B4-13AE46997DEB@ziggo.nl \
--to=havdmeer@ziggo.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).