From: Hans Hagen <pragma@wxs.nl>
Cc: NTG-ConTeXt <ntg-context@ntg.nl>
Subject: Re: [ConTeXt] Math fonts: cal etc.
Date: Mon, 05 Jul 1999 20:13:50 +0200 [thread overview]
Message-ID: <3780F5DE.EE4E699C@wxs.nl> (raw)
In-Reply-To: <3780EE97.99EDCF6A@gmx.de>
Tobias Burnus wrote:
> Maybe better:
> \definefont [fraktur] [Fraktur sa \currentfontscale]
> \definefont [gothic] [Gothic sa \currentfontscale]
> \definefont [caligraphic] [Caligraphic sa \currentfontscale]
> \def\frak #1{\ifmmode\hbox{\fractur #1}\else\factur #1\fi}
> \def\goth #1{\ifmmode\hbox{\gothic #1}\else\gothic #1\fi}
> \def\cal #1{\ifmmode\hbox{\caligraphic #1}\else\caligraphic #1\fi}
The problem is that the ones I mentioned are already defined, and I want
to remain upward compatible.
> (so small letters), I don't know whether it is possible with Fraktur to obtain
> umlauts, ligatures etc., if not I think this is also a ''math only'' candidate.
If the encoding is right, it should work, otherwise something should be
cooked up, but I fear it only works ok for a normal encoded font.
> \definefontsynonym [RalfSmithFS] [rsfs10]
> \definefont [ralfsmithfs] [RalfSmithFS sa \currentfontscale]
> \def\rsfs #1{\ifmmode\hbox{\ralfsmithfs #1}\else\ralfsmithfs #1\fi}
>
> The question is: Where should we put something like this?
If you use it as caligraphic, then I would say:
\definefontsynonym[RalfSmithFormalScript] [rsfs10] % goes into
font-fil.tex
\definefontsynonym[Caligraphic][RalfSmithFormalScript] % goes into a
style/preamble
So, no separate font file is needed, just a setting in the preamble of
your document (or your local cont-sys.tex file). I've added the rsfs
entry to font-fil.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-07-05 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-05 13:28 Tobias Burnus
1999-07-05 14:27 ` Hans Hagen
1999-07-05 17:42 ` Tobias Burnus
1999-07-05 18:13 ` Hans Hagen [this message]
1999-07-06 12:47 ` Ed L. Cashin
1999-07-06 13:17 ` Hans Hagen
1999-07-06 15:03 ` Ed L. Cashin
1999-07-06 15:13 ` Hans Hagen
1999-07-06 15:37 ` Ed L. Cashin
1999-07-07 8:42 Gilbert van den Dobbelsteen
1999-07-07 21:39 ` 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=3780F5DE.EE4E699C@wxs.nl \
--to=pragma@wxs.nl \
--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).