From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Rik Kabel <context@rik.users.panix.com>
Subject: Re: More spurious <break/> problems in exports
Date: Wed, 18 Jul 2018 13:11:07 +0200 [thread overview]
Message-ID: <4d993789-77ef-37de-afcc-8d87d94ce816@xs4all.nl> (raw)
In-Reply-To: <f3be5b28-170d-7c26-fe42-596636da0d0e@rik.users.panix.com>
On 7/18/2018 4:59 AM, Rik Kabel wrote:
> List,
>
> Another oddity with <break/> elements in XML / xhtml / html export:
>
> With a defined highlight, a break is inserted if the highlight is the
> first item in an environment. If it is not the first item in the
> environment, no break is inserted.
>
> Most of the other odd breaks can be dealt with in css. These are more
> difficult to tame -- for example, in the startlines environment in the
> example below, there is not enough information preserved to know if the
> tagged item is supposed to be a single line or not.
>
> (Tests using 2018-07-17 beta on Win64.)
>
> Has anyone dealt with this before? Is there a way to control the
> insertion of the breaks?
>
> MWE:
>
> \setupbackend [export=yes]
> \definehighlight [emIt]
> [style=italic]
> \starttext
> \startparagraph
> {\emIt Taa} aaaaaaaaaaa aa aaaaaaaaa aaaaaa aaa aaaaaaaa aa aaaaaaaaaa
> aaaaaa. Taa aaaaaaaa aaaaa, aaaaa aaaaaaaa aa aaaaa aaaa aaaaa.
\emIt{Taa}
> \stopparagraph
> \startparagraph
> Taa {\emIt aaaaaaaaaaa} aa aaaaaaaaa aaaaaa aaa aaaaaaaa aa aaaaaaaaaa
> aaaaaa. Taa aaaaaaaa aaaaa, aaaaa aaaaaaaa aa aaaaa aaaa aaaaa.
> \stopparagraph
> \startlines
> {\emIt Xyz} abcdefg
> Xyz {\emIt abcdefg}
> \stoplines
> \stoptext
>
> XML output snip:
>
> <document context="2018.07.17 17:25" date="2018-07-17T22:41:25+20:00" file="xxx" language="en" version="0.35" xmlns:m="http://www.w3.org/1998/Math/MathML">
> <metadata>
> </metadata>
> <paragraph><highlight detail="emIt">Taa</highlight> <break/>
> aaaaaaaaaaa aa aaaaaaaaa aaaaaa aaa aaaaaaaa aa aaaaaaaaaa aaaaaa. Taa aaaaaaaa aaaaa, aaaaa aaaaaaaa aa aaaaa aaaa aaaaa.</paragraph>
> <paragraph>Taa <highlight detail="emIt">aaaaaaaaaaa</highlight> aa aaaaaaaaa aaaaaa aaa aaaaaaaa aa aaaaaaaaaa aaaaaa. Taa aaaaaaaa aaaaa, aaaaa aaaaaaaa aa aaaaa aaaa aaaaa.</paragraph>
> <lines detail="lines" chain="lines">
> <line><highlight detail="emIt">Xyz</highlight> <break/>
> abcdefg</line>
> <line>Xyz <highlight detail="emIt">abcdefg</highlight></line>
> </lines>
> </document>
>
> Rendered in Firefox:
>
> --
> 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
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-18 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 2:59 Rik Kabel
2018-07-18 11:11 ` Hans Hagen [this message]
2018-07-18 14:56 ` Hans Hagen
2018-07-18 16:05 ` Rik Kabel
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=4d993789-77ef-37de-afcc-8d87d94ce816@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=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).