ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: A font question.
Date: Fri, 23 Dec 2005 10:19:55 +0100	[thread overview]
Message-ID: <43ABC13B.1050903@wxs.nl> (raw)
In-Reply-To: <43ABAAFC.9000902@elvenkind.com>

Taco Hoekwater wrote:

> Hi John,
>
> John R. Culleton wrote:
>
>> I use Context for highly formatted non-fiction, but I am a bit
>> reluctant to use it for much of my work because of the strange
>> (to me) font handling arrangements. I see no purpose for the
>> multiple synonyms of the same font. That just adds layers of
>> extra work.
>
>
> It also adds layers of configurability. Clearly you do not
> need that (your font setups is extremely simple and low-level),
> but lots of other people do. For example, I have documents that
> use 6 totally different font sets, because all 'examples' and
> 'definitions' are typeset in font families that differ from
> the normal text font family. It would be a nightmare if I had to
> define and remember the 200+ font definitions by hand.


Also, when you want some special size, by using the synonyms you can say 
\definedfont[Serif at 123pt] without worrying about what the current 
serif is.

Many years ago, Taco wrote a style for the dutch math journal which had 
several font sets, complex columns, mixed encodings per document, etc  
(i still do not understand how he managed to do it in those-days context 
-). A few years later when some specs changed I was asked to rewrite 
those styles and in the process typescripts (font classes), column sets 
(complex figure placement) and some more things evolved.  Since then 
Taco and I have less nighmares -)

>> So here is my question. If I set up my own font definition
>> system and as part of it I have statements like:
>> \font\tfa bchr8r at 10.45pt
>> \font\tfb bchr8r at 11.37pt
>> ...
>> ... will the rest of Context accept the above tfb font and size in 
>> places
>> where a heading macro automatically defaults to tfb?
>
>
> Only if you never make any \{setup,switchto}bodyfont switches after
> your new font definitions.


if you want that, you'd say:

\definefont[MyNiceBigFont][bchr8r at 10.45pt]

or better:

\usetypescript [serif] [charter] [ec]

\definefont[MyNiceBigFont][Charter-Roman at 10.45pt]

in which case you at least see what font is used, and more important, 
you get the encoding for free

\setuphead[chapter][style=\MyNiceBigFont]

btw, if there is a system behind those sizes, you can say:

\definebodyfontenvironment
  [default]
  [a=1.045,
   b=1.137]

and such which lets the a-d sizes scale that way


Hans

      reply	other threads:[~2005-12-23  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 23:11 John R. Culleton
2005-12-23  7:45 ` Taco Hoekwater
2005-12-23  9:19   ` 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=43ABC13B.1050903@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).