ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mohamed Bana <abbg770@city.ac.uk>
To: ntg-context@ntg.nl
Subject: Re: Using free Lucida, MinionPro and MyriadPro
Date: Thu, 10 Jul 2008 01:39:25 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080710T013707-598@post.gmane.org> (raw)
In-Reply-To: <E1KFdd5-0006Vc-00@ms2.city.ac.uk>

 <abbg770 <at> city.ac.uk> writes:

> 
> Hi,
> 
> Anyone tried using the MinionPro or MyriadPro thats ships with Adobe Reader 
> 8?
> 
> $ tree /opt/jdk1.6.0_06/jre/lib/fonts/
> /opt/jdk1.6.0_06/jre/lib/fonts/
> |-- LucidaBrightDemiBold.ttf
> |-- LucidaBrightDemiItalic.ttf
> |-- LucidaBrightItalic.ttf
> |-- LucidaBrightRegular.ttf
> |-- LucidaSansDemiBold.ttf
> |-- LucidaSansRegular.ttf
> |-- LucidaTypewriterBold.ttf
> |-- LucidaTypewriterRegular.ttf
> `-- fonts.dir
> 
> $ tree /opt/jdk1.6.0_06/jre/lib/oblique-fonts/
> /opt/jdk1.6.0_06/jre/lib/oblique-fonts/
> |-- LucidaSansDemiOblique.ttf
> |-- LucidaSansOblique.ttf
> |-- LucidaTypewriterBoldOblique.ttf
> |-- LucidaTypewriterOblique.ttf
> `-- fonts.dir
> 
> 0 directories, 5 files

Assuming I've got

\loadmapfile[texnansi-bandh-lucida.map]

\definefontsynonym[LucidaBright-Demi]
[texnansi-LucidaBrightDemiBold][encoding=texnansi]
\definefontsynonym[LucidaBright-DemiItalic]
[texnansi-LucidaBrightDemiItalic][encoding=texnansi]
\definefontsynonym[LucidaBright-Italic]
[texnansi-LucidaBrightItalic][encoding=texnansi]
\definefontsynonym[LucidaBright]
[texnansi-LucidaBrightRegular][encoding=texnansi]
\definefontsynonym[LucidaSans-Demi]
[texnansi-LucidaSansDemiBold][encoding=texnansi]
\definefontsynonym[LucidaSans-DemiOblique]
[texnansi-LucidaSansDemiOblique][encoding=texnansi]
\definefontsynonym[LucidaSans-Oblique]
[texnansi-LucidaSansOblique][encoding=texnansi]
\definefontsynonym[LucidaSans]
[texnansi-LucidaSansRegular][encoding=texnansi]
\definefontsynonym[LucidaSans-TypewriterBold]
[texnansi-LucidaTypewriterBold][encoding=texnansi]
\definefontsynonym[LucidaSans-TypewriterBoldOblique]
[texnansi-LucidaTypewriterBoldOblique][encoding=texnansi]
\definefontsynonym[LucidaSans-TypewriterOblique]
[texnansi-LucidaTypewriterOblique][encoding=texnansi]
\definefontsynonym[LucidaSans-Typewriter]
[texnansi-LucidaTypewriterRegular][encoding=texnansi]


How would the typscript file be defined?


Thanks



___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-07-10  1:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06 23:26 abbg770
2008-07-06 23:34 ` Diego Depaoli
2008-07-10  7:19   ` Mojca Miklavec
2008-07-10  1:39 ` Mohamed Bana [this message]
2008-07-10  6:44   ` Hans Hagen

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=loom.20080710T013707-598@post.gmane.org \
    --to=abbg770@city.ac.uk \
    --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).