ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Subject: simplefonts
Date: Sun, 14 Mar 2010 08:12:05 -0500	[thread overview]
Message-ID: <54d7f5601003140612q60e57ccctc1dba0df39454a32@mail.gmail.com> (raw)

Thomas A. Schmitz:

Thank you, Thomas.  I've been studying this closely.

> A typescript file can contain a series of typeface definitions, e.g., one for serif, one for sans, one for mono, one for math, etc. hence the syntax \starttypescript

[<typeface>] [<identifier>]

I see!  So, I'm guessing that it is this <typeface> which connects the
typescripts to the font switching commands like \rm.  My guess is:
<typeface>     switch
serif              \rm
sans              \ss
mono            \tt
math             \mm
??                 \hw
??                 \cg
and that Context only permits these six families?


> > In the typography manual, Hans says,
> > "The third and fourth
> > arguments to \definetypeface are pointers to already declared font
> > sets; these are defined elsewhere."  I think by "font set" he must
> > mean a typescript like garamondprem, but I don't know where  the font
> > set (typescript?) "serif" is or why two font sets need to be pointed
> > to.

> ???

That's how I feel.  The command in question was:
\definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default]
The typography document says that the "[serif] [garamondprem]"
"are pointers to already declared font sets; these are defined elsewhere."
I know now that "[garamondprem]" is the "font set" in your typescript.
I don't know what font set "[serif]" points to or why.


> The same  typography document goes on to explain the fifth
> argument:
> "The fifth argument to \definetypeface specifies specific font size
> setups (if any), these will be covered in section ?? in the next
> chapter."
> This is getting scary, but I'm hoping putting "[optical]" there will
> solve everything.
>
I don't follow.

http://context.aanhet.net/svn/contextman/context-reference/en/co-typography.pdf
says:   "The fifth argument to \definetypeface specifies specific font
size setups (if any), these will be covered in section ?? in the next
chapter."
If this chapter were inserted into the manual, the next chapter would
be about color and backgrounds, so, no luck searching there.
But, I noticed that that fifth argument was filled by "[optical]" at
the bottom of this page:
http://wiki.contextgarden.net/Optical_Size
so:  "\definetypeface [minion-pro] [rm] [serif] [minion-pro] [optical]"



> > I'm confused about how [GaramondPremUpper] and [garamondpremupper]
> > seem to be getting associated with [rm] and [serif] after they were
> > already associated with
> > [GaramondPrem] and [garamondprem].  I don't see how, when I now use \rm, the
> > machine is going to know whether I mean garamondpremupper or garamondprem.
> > The rest of the file seems straightforward.

> In ConTeXt, you are always within a certain bodyfont (the one defined with the \definetypeface command). A switch like \it or \rm will thus take the italic/roman from this bodyfont. Meaning: when you say \setubodyfont[GaramondPrem], it will use "normal" Garamond Premier, if you use \switchtobodyfont[GaramondPremUpper], it will use the superior numbers variant.

Ahhh, okay.  It wasn't intuitive to me, as a user, that a relatively
small change (from, say, oldstyle to superiors) would take a much
bigger switch (of the whole bodyfont) than would a relatively big
change (from, say, roman to italic, which only needs a little \it).  I
wrote a set of font switches once (in LaTeX) that were all little
digraph codes

(major axis: rm, it, sl, ui; minor axis:  rg, ac, sc, sw, in, su, nu,
de, po, pl, to, tl  +  ornaments, which handles all of the variations
that Adobe makes, anyway).  Maybe I'll be able to reproduce it once I
get this working.

> > I get the error:
> > !undefined control sequence
> > <recently read>  \usetypescript
> > l.12 \usetypescript
> >                         [GaramondPrem]

> Then we will need your example - this is not normal behavior.

okay:

First, I put an almost exact copy of your file (with your comments
commented out) in type-garamondprem.tex in
C:\contextminimal\tex\texmf-local
and ran luatools --generate, which seems to see the directory alright.
Then I put the commands:
\usetypescriptfile [type-garamondprem]
\usetypescript [GaramondPremUpper]
\usetypsecript [GaramondPrem]
\setupbodyfont [GaramondPrem,12pt]
 in my preamble, with nothing else.

When I try to run Context, the above error was returned.  For the
record, here is the exact contents of type-garamondprem.tex:

%So we define a set of such features for the different font instances
we want to define.
%In my case, I want regular text with oldstyle figures, small caps
with lining figures, and superior numerals. This goes into your
typescript:

\definefontfeature
 [myroman]
 [protrusion=pure,expansion=quality,script=latn,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes]

\definefontfeature
 [mysmcp]
 [mode=node,script=latn,language=dflt,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes,smcp=yes]

\definefontfeature
 [mysup]
 [mode=node,script=latn,onum=no,pnum=yes,sups=yes]

%Next step: we set up the "normal" and smallcaps font:

\starttypescript [serif] [garamondprem]
 \definefontsynonym [Garamond-Roman]
[name:garamondpremierpro]  [features=myroman]
 \definefontsynonym [Garamond-Bold]
[name:garamondpremierprobold]  [features=myroman]
 \definefontsynonym [Garamond-Italic]
[name:garamondpremierproitalic]  [features=myroman]
 \definefontsynonym [Garamond-Bold-Italic]
[name:garamondpremierprobolditalicc] [features=myroman]
 \definefontsynonym [Garamond-SmallCaps]
[name:garamondpremierpro]  [features=mysmcp]
 \stoptypescript

\starttypescript [serif] [garamondprem]
 \definefontsynonym [Serif]           [Garamond-Roman] [features=myroman]
 \definefontsynonym [SerifItalic]     [Garamond-Italic] [features=myroman]
 \definefontsynonym [SerifBold]       [Garamond-Bold] [features=myroman]
 \definefontsynonym [SerifBoldItalic] [Garamond-Bold-Italic] [features=myroman]
 \definefontsynonym [SerifCaps]       [Garamond-SmallCaps] [features=mysmcp]
\stoptypescript

%Finally, define your first typeface:

\starttypescript [GaramondPrem]
 \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default]
\stoptypescript

%Next step: defining a typeface with superior numbers for footnote
references etc.:

\starttypescript [serif] [garamondpremupper]
 \definefontsynonym [GaramondPremUpper-Roman]
[name:agaramondproregular]  [features=mysup]
 \stoptypescript

\starttypescript [serif] [garamondpremupper]
 \definefontsynonym [Serif]           [GaramondPremUpper-Roman]
[features=mysup]
 \definefontsynonym [SerifItalic]     [Serif]
 \definefontsynonym [SerifBold]       [Serif]
 \definefontsynonym [SerifBoldItalic] [Serif]
 \definefontsynonym [SerifCaps]       [Serif]
 \stoptypescript

\starttypescript [GaramondPremUpper]
 \definetypeface [GaramondPremUpper] [rm] [serif] [garamondpremupper] [default]
\stoptypescript

%Save this typescript somewhere where ConTeXt can find it and run
luatools --generate. To use these in your documents, you need these
lines



Thank you again, this has been a huge help.
___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2010-03-14 13:12 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14 13:12 Michael Saunders [this message]
2010-03-14 13:54 ` simplefonts Henning Hraban Ramm
2010-03-14 13:59 ` simplefonts Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2014-05-21  3:32 SimpleFonts hwitloc
2014-05-21  4:41 ` SimpleFonts Mikael P. Sundqvist
     [not found] <mailman.1.1382176801.27687.ntg-context@ntg.nl>
2013-10-19 12:21 ` Simplefonts John Kitzmiller
2013-10-19 18:20   ` Simplefonts Wolfgang Schuster
2013-10-10 18:02 Simplefonts Wolfgang Schuster
2013-10-12 13:04 ` Simplefonts Zhichu Chen
2013-10-12 17:39   ` Simplefonts Wolfgang Schuster
2013-10-13  9:56     ` Simplefonts Zhichu Chen
2013-10-13 11:12       ` Simplefonts Wolfgang Schuster
2013-10-18 16:18     ` Simplefonts Wolfgang Schuster
2013-10-14 15:17 ` Simplefonts Lars Huttar
2013-10-14 16:45   ` Simplefonts Hans Hagen
2013-10-14 16:38 ` Simplefonts Prashanth
2013-10-14 17:38   ` Simplefonts Wolfgang Schuster
2013-10-15  8:02     ` Simplefonts Otared Kavian
2013-10-15  8:26       ` Simplefonts Hans Hagen
2013-10-15  8:41         ` Simplefonts Mikael P. Sundqvist
2013-10-15  9:12           ` Simplefonts Hans Hagen
2013-10-15 19:12             ` Simplefonts Marcin Borkowski
2013-10-15 19:17               ` Simplefonts Wolfgang Schuster
2013-10-15 20:00                 ` Simplefonts Marcin Borkowski
2013-10-15 20:58               ` Simplefonts Hans Hagen
2013-10-15  9:26           ` Simplefonts Hans Hagen
2013-10-15  9:57             ` Simplefonts Hans Hagen
2013-10-15 11:42         ` Simplefonts Keith J. Schultz
2013-10-15 17:08           ` Simplefonts Wolfgang Schuster
2013-10-16  7:47             ` Simplefonts Keith J. Schultz
2013-10-15 17:41         ` Simplefonts Otared Kavian
2013-10-15 12:18     ` Simplefonts Prashanth
2011-03-11 12:28 Simplefonts Charles Doherty
2011-03-11 18:30 ` Simplefonts Wolfgang Schuster
2011-03-14 11:55   ` Simplefonts Charles Doherty
2011-02-21 16:38 Simplefonts Charles Doherty
2010-11-13 18:25 simplefonts Herbert Voss
2010-11-13 18:32 ` simplefonts Aditya Mahajan
2010-11-13 18:37   ` simplefonts Herbert Voss
2010-11-13 18:47     ` simplefonts Khaled Hosny
2010-11-13 18:44 ` simplefonts Wolfgang Schuster
2010-11-13 19:16   ` simplefonts Herbert Voss
2010-03-15  2:48 simplefonts Michael Saunders
2010-03-13 16:09 simplefonts Michael Saunders
2010-03-13 16:36 ` simplefonts Wolfgang Schuster
2010-03-13 20:13 ` simplefonts Thomas A. Schmitz
2010-03-12 19:11 simplefonts Michael Saunders
2010-03-12 19:24 ` simplefonts Aditya Mahajan
2010-03-12 19:32 ` simplefonts Hans Hagen
2010-03-12 20:11 ` simplefonts Thomas A. Schmitz
2010-03-12 20:17   ` simplefonts Wolfgang Schuster
2010-03-12 20:31   ` simplefonts Andreas Harder
2010-03-12 20:38   ` simplefonts Wolfgang Schuster
2010-03-12 22:29     ` simplefonts Hans Hagen
2010-03-13  5:35       ` simplefonts Wolfgang Schuster
2010-03-13  6:19         ` simplefonts Khaled Hosny
2010-03-13 12:16           ` simplefonts Hans Hagen
2010-03-13 12:26             ` simplefonts Wolfgang Schuster
2010-03-13 12:35               ` simplefonts Hans Hagen
2010-03-13 13:27               ` simplefonts Andreas Harder
2010-03-13 16:17                 ` simplefonts Wolfgang Schuster
2010-03-13 16:59                   ` simplefonts Andreas Harder
2010-03-13 17:29                     ` simplefonts Wolfgang Schuster
2010-03-12 10:05 simplefonts Michael Saunders
2010-03-12 12:45 ` simplefonts Wolfgang Schuster
2010-03-12  4:50 simplefonts Michael Saunders
2010-03-12  5:36 ` simplefonts Wolfgang Schuster
     [not found] <mailman.580.1258822015.22155.ntg-context@ntg.nl>
2009-11-21 21:33 ` simplefonts Vyatcheslav Yatskovsky
2009-11-22 12:24   ` simplefonts Wolfgang Schuster
2009-11-22 13:10     ` simplefonts Alan BRASLAU
2009-11-22 13:13       ` simplefonts Wolfgang Schuster
2009-11-22 13:16       ` simplefonts Alan BRASLAU
2009-09-14 11:06 simplefonts Wolfgang Schuster

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=54d7f5601003140612q60e57ccctc1dba0df39454a32@mail.gmail.com \
    --to=odradek5@gmail.com \
    --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).