From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Lucida Bright Font Problem
Date: Mon, 31 Jul 2006 23:38:15 +0200 [thread overview]
Message-ID: <44CE7847.5000400@wxs.nl> (raw)
In-Reply-To: <6faad9f00607311358p4d7f7b8s462249fa9f22b269@mail.gmail.com>
Mojca Miklavec wrote:
> 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.)
>
when i started using lucida (many years ago) they came with tfm files
(texnansi) abut nowadays i just generate the metrics with texfont
because yandy went away tug now sells the fonts, and as a result new
metrics for latex were made; i'm not sure with what (afm) files the
fonts ship nowadays but i'm not going to change/adapt my local setup
(too tricky) to different lucida spacing and metrics; the font metrics
zip has them
>
>> \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.)
>
my impression is that when ec was made nobody cared much about eastern european languages; for some reason the hardly (or once per doc) used copyright and registere symbols were considered to be of more importance, alas ...
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-07-31 21:38 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
2006-07-31 21:38 ` Hans Hagen [this message]
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=44CE7847.5000400@wxs.nl \
--to=pragma@wxs.nl \
--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).