ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Idris Samawi Hamid <ishamid@attbi.com>
Cc: ntg-context@ntg.nl
Subject: Re: Let's try again:-> [was Re: One last thing:-)]
Date: Thu, 18 Apr 2002 15:35:35 -0600	[thread overview]
Message-ID: <FA4XFBSDZU94GF216ZB7SOVU31KJWS.3cbf3c27@c1909372-a> (raw)
In-Reply-To: <5.1.0.14.1.20020418092920.032b2ed0@server-1>

>>1. Why does this work? What is the difference between <Naskh> and <Naskh
>>sa 1>?
:
>so, sa 1 like definitions adapt themselves (and this is how for instance 
>getglyph in symbol defs can adapt itsef nicely)

So I think I understand this now:

Although <SomeFont> and <SomeFont sa 1> denote the same font and size, the body font size and magnifications like x, xx, small, and big are generated as functions of the scale factor. So if 
the scale factor like <sa 1> is not present, then the scaling does not get done, and so \tfx etc. and [myfont, 12pt] don't do any scaling. But \tfa, \tfb, etc still work because these are explicitly 
defined in terms of \magstep which will scale <SomeFont> even without the <sa 1>. 

Am I understanding this correctly? I will probably mention this in an upcoming font how-to.

Thnx again.

Best wishes
Idris

==========================
Dr. Idris Samawi Hamid
Depatment of Philosophy
Colorado State University
Fort Collins, CO 80526


  reply	other threads:[~2002-04-18 21:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12 20:34 typescripts faq-in-progress Idris Samawi Hamid
2002-04-13 18:52 ` Eureka! [was Re: typescripts faq-in-progress] Idris Samawi Hamid
2002-04-13 22:17   ` Hans Hagen
2002-04-14  0:14     ` Idris Samawi Hamid
2002-04-14  0:31     ` \definefontstyle Idris Samawi Hamid
2002-04-14  5:58       ` small sizes Idris Samawi Hamid
2002-04-14 21:28       ` ConTeXt bug (size-changing)? Idris Samawi Hamid
2002-04-15  8:44         ` Hans Hagen
2002-04-16  1:36           ` Idris Samawi Hamid
2002-04-16  1:50           ` small feature request Idris Samawi Hamid
2002-04-16 11:26             ` Hans Hagen
2002-04-16 20:53               ` Idris Samawi Hamid
2002-04-15  9:18         ` ConTeXt bug (size-changing)? Hans Hagen
2002-04-15 15:48           ` Idris Samawi Hamid
2002-04-15 21:34           ` One last thing:-) Idris Samawi Hamid
2002-04-16 11:13             ` Hans Hagen
2002-04-16 20:44               ` Idris Samawi Hamid
2002-04-17  7:53                 ` Hans Hagen
2002-04-17 14:32                   ` Let's try again:-> [was Re: One last thing:-)] Idris Samawi Hamid
2002-04-17 17:50                     ` Hans Hagen
     [not found]                       ` <BARL64B0NJ6ZPMVQ3OKNJDB3HF0LI.3cbe21da@c1909372-a>
2002-04-18  7:32                         ` Hans Hagen
2002-04-18 21:35                           ` Idris Samawi Hamid [this message]
     [not found]                       ` <3CBE43E9.7565CE19@gcmail.maricopa.edu>
2002-04-18  7:36                         ` Lucida Bright fonts Hans Hagen
     [not found]                           ` <3CC0CC3C.7218C29C@gcmail.maricopa.edu>
2002-04-20 23:24                             ` Hans Hagen
2002-04-18 21:59       ` \definefontstyle Idris Samawi Hamid
2002-04-13 22:31   ` Eureka! [was Re: typescripts faq-in-progress] Henning Hraban Ramm
2002-04-14  9:56     ` 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=FA4XFBSDZU94GF216ZB7SOVU31KJWS.3cbf3c27@c1909372-a \
    --to=ishamid@attbi.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).