ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thomas Fehige <thomas@fehige.de>
To: ntg-context@ntg.nl
Subject: Re: uppercase, small caps, numerals and German capital sharp s
Date: Wed, 20 Apr 2016 23:27:02 +0200	[thread overview]
Message-ID: <5717F426.1040700@fehige.de> (raw)
In-Reply-To: <57179143.1070009@gmail.com>


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

Thanks for the clarification, Wolfgang.

Am 20.04.2016 um 16:25 schrieb Wolfgang Schuster:
> [...]
>> I was looking for a general way how to substitute one glyph with 
>> another depending on context, thus I can't see how there are 
>> different problems in my post? But it's good to hear that others have 
>> thought at least of a partial solution.
>>
>> Is my guess right that normally the author of a font ought to provide 
>> otf features that can be switched on and off to get one result 
>> instead of the other? That area seems to be utter chaos in the 
>> Calluna fonts.
> The output of \sc to produce small capitals depends on the font and 
> it’s the font designers job to provide a small ẞ (he could use 
> stilistic sets to let you choose between ß and ẞ).

Well, there's the problem, I think. Jos Buivenga, aka exljbris, 
Calluna's font designer, has done a superb job on the graphics (in my 
eyes), but his stylistic sets or otf features seem to be full of holes, 
as far as I understand them, which is perhaps not very far.

What I'm looking for is a way on the TeX, LuaTeX or ConTeXt level to 
define "environments" ('scuse my LaTeX slang) within which certain glyph 
substitutions happen. Then I could kind of redefine a thing like \sc to 
use the smallcaps ß and switch to smallcaps lining figures, if 
available, or, otherwise, scaled-down uppercase lining figures. I have 
still other fish to fry in this context, but a general hint where to 
look for something like this would be helpful.

Thanks a lot so far -- Thomas






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

[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2016-04-20 21:27 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  7:10 Thomas Fehige
2016-04-19 12:05 ` Wolfgang Schuster
2016-04-19 12:46   ` Thomas Fehige
2016-04-20 14:03   ` Thomas Fehige
2016-04-20 14:25     ` Wolfgang Schuster
2016-04-20 21:25       ` Thomas Fehige
2016-04-20 21:27       ` Thomas Fehige [this message]
2016-04-22 11:35       ` glyph substitution Thomas Fehige
2016-04-22 20:28         ` Hans Hagen
2016-04-25  9:53           ` Thomas Fehige
2016-04-25 12:48           ` Thomas Fehige
2016-04-25 15:49             ` Thomas Fehige
2016-04-25 18:12             ` Thomas Fehige
2016-04-25 20:44               ` Wolfgang Schuster
2016-04-26  8:42                 ` Thomas Fehige
2016-04-27 14:27                 ` Thomas Fehige
2016-04-27 15:10                   ` Hans Hagen
2016-04-29  7:44                     ` Thomas Fehige
2016-04-29  7:56                       ` Hans Hagen
2016-04-29  8:38                     ` Test Suite Fonts "extensions-001" Thomas Fehige
2016-04-29  9:05                       ` Wolfgang Schuster
2016-05-03  9:22                         ` Setting up TeXworks Thomas Fehige
2016-05-06  8:04                           ` Mojca Miklavec
2016-05-06 11:39                             ` L.S.-Soc&Gam
2016-05-16 15:46                               ` Thomas Fehige
2016-05-16 15:55                                 ` Jean-Pierre Delange
2016-05-17 11:16                                   ` Thomas Fehige
2016-05-17 12:39                                     ` Thomas Fehige
2016-05-17 12:59                                       ` Hans Hagen
2016-05-19 14:09                                         ` Thomas Fehige
2016-05-17 13:22                                       ` Jean-Pierre Delange
2016-05-19 15:16                                         ` Thomas Fehige
2016-05-19 16:15                                           ` Jean-Pierre Delange
2016-05-07 10:49                             ` Thomas Fehige
2016-05-09 11:02                               ` Thomas Fehige
2016-05-15 19:29                                 ` Thomas Fehige
2016-05-16 14:34                                   ` ConTeXt and Scite Thomas Fehige
2016-05-03  9:51                         ` Setting up TeXworks Thomas Fehige
2016-05-03 10:21                           ` Mojca Miklavec
2016-05-03 13:01                             ` Thomas Fehige
2016-04-25 20:47             ` glyph substitution Wolfgang Schuster
2016-04-26  7:42               ` Thomas Fehige
  -- strict thread matches above, loose matches on Subject: below --
2016-04-14 16:22 uppercase, small caps, numerals and German capital sharp s Thomas Fehige

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=5717F426.1040700@fehige.de \
    --to=thomas@fehige.de \
    --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).