ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Idris S Hamid <ishamid@attbi.com>
Subject: Re: \switchtobodyfont[cmr]  in Gamma
Date: Wed, 13 Nov 2002 12:07:23 -0800	[thread overview]
Message-ID: <200211131207.23863.ishamid@attbi.com> (raw)
In-Reply-To: <5.1.0.14.1.20021112092521.00ad1ab0@server-1>

On Tuesday 12 November 2002 00:31, Hans Hagen wrote:
> >-------------cm-test.tex--------------
> >\input m-gamma.tex
> >\input type-omg.tex
> >
> >\setupbodyfont[cmr,14pt]
> >%\setupbodyfont[omlgc, 14.4pt]
> >
> >This is a test
> >
> >\switchtobodyfont[omlgc, 14.4pt]
> >%\switchtobodyfont[cmr,14pt]
> >
> >This is a test
> >
> >\switchtobodyfont[cmr, 14pt]
> >%\switchtobodyfont[omlgc, 14.4pt]
> >
> >This is a test
> >
> >\stoptext

> in my type-omg i see no omlgc defined, so \setupbodyfont[cmr,14pt]

Eh? The following is at the end of the official tpe-omg.tex:

------------------------------
\starttypescript [OmegaLGC]

  \definebodyfontenvironment
    [omlgc]
    [default]
    [interlinespace=2.8ex]

  \definetypeface [omlgc] [rm] [serif] [omega] [omega]
  \definetypeface [omlgc] [tt] [mono] [omega] [omega]

\stoptypescript
-----------------------------------

and \switchtobodyfont[omlgc] is used throughout m-gamma.tex. 
And it works:-)

> \setupbodyfont[cmr, 14pt]        This is a test \fontname\font \par
> \switchtobodyfont[omlgc, 14.4pt] This is a test \fontname\font \par
> \switchtobodyfont[cmr, 14pt]     This is a test \fontname\font \par
>
> gives me expected behavior.

Are you sure? I get 

This is a test omlgc at 14.0pt

in omlgc of course. 

Are you sure there's not a bug somewhere else? I have my own private fonts

\definetypeface [mtnaskh] [rm] [naskh] [mtnaskhi] [mtnaskhi] [rscale=1.6]

and when I do a switch to omlgc it works fine.  I always enclose omlgc in its 
own group as well. But when I switch to cmr in its own group it does not work 
at all.

I bet that if I replaced all the fonts in type-omg.tex with cmr it would work 
with no problem. There must be something else afoot.

>
> When mixing fonts, esp with similar names, and esp in an ungrouped way,
> it's best to use the typeface mechanism, since it provides a namespace,
> while the less clever mechanism overloads definitions (keep in mind that
> there are some limitations to the amount of fonts and memory, so there are
> some trade off's)

I will study the xchange between u and Giuseppe and see if I can make sense of 
this. Stay tuned.

Best wishes
Idris

-- 
Dr. Idris S Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523

  parent reply	other threads:[~2002-11-13 20:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11 22:48 Idris S Hamid
2002-11-11 21:56 ` Giuseppe Bilotta
2002-11-11 23:28 ` Giuseppe Bilotta
2002-11-12  1:02   ` Idris S Hamid
2002-11-12  8:31 ` Hans Hagen
2002-11-12 14:06   ` Re[2]: " Giuseppe Bilotta
2002-11-12 18:12     ` Hans Hagen
2002-11-12 22:10       ` Re[3]: " Giuseppe Bilotta
2002-11-13  8:39         ` Hans Hagen
2002-11-13 11:31           ` Re[4]: " Giuseppe Bilotta
2002-11-13 16:16             ` Hans Hagen
2002-11-13 20:25           ` Re[3]: " Idris S Hamid
2002-11-13 20:07   ` Idris S Hamid [this message]
2002-11-12 11:59 ` Matthew Huggett
2002-11-13 19:53   ` Idris S Hamid
2002-11-13 22:16 ` Idris S Hamid
2002-11-13 23:06   ` Idris S Hamid

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=200211131207.23863.ishamid@attbi.com \
    --to=ishamid@attbi.com \
    --cc=ntg-context@ref.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).