Re: Setting up lbr fonts

[Hans Hagen <pragma@wxs.nl>]

At 08:25 AM 1/25/2002 +0100, Jens-Uwe Morawski wrote:
>On Thu, 24 Jan 2002 14:23:08 +0100
>Hans Hagen <pragma@wxs.nl> wrote:
>
> > >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
>
>In mfonts.pdf is shown how font-style switches (\bf, ...)
>automatically apply to the Euro-Symbol.
>
>Is it enough when i say
>\definefontsynonym [PalatinoSymbols] [<TS1-Font>]
>\definefontsynonym [PalatinoSymbolsBold] [<TS1-Bold-Font>]
>
>\definefontsynonym [SerifSymbols] [PalatinoSymbols]
>\definefontsynonym [SerifSymbolsBold] [PalatinoSymbolsBold]
>
>\definesymbol [registered] [\getglyph{SerifSymbols}{\char123}]
>
>to reach the same automatism.

indeed, the getglyph macro tries to resolve size (x,xx,1,a,b,c,d,..) as 
well as style (Bold, BoldSlanted,...).

>Can i use the \definesymbol declaration in typescripts in order to
>make the symbol-name<-->slot mapping local?

in principle you can put anythinhg in a typescript, but it's not local

btw, interesting point; maybe i should add fontclass/encoding specific symbols

   \definesymbol[registered] [{\symbol[\currentencoding-registered]}]

   \definesymbol[texnansi-registered][\getglygh{SerifSymbols}{\char123}]

that one switches with the encoding, the next with the typeface

   \definesymbol [registered] [{\symbol[\fontclass-registered]}]

   \definesymbol [somename-registered] [...]

with somename being the typeface;

actually, i think that i could even automate that; will think about it. 
that way we can mix any combination of fonts / symbols

[one of the ideas behind typefaces/scripts is that one can mix in one doc 
complete different font families without clashes]

> > 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.
>
>In both cases
>- declaring a symbol
>- using a symbol from a predefined encoding
>  one must know which symbols are available, thus some predefined
>  symbol-declarations could make the life easier. TS1 s a good
>  starting-point, since it includes most of the symbols commonly available
>  in commercial fonts. But i see, there is no good integration in texfont.

sure, but for that i depend on users; these things can go into the symb-* files

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
-------------------------------------------------------------------------