From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with setuptagging and ebgaramond font
Date: Sun, 20 Nov 2016 19:37:55 +0100 [thread overview]
Message-ID: <390b81d7-02d0-8dc5-3883-2dc3bf90bb53@wxs.nl> (raw)
In-Reply-To: <11a132bb-1b9e-8724-da3f-d6e1e7486025@rik.users.panix.com>
On 11/20/2016 6:17 PM, Rik Kabel wrote:
> On 2016-11-20 11:51, Rik wrote:
>> On 2016-11-20 05:52, Hans Hagen wrote:
>>> On 11/20/2016 3:39 AM, Rik wrote:
>>>> On 2016-11-19 20:58, Rik Kabel wrote:
>>>>> Hmmm, it does work (the hyphenation, at least) with TL2016. Both logs
>>>>> show the same font files and typescript files.
>>>>>
>>>> Sorry, I did not mean to say the same files, but files identical in
>>>> content. The TL files are all from the TL directory. The standalone
>>>> files are from the standalone distribution and from my Windows font
>>>> directory. The font files originally were not the same version; TL2015
>>>> has version 0.016+, while my Windows font directory had version 0.016.
>>>> The typescript files are identical, one in the \ConTeXt directory, one
>>>> in the TL2016 directory.
>>>>
>>>> When I installed the TL2016 version of the fonts as system fonts (and
>>>> cleared the font cache) I still have the problem. So, identical files,
>>>> but different locations.
>>>
>>> And the garden distribution? I see hyphens.
>> Problem solved. Windows keeps multiple versions of a font file, even
>> when it says it is replacing. A bit of file maintenance and all is
>> well. Thank you for confirming that you see hyphens.
>>
> 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
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2016-11-20 18:37 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 [this message]
2016-11-21 1:54 ` Rik Kabel
2016-11-21 10:59 ` Hans Hagen
2016-11-21 15:38 ` 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=390b81d7-02d0-8dc5-3883-2dc3bf90bb53@wxs.nl \
--to=pragma@wxs.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).