On Thu, 24 Jan 2002 14:23:08 +0100
Hans Hagen <[EMAIL PROTECTED]> 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.
Can i use the \definesymbol declaration in typescripts in order to
make the symbol-name<-->slot mapping local?
> 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.
Regards,
Jens
