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