ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: \definefontfeature and script
Date: Tue, 5 Jan 2021 18:53:00 +0100	[thread overview]
Message-ID: <fcf37e07-128b-7f62-e1e9-88abea0f5f58@gmx.es> (raw)
In-Reply-To: <fd9da1d9-6fa3-277c-9cdd-f0d778bd105a@xs4all.nl>

On 1/5/21 5:11 PM, Hans Hagen wrote:
> On 1/5/2021 4:46 PM, Pablo Rodriguez wrote:
>> [...]
>> If script=auto, current latest (2021.01.05 10:45) works fine. If it is
>> set to Latin (as above), I don’t get small caps.
>>
>> Besides the potential issue in ConTeXt, I think that "script=auto" may
>> be safer than "script=latn". Or am I taking too much for granted?
> well, ytou get what you ask for ... if you don't set the script you get
> default (dflt) which also gives small caps

I have another sample that makes me wonder whether ConTeXt is misbehaving:

  \definefontfeature
    [onumsmcp]
    [script=latn,
     onum=yes,
     smcp=yes,
     c2sc=yes]

  \definefallbackfamily
    [mainface]
    [rm]
    [GFS Heraklit]
    [preset=range:greek,
     force=yes]

  \definefontfamily
    [mainface]
    [rm]
    [TeX Gyre Pagella]

  \setupbodyfont
    [mainface]

  \starttext
    \feature[+][onumsmcp]\tfb ab12αβ
  \stoptext


GFS Heraklit
(https://greekfontsociety-gfs.gr/_assets/fonts/GFS_Heraklit.zip [direct
link].) defines Greek c2sc and smcp for grek{dflt} (as displayed by
FontForge [which I read as: default language and Greek script]).

Adding script=latn works with latest from 2020.12.30 16:45. Altough it
shouldn’t, since it would requiere Greek script for the Greek glyph
substitution.

That trick doesn’t work with latest from 2021.01.05 10:45. Either
script=latn or script=grek. And so are the glyph substitutions I get.

Sorry, but shouldn’t script=auto work for both?

I don’t know what I am missing or whether I hit a bug.

Many thanks for your help,

Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2021-01-05 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 15:46 Pablo Rodriguez
2021-01-05 16:11 ` Hans Hagen
2021-01-05 17:53   ` Pablo Rodriguez [this message]
2021-01-06 12:41     ` Hans Hagen
2021-01-06 13:31       ` Pablo Rodriguez

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=fcf37e07-128b-7f62-e1e9-88abea0f5f58@gmx.es \
    --to=oinos@gmx.es \
    --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).