ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mikael P. Sundqvist" <mickep@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Lucida small caps
Date: Mon, 17 Feb 2020 16:48:32 +0100	[thread overview]
Message-ID: <CAHy-LL8YgN1E8GABcUep2URXZLv_ePq-Hi+mYh5USGGajyHjEQ@mail.gmail.com> (raw)
In-Reply-To: <28f0e75b-88b8-b018-7ef0-119a430ede19@xs4all.nl>


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

On Sun, Feb 16, 2020 at 11:34 AM Hans Hagen <j.hagen@xs4all.nl> wrote:

> On 2/15/2020 10:02 PM, Mikael P. Sundqvist wrote:
> > On Sat, Feb 15, 2020 at 9:50 PM Hans Hagen <j.hagen@xs4all.nl
> > <mailto:j.hagen@xs4all.nl>> wrote:
> >
> >     On 2/15/2020 4:34 PM, Mikael P. Sundqvist wrote:
> >      > Hi,
> >      >
> >      > One can easily enable small caps when using lucida, see the old
> mail
> >      > https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
> >      >
> >      > Could this be added to the type script file?
> >
> >     best use \smallcaps or somethign equivalent
>
> > Ah, so it was the \sc that was the problem. Thanks!
> \sc is more somthing mkii ... when type1 fonts (in an 8 bit universum)
> smallcaps and oldstyle and such meant using a different font
>
> nowadays one can turn them on/off as features and when you need them a
> lot you can even define an extra bodyfont variant from them and switch
> to that one when needed
>
> now, when smallcaps and oldstyle etc became features instead of font
> properties that didn't mean it always became easier because when
> opentype came around there was no 'recipe' or possibility to define what
> is default; for instance some fonts default to oldstyle in the sense
> that these shapes are in the default slots and you need to turn them off
> instead; also one needs to keep in mind that some features are language
> / script dependent and fonts differ in what they do default
>
> summary: see smallcaps as features but always look at what the font
> assumes and does by default; be prepared for inconsistencies (after all
> this is why we want/need control over what context does with a font)
>
> 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
> -----------------------------------------------------------------
>

That is good to know, thank you. While replacing all \sc with \smallcaps in
a document I work on, I realized that in a \setuphead I had

style={\sca},

What is the correct substitute for that?

/Mikael

[-- Attachment #1.2: Type: text/html, Size: 3236 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
___________________________________________________________________________________

  reply	other threads:[~2020-02-17 15:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15 15:34 Mikael P. Sundqvist
2020-02-15 20:50 ` Hans Hagen
     [not found]   ` <CAHy-LL9jbpyPiTuyPk1tg8-cerRrbHmq303b2-U4T09iG4=+Lg@mail.gmail.com>
2020-02-16 10:34     ` Hans Hagen
2020-02-17 15:48       ` Mikael P. Sundqvist [this message]
2020-02-17 16:20         ` Hans Hagen
2020-02-17 18:40         ` Henning Hraban Ramm

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=CAHy-LL8YgN1E8GABcUep2URXZLv_ePq-Hi+mYh5USGGajyHjEQ@mail.gmail.com \
    --to=mickep@gmail.com \
    --cc=j.hagen@xs4all.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).