From: Hans Hagen <pragma@wxs.nl>
Subject: Re: definetypeface vs math symbols
Date: Tue, 11 Jul 2006 10:02:25 +0200 [thread overview]
Message-ID: <44B35B11.7070608@wxs.nl> (raw)
In-Reply-To: <44B34ED4.7060302@brainbot.com>
Ralf Schmitt wrote:
> Hans Hagen wrote:
>
>> \definetypeface [charter] [it] [italics] [modern] [default][encoding=ec]
>> \definetypeface [charter] [bf] [bold] [modern] [default] [encoding=ec]
>>
>> does not make sense,
>>
>
> ack
>
>
>> \usetypescript[serif][charter][ec]
>> \definetypeface [charter] [rm] [serif] [charter] [default] [encoding=ec]
>> \definetypeface [charter] [mm] [math] [modern] [default] [encoding=ec]
>> \definetypeface [charter] [tt] [mono] [charter] [default] [encoding=ec]
>>
>> \setupbodyfont [charter, 11pt] % rm si default since defined first
>>
>>
>
> and what is surprising to me: order does matter here. If I put the
> definetypeface for math mode command at the front, {\bf bold} does not
> work anymore.
>
indeed, this is because the first one defined is the default (think of typefaces that only have ss, like optima)
so, this may work when rm, tt or ss is defined first
\setupbodyfont [charter, 11pt]
but this is more robust
\setupbodyfont [charter, rm, 11pt]
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.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-07-11 8:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 7:10 Ralf Schmitt
2006-07-10 8:03 ` Thomas A. Schmitz
2006-07-10 9:01 ` Ralf Schmitt
2006-07-10 9:48 ` Thomas A. Schmitz
2006-07-10 10:19 ` Ralf Schmitt
2006-07-10 12:02 ` Ralf Schmitt
2006-07-10 21:05 ` Hans Hagen
2006-07-11 7:10 ` Ralf Schmitt
2006-07-11 8:02 ` 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=44B35B11.7070608@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).