From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: ConTeXt inserts additional dots for Iosevka font
Date: Sun, 12 Sep 2021 14:21:11 +0200 [thread overview]
Message-ID: <ede6a79a-4744-332c-e431-b975f2b04eb7@xs4all.nl> (raw)
In-Reply-To: <773d095a-53f2-658a-bda7-c7469dd9cd96@gmail.com>
On 9/12/2021 9:45 AM, Wolfgang Schuster via ntg-context wrote:
> Marcel Fabian Krüger via ntg-context schrieb am 12.09.2021 um 01:12:
>> Hi,
>>
>> On Sun, Sep 12, 2021 at 12:01:08AM +0200, Hans Hagen wrote:
>>>> \definefontfeature
>>>> [default:test]
>>>> [default]
>>>> [cv36=2,cv26=6]
>>> What is the number supposed to indicate ? It is not an alternate, right?
>> Actually it is an alternate, but only partially.
>
> There is a table on the github page with the results from all alternatives.
>
> Look at section "Character Variats" on https://github.com/be5invis/Iosevka
With fonts like that we might end up in issues anyway:
\definefontfeature[default:test][default][mlxx=yes,wflm=yes]
\definedfont[file:iosevka.ttc(Iosevka)*default:test] :> <>
e.g.
WFLM Wolfram Language (Mathematica)
so we get font specific 4 char feature names that themselves have script
/ language specifications (like latin default and cyrillic serbian
wolfram) ... these could have been ss* features (after all, cv and ss
are wildcards and opentype has never been that consistent), not that it
matters much because it gets processed anyway, but it's a clear signal
that anyone can roll out adn use any feature name
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-09-12 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 20:36 Marcel Fabian Krüger via ntg-context
2021-09-11 22:01 ` Hans Hagen via ntg-context
2021-09-11 23:12 ` Marcel Fabian Krüger via ntg-context
2021-09-12 7:45 ` Wolfgang Schuster via ntg-context
2021-09-12 11:43 ` Hans Hagen via ntg-context
2021-09-12 12:21 ` Hans Hagen via ntg-context [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=ede6a79a-4744-332c-e431-b975f2b04eb7@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).