From: Ciro Soto <cirosoto@gmail.com>
Subject: Re: chancery font
Date: Sat, 2 Apr 2005 13:29:16 -0500 [thread overview]
Message-ID: <297ee2eb05040210292aaeea7e@mail.gmail.com> (raw)
In-Reply-To: <424EDBCE.8090108@boede.nl>
Idris solution didn't work. I got:
TeXFont 2.2.1 - ConTeXt / PRAGMA ADE 2000-2004
processing aborted : unknown tex root
which seems to be an installation problem...
BUT
Willi's solutions worked when I use encoding=ec (not texnansi)...
thank you
Ciro
On Apr 2, 2005 12:52 PM, Willi Egger <w.egger@boede.nl> wrote:
> Hi Ciro,
>
> AFAIK chancery has no typeface associated. So you need to do that yourself
>
> \usetypescript[chancery][texnansi]
> \definetypeface
> [myfont][cg][calligraphy][chancery][default][encoding=texnansi]
> \setupbodyfont[myfont,cg,12pt]
>
> KR
> Willi
> Ciro Soto 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
> > _______________________________________________
> > ntg-context mailing list
> > ntg-context@ntg.nl
> > http://www.ntg.nl/mailman/listinfo/ntg-context
>
--
=======================================
"All problems are at the interface. Each one of them has a solution."
from:
"The Guitar Maker, An Exploration of Wisdom, Design and Love."
A novel by C. A. Soto Aguirre. Pub. Date: Aug. 20
next prev parent reply other threads:[~2005-04-02 18:29 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
2005-04-02 17:52 ` Willi Egger
2005-04-02 18:29 ` Ciro Soto [this message]
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=297ee2eb05040210292aaeea7e@mail.gmail.com \
--to=cirosoto@gmail.com \
--cc=ciro@kavyata.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).