From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Some things I don't understand about typescripts...
Date: Thu, 22 Dec 2005 14:52:08 +0100 [thread overview]
Message-ID: <43AAAF88.7080407@elvenkind.com> (raw)
In-Reply-To: <33BAB34E-1DC8-4F25-AD0C-1049AEA329B3@uni-bonn.de>
Thomas A. Schmitz wrote:
> Christmas is approaching, and I hate to be a pest this time of the
> year, but there's this problem that really bothers me: I'm still
> working hard to release version 2 of my Greek module on the
> unsuspecting masses. It will define all fonts in a typescript instead
> of as single fonts to allow switches like {\em } etc. It appears that
> the typescript mechanism creates some problems. The most serious one
> for me is that it seems to demand a full list of sizes that can be used
> in this form:
>
> \definebodyfont
> [30pt,25pt,20pt,18pt,17.3pt,14.4pt,14pt,12pt,11pt,11.5pt,10pt,9pt,8pt,
> 7pt,6pt,5pt,4pt]
> [rm]
> [default]
This
\definebodyfont [default] [rm] [tf=, ] % ...
should work, afaik
> If I specify a bodyfont with a size that's not in this list
> \setupbodyfont[somebodyfont,19.7pt]
> I get no errors, but no output either :-( If I add 19.7pt to the list,
> everything works again. Is there an explanation for this behavior?
Before that call, you may need to do
\definebodyfontenvironment [19.7pt]
as well (not sure)
> It also looks like I should define a math font for these Greek fonts.
> It looks like ConTeXt will try to get certain symbols from math if
> they're not defined in the bodyfont. Is there a syntax for creating a
> default math font for an entire set of typescripts? I tried this
>
> \starttypescript
> \definetypeface [all] [mm] [math] [times] [default]
> [encoding=default]
Replacing [all] with [tsgreek] (or whatever you typescript is named)
should work.
Hope this helps,
Taco
next prev parent reply other threads:[~2005-12-22 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 12:08 Thomas A. Schmitz
2005-12-22 13:52 ` Taco Hoekwater [this message]
2005-12-22 14:43 ` Thomas A. Schmitz
2005-12-22 14:50 ` Taco Hoekwater
2005-12-22 14:58 ` Taco Hoekwater
2005-12-22 21:08 ` Hans Hagen
2005-12-22 22:21 ` Taco Hoekwater
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=43AAAF88.7080407@elvenkind.com \
--to=taco@elvenkind.com \
--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).