ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans van der Meer <havdmeer@ziggo.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: please explain
Date: Fri, 7 Aug 2020 10:14:35 +0200	[thread overview]
Message-ID: <99D30032-165F-43FF-9E8D-10987FFF90AF@ziggo.nl> (raw)
In-Reply-To: <B5B5B990-CE23-488B-AA3D-CABED410BCED@elvenkind.com>


[-- Attachment #1.1: Type: text/plain, Size: 1505 bytes --]

> It is because ffi is a multi-part ligature.

Indeed, of course. I am getting old, I fear. It kept me awake in bed yesterday until I realised (far too late) it must be the ffi ligature. 

dr. Hans van der Meer


> On 7 Aug 2020, at 09:29, Taco Hoekwater <taco@elvenkind.com> wrote:
> 
> 
> 
>> On 6 Aug 2020, at 21:30, Hans van der Meer <havdmeer@ziggo.nl> wrote:
>> 
>> This MWE is an example of strange font behaviour according to the log and I do not understand what is causing it.
>> ConTeXt complains "check count_components with mkiv" when the word 'suffi' is present (see log message below).
>> 
>> Now comes the most strange: remove 'suffi' or shorten to 'suff' and the message goes away.
>> I have put the full set of files inside the zip.
> 
> Looks like it is a warning from Hans, mostly for himself. It is because ffi is a multi-part ligature.
> As long as the output looks ok, I do not think you have to pay attention.
> 
> Best wishes,
> Taco
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 3657 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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
___________________________________________________________________________________

      parent reply	other threads:[~2020-08-07  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 19:30 Hans van der Meer
2020-08-07  7:29 ` Taco Hoekwater
2020-08-07  7:49   ` Hans Hagen
2020-08-07  8:14   ` Hans van der Meer [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=99D30032-165F-43FF-9E8D-10987FFF90AF@ziggo.nl \
    --to=havdmeer@ziggo.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).