From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Setting up lbr fonts
Date: Fri, 25 Jan 2002 08:25:13 +0100 [thread overview]
Message-ID: <20020125082513.4dd06657.morawski@gmx.net> (raw)
In-Reply-To: <5.1.0.14.1.20020124140116.02db2aa8@server-1>
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.
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
next prev parent reply other threads:[~2002-01-25 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 11:45 Randall Skelton
2002-01-22 12:28 ` Hans Hagen
2002-01-23 1:44 ` Jens-Uwe Morawski
2002-01-23 8:54 ` Hans Hagen
2002-01-24 10:56 ` Jens-Uwe Morawski
2002-01-24 13:23 ` Hans Hagen
2002-01-25 7:25 ` Jens-Uwe Morawski [this message]
2002-01-25 9:46 ` Hans Hagen
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=20020125082513.4dd06657.morawski@gmx.net \
--to=morawski@gmx.net \
/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).