From: David Arnold <darnold@northcoast.com>
Subject: Lucida, some progress
Date: Sat, 02 Aug 2003 23:04:47 -0700 [thread overview]
Message-ID: <3.0.5.32.20030802230447.00b3c4a0@mail.northcoast.com> (raw)
All,
I am running Miktex on Windows. I took my YandY lucida fonts (pfb and afm
files) and put them in a temporary directory, f:\temp\fonts\lucida on my
system.
I then ran:
texfont --fontroot=f:\localtexmf --sourcepath=f:\temp\fonts\lucida
--vendor=yandy --collection=lucida --makepath --install
I then added the following line to pdftex.cfg.
map +texnansi-yandy-lucida.map
The following file now compiles. However, feelings are bittersweet. I've
got something working, but I have no idea why. Nor am I assured that I've
found the proper solution. More difficulties could loom on the horizon.
Have I done this the correct way?
\setupoutput[pdf]
\usetypescript[berry][texnansi]
\usetypescript[lbr]
\setupbodyfont[lbr]
\starttext
Hello. This is a {\em test} of what the {\it Lucida} {\sl Fonts} can
do at 6 {\sc am}.
\placeformula
\startformula
f(x)=\int_0^x f(t)\, dt
\stopformula
\stoptext
reply other threads:[~2003-08-03 6:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3.0.5.32.20030802230447.00b3c4a0@mail.northcoast.com \
--to=darnold@northcoast.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).