ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: proposed convention for variation switching [wasRE:inheriting ...
Date: Thu, 21 Apr 2005 12:36:55 -0600	[thread overview]
Message-ID: <4275956D@webmail.colostate.edu> (raw)

>===== Original Message From "Adam Lindsay" <atl@comp.lancs.ac.uk> =====

>I don't have time to really delve into the implementation details, but it
>looks like the difference is that ConTeXt isn't so responsive with user-
>defined alternatives with more than two characters. Compare the stripped
>down version with your own. Your \scsb has been changed to \SB, effectively.

Hmm, I was a little worried at first about >2-char switches at first, till I 
noticed that type-siz.tex uses some four-letter switches as well, e.g.

============line-575==============
  \definebodyfont [12pt] [mm]
    [mrbf=xcmb12,
     exbf=cmex10 at 12pt,
     mibf=cmmib10 at 12pt,
     sybf=cmbsy10 at 12pt]
=====================================

So I assumed that such a scheme would work.

My suggestion: Either
a) the \*a(b)(c) etc mechanism needs modification to accomodate >2-char 
switches, or
b) an official 2-char switching convention for dealing with semibold and the 
standard five variants of small caps in ConTeXt is needed. Ideally users 
should not have to define switches for these standard variants anyway.

Here is an idea (further discussion needed):

a) Let's assume no change to the ConTeXt internals to accomodate >2-char 
switches.

b) There are twelve basic style variants in a professional modern serif font 
(math, greek, etc excluded): six for lower case and six for small caps.

On this basis, here is my suggestion for an official ConTeXt convention for 
professional fonts:

%% lowercase
% medium \tf
% semibold \sb
% bold \bf
% italic \it
% semibold italic \st
% bold italic \bi

%% small caps
% medium \TF
% semibold \SB
% bold \BF
% italic \IT
% semibold italic \ST
% bold italic \BI

The small caps versions are identical to the lowercase versions, with the 
difference that the small caps versions use caps. This serves as a mnemonic 
device.

We also need some long-winded control sequences:

  \definestyle [semiboldroman,semibold]                         [\sb][]
  \definestyle [semibolditalic]                                 [\st][]
  \definestyle [smallcapssemibold,semiboldsmallcaps]            [\SB][]
  \definestyle [smallcapsbold,boldsmallcaps]                    [\BF][]
  \definestyle [smallcapsitalic,italicsmallcaps]                [\IT][]
  \definestyle [smallcapssemibolditalic,semibolditalicsmallcaps][\ST][]
  \definestyle [smallcapsbolditalic,bolditalicsmallcaps]        [\BI][]

An identical or similar analysis may work for sans-serif, but I have to 
check...

Thank you very much for pinning down the source of this!
Best
Idris

============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523

             reply	other threads:[~2005-04-21 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 18:36 Idris Samawi Hamid [this message]
2005-04-21 19:56 ` Adam Lindsay
2005-04-21 22:43   ` Vit Zyka
2005-04-21 23:00     ` Adam Lindsay
2005-04-22  8:16   ` Hans Hagen
2005-04-22  9:38     ` Vit Zyka
2005-04-22 14:36     ` Idris Samawi Hamid
2005-04-22 14:55       ` Adam Lindsay
2005-04-22 17:13         ` Idris Samawi Hamid
2005-04-21 19:59 ` Adam Lindsay
2005-04-21 23:53 Idris Samawi Hamid
2005-04-22  8:45 ` Vit Zyka
2005-04-22  9:03   ` Taco Hoekwater

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=4275956D@webmail.colostate.edu \
    --to=ishamid@lamar.colostate.edu \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).