From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: Lucida Bright Font Problem
Date: Mon, 31 Jul 2006 22:58:55 +0200 [thread overview]
Message-ID: <6faad9f00607311358p4d7f7b8s462249fa9f22b269@mail.gmail.com> (raw)
In-Reply-To: <44CE1D5F.5080507@wxs.nl>
On 7/31/06, Hans Hagen wrote:
> Taco Hoekwater wrote:
> > Helin Gai wrote:
> >
> >> Hi all,
> >>
> >> I'm trying to set up ConTeXt to use the Lucida Bright Font. I've
> >> already installed the font in the "LaTeX way" and it works pretty
> >> well in LaTeX. But when I use the following:
On 7/31/06, Helin Gai wrote:
> I wrote a typescriptfile according to the manual of TeXfont (attached
> below) and with the following code
OK, now I understand it. After some time of playing (before this
thread was started) I came out with some definitions like these:
% at least the basic ones which are needed for a document to compile properly
\definefontsynonym [lbmr] [hlcrm] [encoding=default]
\definefontsynonym [lbmo] [hlcrima] [encoding=default]
\definefontsynonym [lbms] [hlcry] [encoding=default]
\definefontsynonym [lbme] [hlcrv] [encoding=default]
\definefontsynonym [lbma] [hlcra] [encoding=default]
\definefontsynonym [texnansi-lbr] [hlhr8y] [encoding=texnansi]
\definefontsynonym [texnansi-lbd] [hlhb8y] [encoding=texnansi]
\definefontsynonym [texnansi-lbsl] [hlhro8y] [encoding=texnansi]
\definefontsynonym [texnansi-lbi] [hlhri8y] [encoding=texnansi]
\definefontsynonym [texnansi-lbdi] [hlhbi8y] [encoding=texnansi]
\definefontsynonym [texnansi-lbrsc] [hlhrc8y] [encoding=texnansi]
\loadmapfile[lucida.map]
\usetypescript[lucida][texnansi]
\setupbodyfont[lucida]
But then again I didn't understand how it was possible that so many
people were using lucida without any problems. (And that it was only
me who had problems installing the font - I simply took all the files
from the "LaTeX world" and forgot about using texfont, which caused me
some headaches until now anyway.)
> \usetypescript[lucida][\defaultencoding]
Hmmm ... Yesterday I figured out that lucida doesn't support EC (ie.
doens't have enough glyphs to cover Slovenian and Croatian). I guess
that only texnansi is a sensible choice. :(
(I hoped that empty slots in Hans's manuals were a consequence of
faulty ec.enc files, but now I figured out that the font has indeed
many glhyps missing.)
Mojca
next prev parent reply other threads:[~2006-07-31 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 4:37 Helin Gai
2006-07-31 9:21 ` Taco Hoekwater
2006-07-31 9:28 ` Helin Gai
2006-07-31 9:55 ` Helin Gai
2006-07-31 15:10 ` Hans Hagen
2006-07-31 15:14 ` Helin Gai
2006-07-31 16:45 ` Hans Hagen
2006-07-31 20:58 ` Mojca Miklavec [this message]
2006-07-31 21:38 ` Hans Hagen
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=6faad9f00607311358p4d7f7b8s462249fa9f22b269@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.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).