ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Cc: "Michel Bovani" <michel.bovani@wanadoo.fr>
Subject: Re: fourier
Date: Fri, 19 Sep 2003 15:30:15 +0100	[thread overview]
Message-ID: <20030919143015.28238@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <5.2.0.9.1.20030919134352.020162b0@server-1>

Hans Hagen said this at Fri, 19 Sep 2003 13:54:46 +0200:

>i.e. we don't need the -Expert here because it can live in a typeface; but 
>how to deal with Black and Semi?

And Light? (and ExtraLight and ExtraBlack?)

Hmm. You're asking us?
I always assumed, since I came to the ConTeXt game relatively late, that
it was a conscious choice to make only two weights available at once.
Typographically, it mostly makes sense not to mix Regular with SemiBold
and Bold in text, so I didn't argue with that.

However, I realise others will point out that SemiBold could be very
useful in headings and other areas outside the normal text flow. Likewise
with the other weights.

Plus, many of these weights are somewhat intended by their designers to
be contrasted with one another, like Light+SemiBold, Regular+Bold,
SemiBold+ExtraBold.

So one way could be to keep the [Serif] [SerifBold] [SerifSemiBold]
[SerifLight] synonyms around, and selectively sub-set them and associate
the with \tf and \bf as appropriate.

It could be taken further, as Michel has done, to make all four
accessible at once, with tf, db, bf, and eb. 
...but then you run into people who want to accommodate a fifth and sixth
weight.

(I would also prefer to break small caps out as a separate design axis
for faces in general, and not be tied to the notion that SerifSemiCaps is
possible, but SerifItalicCaps is not. Side issue.)

However, this list:
    [Serif]            
    [SerifSlanted]   
    [SerifItalic]   
    [SerifCaps]        
    [SerifSemiBold]    
    [SerifSemiSlanted]    
    [SerifSemiItalic]    
    [SerifSemiCaps]    %[SerifCapsSemi] ??
    [SerifBold] 
    [SerifBoldSlanted]  
    [SerifBoldItalic]  %[SerifCapsBold] ??
    [SerifBlack]  

Looks reasonably well-named, as far as it goes, if that's the question.
When dealing with the Adobe OpenType Pro font sets, I named a subset of
them SerifCapsBold, etc. within their own family (rc), parallel to the
Serif (rm) family.

There's also the issue of the optical size axis (Caption, Text, Subhead,
Display), but I think that can be sufficiently handled within size mappings.
For interest, here's an except from my treatment of weight x shape x caps
x size:

\starttypescript [serif] [Opticals] [size] 
\definebodyfont 
  [12pt,11pt][rm]
  [tf=SerifText sa 1,
  tfa=SerifSubhead sa \magfactor1,
  tfb=SerifSubhead sa \magfactor2,
  tfc=SerifSubhead sa \magfactor3,
  tfd=SerifDisplay sa \magfactor4,
   bf=SerifBoldText sa 1,
  bfa=SerifBoldSubhead sa \magfactor1,
  bfb=SerifBoldSubhead sa \magfactor2,
  bfc=SerifBoldSubhead sa \magfactor3,
  bfd=SerifBoldDisplay sa \magfactor4,
   it=SerifItalicText sa 1,
  ita=SerifItalicSubhead sa \magfactor1,
  itb=SerifItalicSubhead sa \magfactor2,
  itc=SerifItalicSubhead sa \magfactor3,
  itd=SerifItalicDisplay sa \magfactor4,
   bi=SerifBoldItalicText sa 1, 
  bia=SerifBoldItalicSubhead sa \magfactor1,
  bib=SerifBoldItalicSubhead sa \magfactor2,
  bic=SerifBoldItalicSubhead sa \magfactor3,
  bid=SerifBoldItalicDisplay sa \magfactor4,
   sc=SerifCapsText sa 1,
  sca=SerifCapsSubhead sa \magfactor1,
  scb=SerifCapsSubhead sa \magfactor2,
  scc=SerifCapsSubhead sa \magfactor3,
  scd=SerifCapsDisplay sa \magfactor4]
\definebodyfont 
  [12pt,11pt][rc]
  [tf=SerifCapsText sa 1,
  tfa=SerifCapsSubhead sa \magfactor1,
  tfb=SerifCapsSubhead sa \magfactor2,
  tfc=SerifCapsSubhead sa \magfactor3,
  tfd=SerifCapsDisplay sa \magfactor4,
   bf=SerifCapsBoldText sa 1,
  bfa=SerifCapsBoldSubhead sa \magfactor1,
  bfb=SerifCapsBoldSubhead sa \magfactor2,
  bfc=SerifCapsBoldSubhead sa \magfactor3,
  bfd=SerifCapsBoldDisplay sa \magfactor4,
   it=SerifCapsItalicText sa 1,
  ita=SerifCapsItalicSubhead sa \magfactor1,
  itb=SerifCapsItalicSubhead sa \magfactor2,
  itc=SerifCapsItalicSubhead sa \magfactor3,
  itd=SerifCapsItalicDisplay sa \magfactor4,
   bi=SerifCapsBoldItalicText sa 1, 
  bia=SerifCapsBoldItalicSubhead sa \magfactor1,
  bib=SerifCapsBoldItalicSubhead sa \magfactor2,
  bic=SerifCapsBoldItalicSubhead sa \magfactor3,
  bid=SerifCapsBoldItalicDisplay sa \magfactor4]
\stoptypescript

It's tough: you can easily come up with 100+ styles for a single font,
very legitimately, which suggests that perhaps a stricter
parameterisation could be useful:
  3 upright vs italic vs slanted (+ upright italic?)
  4 or 5 weights
  2 roman vs caps (or oldstyle, other variants)
x 4 optical sizes
---
 96+ variations

yow.
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay                      atl@comp.lancs.ac.uk
 Computing Dept, Lancaster University   +44(0)1524/594.537
 Lancaster, LA1 4YR, UK             Fax:+44(0)1524/593.608
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-09-19 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 11:54 fourier Hans Hagen
2003-09-19 14:30 ` Adam Lindsay [this message]
2003-09-19 19:25   ` fourier Henning Hraban Ramm
2003-09-19 19:18 ` fourier 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=20030919143015.28238@news.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --cc=michel.bovani@wanadoo.fr \
    --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).