ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: lucida
Date: Fri, 13 Dec 2002 18:48:43 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20021213183950.02c5db38@server-1> (raw)
In-Reply-To: <20021213125839.47c678f4.siepo@cybercomm.nl>

At 12:58 PM 12/13/2002 +0100, you wrote:

>Thanks for your input.
>
>Hans, can you confirm that there is no simple way to use an existing
>Lucida installation and that this is really necessary? And what about
>other PostScript fonts?

with existing i guess that youy mean berry names.

if someone is willing to figure out how those barry names map onto internal 
names ...

internally for instance SerifBold maps onto LucidaBright-Demi which maps 
onto <typefaceencoding>-lbd

so what's needed is something

\starttypescript [lucida] [texnansi] % or something else that suits, maybe 
just [texnansi] alone

   \definefontsynonym [texnansi-lbd] [some kind of berry name] 
[encoding=texnansi]

or

   \definefontsynonym [LucidaBright-Demi] [some berry name] [encoding=texnansi]

   ...

and add that script to say mynames.tex and then say

   \usettypescriptfile[mynames]

then things should work with

   \usetypescript [lucida] [texnansi]
   \setupbodyfont [lucida]

So, it's definitely possible, but i'm not going to make those mappings 
myself -)

Hans


-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

  reply	other threads:[~2002-12-13 17:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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               ` Hans Hagen [this message]
2002-12-11  1:07     ` lucida Matthew Huggett
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           ` Lucida Herbert Voss
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

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=5.1.0.14.1.20021213183950.02c5db38@server-1 \
    --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).