From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: Lucida Bright Fonts from StarOffice
Date: 23 Aug 2004 12:28:28 +0200 [thread overview]
Message-ID: <m2brh2qhbn.fsf@levana.de> (raw)
In-Reply-To: <41292107.9000508@wxs.nl> (Hans Hagen Outside's message of "Mon, 23 Aug 2004 00:41:11 +0200")
Hello Hans and others,
>>>Are these fonts exactly the same as the ones that you buy from
>>>yandy.com?
>>I don't know.
>>
> probably not, i once did a project where graphics came from all kind
> of organizations, we ended up with (looking in the final pdf file)
> quite some different lucida clones; the file was a font mess anyway so
> nobody noticed i guess; the same may happen with times and
> helvetica
isn't font and mess a synonym?
These fonts are labelled like:
StartFontMetrics 2.0
Comment Generated by Fontographer 4.1 18.02.00 at 15:49
FontName LucidaBrightCE-Demibold
FullName LucidaBrightCE-Demibold
FamilyName LucidaBrightCE
Weight Demibold
Notice (Copyright \(c\) 1998 Bigelow & Holmes Inc. Pat. Des 289,422.)
...
[...]
> alternatively you can add to your type-loc.tex: \starttypescript
> [serif] [lucida] [ec]
> \definefontsynonym[LucidaBright] [...] [encoding=ec]
> \stoptypescript
>
> in which case you can probably use the existing lbr definition Hans
I want to avoid name clashes betwenn "lucida from staroffice" and
"official lucida". I have to do some more tests and I'll put the
instructions on the wiki.
Patrick
--
ConTeXt wiki: http://contextgarden.net
texshow-web: http://texshow.contextgarden.net
List archive: http://archive.contextgarden.net
next prev parent reply other threads:[~2004-08-23 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 13:21 skhilji
2004-08-21 15:00 ` Patrick Gundlach
2004-08-22 22:41 ` Hans Hagen Outside
2004-08-23 10:28 ` Patrick Gundlach [this message]
2004-08-23 11:04 ` Hans Hagen
2004-08-23 11:21 ` Patrick Gundlach
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=m2brh2qhbn.fsf@levana.de \
--to=patrick@gundla.ch \
--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).