On 10/10/2018 14:50, Rik Kabel wrote:
On 10/8/2018 18:32, Hans Hagen wrote:

Alas, it is fixed for that particular occurence, but it still occurs 29 times in the document (using today's beta).

A more extended search shows that there are also spaces afters en-dashes (in "Press|–|Citizen" and  in "Miniatur|–|Bibliothek der Deutschen Classiker"), but none after em-dashes. Unfortunately, my attempts to reproduce this in a smaller document have so far failed.
well, you know: no mwe, no solution
And here is the mwe. The culprit, it appears, is bidi. I have tried all documented options (but not all combinations) for \setupdirections, and the only one under which there is no problem is "off". With bidi active, there is a spurious space wherever a linebreak is introduced. As the example demonstrates, this is not a function of the compounds, but of hyphenation in general.

    \setupbackend     [export=yes]
    \setupdirections  [bidi=on]
    \starttext
    abraca% adjust to cause hyphenation with your textwidth
    abra|-|cadabra abra|-|cadabra abra|-|cadabra abra|-|cadabra
    abra|-|cadabra abra|-|cadabra abra|-|cadabra abra|-|cadabra
    abra|-|cadabra abra|-|cadabra abra|-|cadabra abra|-|cadabra
    abra-cadabra abra-cadabra abra-cadabra abra-cadabra
    abra-cadabra abra-cadabra abra-cadabra abra-cadabra
    abra-cadabra abra-cadabra abra-cadabra abra-cadabra
    \stoptext

(The problem appears in the export html/xml file, not in the pdf.)

Not a function of explicit compounds (||) but of hyphenation of compounds. Normal hyphenation does not bring about the problem.

--
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
___________________________________________________________________________________

Reply via email to