From: Idris S Hamid <ishamid@attbi.com>
Subject: Re: Re[3]: \switchtobodyfont[cmr] in Gamma
Date: Wed, 13 Nov 2002 12:25:41 -0800 [thread overview]
Message-ID: <200211131225.41164.ishamid@attbi.com> (raw)
In-Reply-To: <5.1.0.14.1.20021113093752.00adeb20@server-1>
On Wednesday 13 November 2002 00:39, Hans Hagen wrote:
> At 11:10 PM 11/12/2002 +0100, you wrote:
> >Tuesday, November 12, 2002 Hans Hagen wrote:
> > >>I never managed to get typeface working correctly, other than
> > >>defining things similarly to type-pre and using those with
> > >>\switchbodyfont. Is there any documentation on how to *use*
> > >>typefaces (not *define* them)?
> >
> >HH> define:
> >
> >HH> \definetypeface[mainface][....]
> >
> >HH> then use 'm:
> >
> >HH> \setupbodyfont[mainface]
> >
> >Something like this?
>
> You forgot to load the typescripts
>
> \usetypescript [modern] [texnansi]
> \usetypescript [postscript] [texnansi]
It's still not working, even with grouping!
--------------------------------------------------
\usetypescript [modern] [texnansi]
%\usetypescript [postscript] [texnansi]
\starttext
\switchtobodyfont[modern]
This is a test
\switchtobodyfont[omlgc]
This is a test
{\switchtobodyfont[modern]
This is a test [This is STILL in omlgc!]}
\stoptext
----------------------------------------------------
Also, uncommenting %\usetypescript [postscript] [texnansi] cause omega's
capacity to be exceeded. Which texmf.cnf values should I increase?:***
----------------------
! Omega capacity exceeded, sorry [number of strings=3265].
\dosetunexpanded ...sname #2\endcsname \endcsname
}\@EA #1\@EA {\@EA \s!do
\...
\@@expanded ...d \setgvalue {postscript17.3pttttf}
{\xxdododefinefont
{1.1}{1...
\dododododefinebodyfont ...}{\the \scratchtoks }}}
\fi \fi
\next7 #1,->\dodododefinebodyfont {tt}{17.3pt}{#1}
\doprocesscommaitem
<argument> \relax tf=Mono sa 1,
bf=MonoBold sa 1, it=MonoItalic sa 1,
sl=Mon...
\doprocesscommalist ...aitem \gobbleoneargument #1
,]\relax \global \advance
...
...
l.32 \stoptypescript
--------------------------
Has anyone figured out how to painlessly switch from omlgc (or any other font)
to cmr? I don't want to have to write an entirely new typescript for cmr! The
fact that I can switch from my private fonts to omlgc and back but not to cmr
is really fishy:-)
Best wishes
Idris
*** Strangely, fpTeX (with the same cnf values as teTeX) does not usually
complain about exceeded capacity, in contrast to teTeX. I'll test this
particular case as well shortly.
--
Dr. Idris S Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next prev parent reply other threads:[~2002-11-13 20:25 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 ` Idris S Hamid [this message]
2002-11-13 20:07 ` Idris S Hamid
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=200211131225.41164.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).