ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Yue Wang <yuleopen@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Hans Hagen <pragma@wxs.nl>
Subject: Re: mkii bug in lucida, again.
Date: Tue, 21 Dec 2010 11:46:30 +0100	[thread overview]
Message-ID: <AANLkTimN3=GXwt7kinj7QkwUDYe947TRrK-6mvoy_opG@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimc0g8Wogxmc_kU=278e7ibNATTpOHSbQhY9ttN@mail.gmail.com>

On Sun, Dec 19, 2010 at 18:34, Yue Wang wrote:
> BTW, there is also something strange with lucida support in context recently.
> if I use
> \usetypescriptfile[type-buy]
> \usetypescript[lucida][texnansi]
> \setupbodyfont[lucida,14pt]

What does recently mean? (It has changed in early 2010.)

I'm using ConTeXt version 2010.12.18 21:03 and it works fine, but I
use files provided by TUG (you get tfm files for free on CTAN).

See the first three lines in
    http://wiki.contextgarden.net/Lucida

You don't need to use type-buy. The typescripts are in the core now. I
asked Hans to change the typescripts, since one had to create own tfm
files otherwise. Not it is possible to use the ones provided by TUG.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-12-21 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 17:26 Yue Wang
2010-12-19 17:34 ` Yue Wang
2010-12-21 10:46   ` Mojca Miklavec [this message]
2010-12-21 10:47     ` Mojca Miklavec
2010-12-31 22:00 ` Yue Wang

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='AANLkTimN3=GXwt7kinj7QkwUDYe947TRrK-6mvoy_opG@mail.gmail.com' \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    --cc=yuleopen@gmail.com \
    /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).