From: Idris Samawi Hamid <ishamid@colostate.edu>
Subject: Re: chancery font
Date: Sat, 02 Apr 2005 10:27:53 -0700 [thread overview]
Message-ID: <opsol74rf4u9mfh0@lamar.colostate.edu> (raw)
In-Reply-To: <297ee2eb050402085271394cc9@mail.gmail.com>
Hi Ciro,
I don't know about Garamond (does it actually come with TeX/ConTeXt?) but
there is an issue with Zapf in the latest ConTeXt; the tfm files are
corrupted. Try the following (it worked for me, thank you Hans):
remake the metrics
texmfstart texfont.pl type-tmf.dat --en=texnansi --ven=urw -col=zapfchan
refresh fndb and then try
==========================
\definetypeface [zapf] [cg] [calligraphy] [chancery]
\switchtotypeface [zapf] [12pt,cg]
\starttext
Zapf Chancery
\input tufte.tex
\stoptext
==========================
Maybe Garamond has a similar problem (assuming the font is actually
present on your system) and you can try the above with Garamond as well...
If Garamond is present, can you point me to its location, typescripts,
etc? I'd like to try it...
Best
Idris
On Sat, 2 Apr 2005 11:52:36 -0500, Ciro Soto <cirosoto@gmail.com> wrote:
> When I try the commands \usetypescript, \setupbodyfont, etc,etc
> I can't find the right combination of switches to make use of the Zapf
> Chancery or Garamond fonts.
> All other fonts work find (bookman, modern, palatino, etc).
>
> I am using Linux/fedoraCore3, texlive2004, and:
> TeXExec 5.2.4 - ConTeXt / PRAGMA ADE 1997-2005
> texexec : TeXExec 5.2.4 - ConTeXt / PRAGMA ADE 1997-2005
> texutil : TeXUtil 9.0.0 - ConTeXt / PRAGMA ADE 1992-2004
> tex : pdfeTeXk, 3.141592-1.20a-2.2 (Web2C 7.5.3)
> context : ver: 2005.01.31
> cont-en : ver: 2005.01.31 fmt: 2005.2.28 mes: english
>
> Please don't ask me to read the manuals, I've read them, but still ...
> thank you...
> Ciro
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next prev parent reply other threads:[~2005-04-02 17:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 8:37 btex-etex Jiri Polcar
2005-04-01 9:24 ` btex-etex Patrick Gundlach
2005-04-01 9:49 ` btex-etex Jiri Polcar
2005-04-02 6:37 ` Taco Hoekwater
2005-04-03 7:59 ` Jiri Polcar
2005-04-03 18:20 ` Taco Hoekwater
2005-04-03 19:28 ` h h extern
2005-04-04 7:28 ` Jiri Polcar
2005-04-04 8:22 ` Hans Hagen
2005-04-05 8:10 ` Jiri Polcar
2005-04-04 10:53 ` btex-etex Patrick Gundlach
2005-04-02 16:52 ` chancery font Ciro Soto
2005-04-02 17:27 ` Idris Samawi Hamid [this message]
2005-04-02 17:52 ` Willi Egger
2005-04-02 18:29 ` Ciro Soto
2005-04-02 19:21 ` Idris Samawi Hamid
2005-04-02 20:00 ` Ciro Soto
2005-04-02 21:22 ` Adam Lindsay
2005-04-02 23:33 ` Ciro Soto
2005-04-03 14:03 ` Rob Ermers
2005-04-03 14:57 ` Adam Lindsay
2005-04-03 16:22 ` Ciro Soto
2005-04-03 19:41 ` h h extern
2005-04-02 21:21 Idris Samawi Hamid
2005-04-02 22:33 Idris Samawi Hamid
2005-04-03 16:15 Idris Samawi Hamid
2005-04-03 16:42 ` Rob Ermers
2005-04-03 16:57 ` Paul Tremblay
2005-04-03 17:10 ` Thomas A.Schmitz
2005-04-03 18:45 Idris Samawi Hamid
2005-04-03 20:25 ` Ciro Soto
2005-04-03 21:06 ` h h extern
2005-04-03 18:46 Idris Samawi Hamid
2005-04-03 19:40 Idris Samawi Hamid
2005-04-03 19:54 ` Paul Tremblay
2005-04-03 20:22 ` Thomas A.Schmitz
2005-04-03 20:39 Idris Samawi Hamid
2005-04-16 14:13 Enrique Laya
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=opsol74rf4u9mfh0@lamar.colostate.edu \
--to=ishamid@colostate.edu \
--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).