From: Herbert Voss <Herbert.Voss@FU-Berlin.DE>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Lucida
Date: Tue, 09 Nov 2010 15:12:03 +0100 [thread overview]
Message-ID: <4CD956B3.8010906@FU-Berlin.DE> (raw)
In-Reply-To: <AANLkTin2_yq9pLqFLDc2q92_2xUJxViDAOP6mwn=jiET@mail.gmail.com>
Am 09.11.2010 14:08, schrieb Mojca Miklavec:
> I have no idea what happens if Type1 version of fonts is not the same
> as described in afm files, but if you don't have all the necessary
> Type1 files that are absolutely needed for Math, it probably won't
> work anyway. I don't know enough of Lucida's history to provide more
> insight. What pfb files exactly do you have on your system?
>
> I would try to completely remove texmf-cache and then regenerate the
> filename database again (mtxrun --generate).
This works:
\starttypescript[lucida]
\definetypeface[\typescriptone][rm][serif]
[lucida][default][features=default]
\definetypeface[\typescriptone][ss][sans]
[lucida][default][features=default]
\definetypeface[\typescriptone][tt][mono]
[lucida][default][features=none]
\definetypeface[\typescriptone][cal][cal]
[lucida][default][features=default]
\definetypeface[\typescriptone][hw][handwriting][lucida][default][features=default]
\definetypeface[\typescriptone][mm][math] [modern][default]
\stoptypescript
\setupbodyfont[lucida,11pt,rm]
%\input LoadLucida
\starttext
foo Lucida Bright \ss Lucida Sans Serif \tt Lucida Mono
\hw Handwriting
\cal Calligraphic
\stoptext
Is it a problem with the definitions for otf in type-otf.mkiv,
but using type1 instead of otf?
Herbert
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-11-09 14:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 12:33 Lucida Herbert Voss
2010-11-08 13:42 ` Lucida Mojca Miklavec
2010-11-08 15:58 ` Lucida Herbert Voss
2010-11-08 20:49 ` Lucida Hans Hagen
2010-11-08 21:12 ` Lucida Herbert Voss
2010-11-09 7:45 ` Lucida Mojca Miklavec
2010-11-09 9:10 ` Lucida Herbert Voss
2010-11-09 9:47 ` Lucida Hans Hagen
2010-11-09 12:31 ` Lucida Herbert Voss
2010-11-09 13:08 ` Lucida Mojca Miklavec
2010-11-09 13:28 ` Lucida Herbert Voss
2010-11-09 14:12 ` Herbert Voss [this message]
2010-11-09 15:45 ` Lucida Mojca Miklavec
2010-11-09 16:42 ` Lucida Hans Hagen
2010-11-09 9:24 ` Lucida Hans van der Meer
-- strict thread matches above, loose matches on Subject: below --
2002-12-10 14:46 lucida Siep
2002-12-10 15:21 ` lucida Matthew Huggett
2002-12-10 15:46 ` lucida Siep
2002-12-10 16:03 ` lucida Daniel Graham
2002-12-11 1:08 ` lucida Matthew Huggett
2002-12-11 9:04 ` lucida Siep
2002-12-11 17:50 ` lucida Larry Stamm
2002-12-13 11:58 ` lucida Siep
2002-12-13 17:48 ` lucida Hans Hagen
2002-12-11 1:07 ` lucida Matthew Huggett
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=4CD956B3.8010906@FU-Berlin.DE \
--to=herbert.voss@fu-berlin.de \
--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).