From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Problem with setuptagging and ebgaramond font
Date: Mon, 21 Nov 2016 10:38:15 -0500 [thread overview]
Message-ID: <cd95e7bb-f66f-cf58-2b08-3d05b4b39467@rik.users.panix.com> (raw)
In-Reply-To: <e9432c80-ac36-f55c-48b9-e359b8cc16de@wxs.nl>
On 2016-11-21 05:59, Hans Hagen wrote:
> On 11/21/2016 2:54 AM, Rik Kabel wrote:
>> On 2016-11-20 13:37, Hans Hagen wrote:
>>> On 11/20/2016 6:17 PM, Rik Kabel wrote:
>>>> I still do not understand why \setuptagging[state=start] made a
>>>> difference. Something there is hinky[1].
>>>>
>>>> [1] Someone, or something, may be said to be hinky if it acts in a
>>>> manner that arouses suspicion. The origin is obscure.
>>>
>>> hard to comment when i cannot reproduce it
>>
>> The problem can be reproduced on my Windows 10 system by removing
>> existing EBGaramond12 and installing EBGaramond12 from version 0.015d,
>> followed by a cache clear. It is available on Georg Duffner's bitbucket
>> at https://bitbucket.org/georgd/eb-garamond/downloads. The problem I had
>> before was ensuring that the old versions of the font files were
>> actually removed -- I found versions with _0 and _1 suffixes that did
>> not show up in explorer and were not removable by an administrator in a
>> command prompt terminal. Other tools allowed their removal.
>
> the softhyphen in ebgaramond has zero width and no visualization .. i
> can patch that in the font (when loading) but can also consider it a
> bug in the font
>
> (i'll make it configurable in tagging but that only obscures the issue)
>
> Hans
>
Thank you, Hans.
As I said earlier, this is not a problem with the current version
(0.016) of the font, so a fix in ConTeXt is not needed unless it can
remediate the issue with other fonts as well.
My concern is that there was something that was amiss when tagging is in
effect and I thought that this might help expose it.
--
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:[~2016-11-21 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 1:48 Rik Kabel
2016-11-20 1:58 ` Rik Kabel
2016-11-20 2:39 ` Rik
2016-11-20 10:52 ` Hans Hagen
2016-11-20 16:51 ` Rik
2016-11-20 17:17 ` Rik Kabel
2016-11-20 18:37 ` Hans Hagen
2016-11-21 1:54 ` Rik Kabel
2016-11-21 10:59 ` Hans Hagen
2016-11-21 15:38 ` 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=cd95e7bb-f66f-cf58-2b08-3d05b4b39467@rik.users.panix.com \
--to=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).