From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/106458
Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail
From: Rik Kabel <ConTeXt@rik.users.panix.com>
Newsgroups: gmane.comp.tex.context
Subject: Re: unwanted <break/> with epub
Date: Wed, 4 Mar 2020 21:08:52 -0500
Message-ID: <781359fa-50f2-804b-0ecf-0897727e0efe@rik.users.panix.com>
References: <0025CEF7-6FD7-45F7-B926-49BEC9C05E63@ziggo.nl>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1813268255708150361=="
Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202";
	logging-data="45208"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Firefox/68.0 Thunderbird/68.5.0
To: ntg-context@ntg.nl
Original-X-From: ntg-context-bounces@ntg.nl Thu Mar 05 03:09:12 2020
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1j9fwm-000Bfx-2F
	for gctc-ntg-context-518@m.gmane-mx.org; Thu, 05 Mar 2020 03:09:12 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 74B8F182751;
	Thu,  5 Mar 2020 03:08:59 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uuOlcIds-5mS; Thu,  5 Mar 2020 03:08:58 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 8D303182740;
	Thu,  5 Mar 2020 03:08:58 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 5659C18272F
 for <ntg-context@ntg.nl>; Thu,  5 Mar 2020 03:08:57 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id v--AhcNCQsdV for <ntg-context@ntg.nl>;
 Thu,  5 Mar 2020 03:08:55 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=166.84.1.89;
 helo=mailbackend.panix.com; envelope-from=context@rik.users.panix.com;
 receiver=<UNKNOWN> 
Original-Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 8A545182710
 for <ntg-context@ntg.nl>; Thu,  5 Mar 2020 03:08:55 +0100 (CET)
Original-Received: from [192.168.201.21] (cpe-72-228-11-252.nycap.res.rr.com
 [72.228.11.252])
 by mailbackend.panix.com (Postfix) with ESMTPSA id 48XvLZ1Gmxz1QCd
 for <ntg-context@ntg.nl>; Wed,  4 Mar 2020 21:08:53 -0500 (EST)
In-Reply-To: <0025CEF7-6FD7-45F7-B926-49BEC9C05E63@ziggo.nl>
Content-Language: en-US
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:106458
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/106458>

This is a multi-part message in MIME format.
--===============1813268255708150361==
Content-Type: multipart/alternative;
 boundary="------------FAF6E6D4F88682675FDE8D93"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------FAF6E6D4F88682675FDE8D93
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit


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


--------------FAF6E6D4F88682675FDE8D93
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 3/3/2020 16:51, Hans van der Meer
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:0025CEF7-6FD7-45F7-B926-49BEC9C05E63@ziggo.nl">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      In producing epub &lt;break/&gt;s are appearing (on the -raw.xml
      file) that are unwanted and seem spurious to me. For example
      aftersome macro's. 
      <div class="">Can someone tell me what triggers a &lt;break/&gt;?
        In the pdf output such breaks are absent.</div>
      <div class=""><br class="">
        <div class="">
          <div style="color: rgb(0, 0, 0); letter-spacing: normal;
            text-align: start; text-indent: 0px; text-transform: none;
            white-space: normal; word-spacing: 0px;
            -webkit-text-stroke-width: 0px; word-wrap: break-word;
            -webkit-nbsp-mode: space; -webkit-line-break:
            after-white-space;" class="">
            <div style="color: rgb(0, 0, 0); font-family: Helvetica;
              font-style: normal; font-variant-ligatures: normal;
              font-variant-caps: normal; font-variant-east-asian:
              normal; font-variant-position: normal; font-weight:
              normal; letter-spacing: normal; line-height: normal;
              orphans: 2; text-align: -webkit-auto; text-indent: 0px;
              text-transform: none; white-space: normal; widows: 2;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;
              word-wrap: break-word; -webkit-nbsp-mode: space;
              -webkit-line-break: after-white-space;" class="">dr. Hans
              van der Meer<br class="">
              <br class="">
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>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:</p>
    <ul>
      <li><a moz-do-not-send="true"
          href="https://www.mail-archive.com/ntg-context@ntg.nl/msg88729.html">Spurious
          breaks in export when blank line ends paragraph</a></li>
      <li><a moz-do-not-send="true"
          href="https://www.mail-archive.com/ntg-context@ntg.nl/msg88311.html">More
          spurious problems in exports</a></li>
      <li><a moz-do-not-send="true"
          href="https://www.mail-archive.com/ntg-context@ntg.nl/msg88268.html">Unexpected
          &lt;break/&gt; in XML output</a></li>
    </ul>
    <p>If you provide an example of your ConTeXt source demonstrating
      the problem, perhaps someone on the list can help.</p>
    <p>-- <br>
      Rik<br>
    </p>
  </body>
</html>

--------------FAF6E6D4F88682675FDE8D93--

--===============1813268255708150361==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s
aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv
IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v
cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn
YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============1813268255708150361==--