Re: Setting up lbr fonts

[Hans Hagen <pragma@wxs.nl>]

At 11:56 AM 1/24/2002 +0100, Jens-Uwe Morawski wrote:

>What means/does [name] here?
>
>When i declare a [serif] typescript, why i need:
>\definefontsynonym [Serif]      [Palatino]

name identifier this script as mapping a name onto a style; the 
\definetypeface macro uses this to identify what it should load (it looks 
for name, size and map scripts

>In my opinion this is redundant.

it depends, you may indeed skip that one but then you cannot write style 
files using the more symbolic Serif instead of Palatino; I tend to write 
styles independent of the font

Or the same question from another point of view: When the font-commands
>use or look for Serif, SerifBold ... why the typescript must be declared 
>as [serif]?

you can name it anything you want, this 'serif' is used to locate the 
script with \definetypeface,

   \starttypescript [fancyshape] ....

combined with

   \definetypeface [..] [..] [fancyshape]

would work as well.

>or what would mean a [sans] typescript with the same
>  \definefontsynonym [Serif...] [...] definitions?

you can do that but it does not make sense, however, some font shapes have 
alternatives, think of

   [lightserif]

so, you can organize your fonts (univers has for instance many 
alternatives) accordingly and map 'm onto different typefaces,

\definetypeface [normal] [rm] [serif] ....
\definetypeface [light]  [rm] [lightserif] ....

> > The next thing is using this font. Of course you can execute typescripts
> > yourself but best is to use the command
> >
> > \definetypeface [myface] [rm] [serif] [adobepalatino] [default] 
> [encoding=ec]
>
>Here again. As far as i understand the font-switching-macros use the 
>declarations
>like Serif, or SerifBold. In this case: why i have to declared it as [rm] too?

actually the chain is:

rmtf <- Serif     <- Palatino     <- fontname.tfm
rmbf <- SerifBold <- PalatinoBold <- boldfontname.tfm

so, rmtf, rmbf etc are the internal names ; the rm/ss/tt/hw/cf etc make up 
a (traditional) collection of familied (in terms of tex) fonts. If you skip 
the typescript altogether, you can use \definefont to set these, like

\definefont [rm] [10pt] [tf=fontname sa 1, bf=boldfontname sa 1]

>Or, why i need 'rm' in the next declaration? 'myface' is already defined 
>as 'rm'
> >
> > \setupbodyfont[myface,10pt,rm]
> >

within a typeface there can be rm,ss,etc and the default is the one defined 
first. Here indeed the rm could be omited, but it does not hurt either.

>Hmm, many questions, which show that i understand nothing ;)
>
>And another question: fontinst generates some fonts including
>symbols like degree. upright-mu or the registered-symbol. These
>are in (LaTeX) TS1 encoding. What declarations are needed to use them?

you can define them as symbols

\definesymbol [registered] [\getglyph{Serif}{\char123}]  % or 
{Palatino}{\char123} or {fontname}{\char123} or take your choice

these will scale with the current font size. The problem with these symbols 
is that because they are not always present in a font, we cannot add them 
to encoding vectors.

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                                   fall-back web server: 
www.pragma-pod.nl
-------------------------------------------------------------------------