ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@atos.wmid.amu.edu.pl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font question
Date: Tue, 11 Mar 2008 15:07:52 +0100	[thread overview]
Message-ID: <20080311140752.GB19259@atos.labs.wmid.amu.edu.pl> (raw)
In-Reply-To: <47CE652D.3080404@elvenkind.com>

Dnia Wed, Mar 05, 2008 at 10:17:33AM +0100, Taco Hoekwater napisa&#322;(a):

Thanks for the answers; still, some things are not clear for me.

> > 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).

Still don't get it.  I tried the following example, just to see what
happens (sorry, I know it looks terrible):

\definefont [TitleFont] [Serif sa b]
\definefont [TitleFontTwo] [Serif mo b]
\starttext
Hello World!\par
{\TitleFont Hello world!\par}
{\TitleFontTwo Hello world!\par}
And with viii:
{\viii
Hello World!\par
{\TitleFont Hello world!\par}
{\TitleFontTwo Hello world!\par}}
And with switchtobodyfont:
{\switchtobodyfont[8pt]
Hello World!\par
{\TitleFont Hello world!\par}
{\TitleFontTwo Hello world!\par}}
\stoptext

No difference between sa and mo using this example...

(Right after looking at the results, I \show-ed \viii and noticed that
\viii and \switchtobodyfont[8pt] do essentially the same.  What's the
use of having them both?)

> > 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.

So to be sure: I can use names defined by \definefontsynonym in place of
font filenames?

> 
> \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.

So it just _defines_ (what a surprise!) some command to be a
font-switching macro?

> 
> \definebodyfont is used to build up font collections

Still, I have no idea about the relation between these three...

Here's what I seem to understand now:

\definebodyfont is a mystery to me;

\definefontsynonym defines #1 to mean the same as #2, where #2 may be
another "synonym" or a filename (and then you have - or may? - provide
encoding informaction in #3).  It doesn't support sa or mo, and that's
ok, because its use is just fiddling with _names_;

\definefont is similar to \definefontsynonym except that it allows
scaling and does not allow filenames (only "synonyms").

How much of that is right?

> > 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).

I'll try that too soon...

> 
> Best wishes,
> Taco

Thanks in advance

-- 
Marcin Borkowski (http://mbork.faculty.fmcs.amu.edu.pl)

Nie wiesz nawet, jak cenny jesteś w Moich oczach!

                                Jezus
___________________________________________________________________________________
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-11 14:07 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
2008-03-05 14:29         ` Marcin Borkowski
2008-03-11 14:07         ` Marcin Borkowski [this message]
  -- 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=20080311140752.GB19259@atos.labs.wmid.amu.edu.pl \
    --to=mbork@atos.wmid.amu.edu.pl \
    --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).