ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: unwanted <break/> with epub
Date: Wed, 4 Mar 2020 21:08:52 -0500	[thread overview]
Message-ID: <781359fa-50f2-804b-0ecf-0897727e0efe@rik.users.panix.com> (raw)
In-Reply-To: <0025CEF7-6FD7-45F7-B926-49BEC9C05E63@ziggo.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1002 bytes --]


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
>
There are many situations in which the export contains break elements 
that don't appear to be associated with aspects of the pdf output.  See, 
for example, the following messages from 2018 in which I noted a few of 
them:

  * Spurious breaks in export when blank line ends paragraph
    <https://www.mail-archive.com/ntg-context@ntg.nl/msg88729.html>
  * More spurious problems in exports
    <https://www.mail-archive.com/ntg-context@ntg.nl/msg88311.html>
  * Unexpected <break/> in XML output
    <https://www.mail-archive.com/ntg-context@ntg.nl/msg88268.html>

If you provide an example of your ConTeXt source demonstrating the 
problem, perhaps someone on the list can help.

-- 
Rik


[-- Attachment #1.2: Type: text/html, Size: 2937 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
___________________________________________________________________________________

  reply	other threads:[~2020-03-05  2:08 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 [this message]
2020-03-05  8:33   ` Hans van der Meer
2020-03-05  9:32     ` Hans van der Meer

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=781359fa-50f2-804b-0ecf-0897727e0efe@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).