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: Unexpected space after hyphen in xml/html export
Date: Wed, 10 Oct 2018 15:11:34 -0400 [thread overview]
Message-ID: <606c6f51-3fa7-157d-4ebd-b151472fc4fa@rik.users.panix.com> (raw)
In-Reply-To: <67be6651-dea5-9318-e6f0-17bd876608e2@rik.users.panix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1688 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 2458 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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-10-10 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 22:19 Rik Kabel
2018-10-06 23:28 ` Hans Hagen
2018-10-08 20:24 ` Rik Kabel
2018-10-08 22:32 ` Hans Hagen
2018-10-10 18:50 ` Rik Kabel
2018-10-10 19:11 ` Rik Kabel [this message]
2018-10-11 21:01 ` 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=606c6f51-3fa7-157d-4ebd-b151472fc4fa@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).