From: Hans Hagen <pragma@wxs.nl>
Cc: "ConTeXt" <ntg-context@ntg.nl>
Subject: Re: More fonts
Date: Sun, 28 Jan 2001 20:06:34 +0100 [thread overview]
Message-ID: <3.0.6.32.20010128200634.0093cb40@server-1> (raw)
In-Reply-To: <000001c087e0$4af3f560$a3ccfea9@nuovo>
At 08:30 PM 1/26/01 +0100, Giuseppe Bilotta wrote:
>Hello, I have a couple of font questions.
>
>(1) how do I tell ConTeXt that I want to use the AMS font family too? More in
>general, how do I tell ConTeXt to load a font module?
Some fonts are predefined in font-* modules. These can be loaded with
\setupbodyfont[ams]
local defs (often document dependent) can best go into document environment
files.
>(2) it would be nice if texexec-ing a module to obtain a documentation would
>give a sample of the font/symbols defined in the module.
Most mechanism's can show you fonts and encodings, just search for \show...
commands.
>(3) in the enco-fro module (Romanian font switches) I've seen that you
define
>some compound characters; noticeably, the "s, "t, "S and "T are mapped to the
>correspective "cedilla" chars; I'm not the right person to discuss this, but
>IIRC in Romania they use a comma under thos letters, and not a cedilla;
again, I
>don't know of a "comma below" TeX accent ... can somebody clarify this to me,
>please?
Unless there are real glyphs, you need to fall back on hacks. In the new
encoding files, you will find named glyphs and fallback methods.
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
-------------------------------------------------------------------------
prev parent reply other threads:[~2001-01-28 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 19:30 Giuseppe Bilotta
2001-01-28 19:06 ` Hans Hagen [this message]
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=3.0.6.32.20010128200634.0093cb40@server-1 \
--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).