ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font question
Date: Wed, 05 Mar 2008 10:17:33 +0100	[thread overview]
Message-ID: <47CE652D.3080404@elvenkind.com> (raw)
In-Reply-To: <20080304225545.GA20252@atos.labs.wmid.amu.edu.pl>



Marcin Borkowski wrote:
> OK, so the first part of my questions about mfonts.pdf;)
> 
> Thank you in advance for the answers; I'd like to stress that I'm not in
> a hurry, so please take your time!  Also, as I said, I have nothing
> against being "redirected" to some other part of documentation in case
> it is easier than to write a full answer here.
> 
> 1. Do I get it right when I think that \definefontsynonym takes 2 or 3
> arguments, and:
> 
> When given two, they mean: (1) the synonym being defined
> and (2) an earlier defined synonym being a "replacement text" for (1);
> 
> When given three, (1) is as above, (2) is the filename of the font (tfm
> I guess?) and (3) contains some low-level options like the encoding 

That sounds right.

> (are there any other options available?)

I think you can also define:

   mapping  % for xetex (?)
   handling % for an experimental pdftex font feature
   features % mostly for mkiv

But all the first two are somewhat experimental, and features are only
really useful for opentype fonts. All three are relatively new and not
documented in mfont.pdf yet.

> 2. What does exactly sa mean?  Do I get it right when I think that it's
> the factor by which the "body font size" - i.e., some constant dimen
> parameter defined for the whole document (or environment) - is
> multiplied?  Does the "laziness" of sa mean that the actual scaling will
> happen _after_ the definition of the body font size, which might be e.g.
> different for different components of a product within a project using a
> common environment?  And what is mo?

sa stands for "scaled at", mo stands for "mapped on".

One of them (I think sa) is a multiple of the value you specify at
   \setupbodyfont[..] or \switchtobodyfont[..],
the other is (I think) in relation to the actual current font size
(so it is different whether \tfx or \tfa is in effect).

> 3. What are the arguments to \definebodyfont?

  #1  size (5pt ... 12pt default)
  #2  family (rm ss tt mm hw cg)
  #3  font definitions (tf = ..., etc.)

> 4. What are the relations between \definefontsynonym, \definefont and
> \definebodyfont?

things defined with \definefontsynonym can be used in the right hand
side of assignments in arg #3 of \definebodyfont, and in the #2
argument of \definefont.

\definefont has no real relation to font switching, it is just a
low-level shortcut for a specific font, much like a bare \font
command in plain TeX, except that it allows synonyms and sa/mo.

\definebodyfont is used to build up font collections

> 5. I can understand neither the paragraph right before the
> \definebodyfont example on page 4 of mfonts.pdf, nor the example itself.

That paragraph is a bit confusing to me as well. Browsing through
type-siz.tex may help (in tex/context/base).

Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-03-05  9:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 19:42 Marcin Borkowski
2008-02-29 20:54 ` Hans Hagen
2008-02-29 22:31   ` Marcin Borkowski
2008-02-29 22:57     ` Hans Hagen
2008-03-01  0:17       ` Marcin Borkowski
2008-03-01  0:22         ` Idris Samawi Hamid
2008-03-02  8:48           ` Marcin Borkowski
2008-03-02 13:08             ` Mojca Miklavec
2008-03-02 13:20               ` Wolfgang Schuster
2008-03-04 20:58               ` Marcin Borkowski
2008-03-04 21:09                 ` Wolfgang Schuster
2008-03-04 21:49                   ` Marcin Borkowski
2008-03-05  8:40                 ` Hans Hagen
2008-03-04 22:55     ` Marcin Borkowski
2008-03-05  6:55       ` Thomas A. Schmitz
2008-03-05 14:23         ` Marcin Borkowski
2008-03-05  9:17       ` Taco Hoekwater [this message]
2008-03-05 14:29         ` Marcin Borkowski
2008-03-11 14:07         ` Marcin Borkowski
  -- strict thread matches above, loose matches on Subject: below --
2005-12-12 15:32 Font Question Henry Blodgiitt
2005-12-07 22:46 Aditya Mahajan
2005-12-07 23:45 ` Adam Lindsay
2005-12-08  0:05   ` Aditya Mahajan
2005-12-07 23:55 ` Hans Hagen
2002-02-19 15:04 font question Frans Goddijn
2002-02-19 16:32 ` Bill McClain
2002-02-19 17:22   ` Frans Goddijn
2002-02-19 18:31     ` Bill McClain
     [not found]     ` <003701c1b976$6ab1c800$0100a8c0@digitpaint.nl>
2002-02-19 21:27       ` Frans Goddijn
2002-02-20 12:39         ` Bill McClain
2002-02-20 18:47         ` W. Egger
2001-08-02 17:01 Font Question Marco Kuhlmann
2001-08-03 14:01 ` Hans Hagen
2001-08-05 21:02   ` Marco Kuhlmann
2001-08-06  7:42     ` 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=47CE652D.3080404@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).