From: Rik Kabel <context@rik.users.panix.com>
To: Hans Hagen <j.hagen@xs4all.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: More spurious <break/> problems in exports
Date: Wed, 18 Jul 2018 12:05:10 -0400 [thread overview]
Message-ID: <c2be5c54-2762-3d49-8485-3e4923d91a23@rik.users.panix.com> (raw)
In-Reply-To: <0a768a8c-4043-b76c-9bbc-a0e43214019c@xs4all.nl>
On 7/18/2018 10:56, Hans Hagen wrote:
> 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.)
>
> You get this, with the numbers representing the paragraph number:
>
> \starttext
> % foo
>
> \startparagraph
> \emIt{x 1} a 1
> \stopparagraph
>
> \startparagraph
> {\emIt x 2} a unset
> \stopparagraph
>
> \stoptext
>
> of this:
>
> \starttext
> foo 1
>
> \startparagraph
> \emIt{x 2} a 2
> \stopparagraph
>
> \startparagraph
> {\emIt x 3} a 1
> \stopparagraph
>
> \stoptext
>
> so, when the par number is effectively set inside a group you end up
> with bad tags which will force that break because it's a different
> paragraph .. no way to intercept or chaneg that
>
> The best I can do is issue a warning like
>
> export > fuzzy paragraph: a (U+00061) [space] - (U+0002D) 2 (U+00032)
> 1 (U+00031) 4 (U+00034) 7 (U+00037) 4 (U+00034) 8 (U+00038) 3
> (U+00033) 6 (U+00036) 4 (U+00034) 7 (U+00037)
> backend > x
>
> so that one can fix the source.
Changing from a font switch – {\emIt text} – to a command – \emit{text}
– resolves the issue for these cases. I will add a note to the wiki
that, when changing from font switches to highlighting, one should
change the syntax.
--
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
___________________________________________________________________________________
prev parent reply other threads:[~2018-07-18 16:05 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
2018-07-18 14:56 ` Hans Hagen
2018-07-18 16:05 ` Rik Kabel [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=c2be5c54-2762-3d49-8485-3e4923d91a23@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).