ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Culleton <john@wexfordpress.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TTF fonts and MKIV
Date: Sat, 29 Jan 2011 11:53:20 -0500	[thread overview]
Message-ID: <201101291153.20782.john@wexfordpress.com> (raw)
In-Reply-To: <871v3wsnk6.fsf@universe.krase.net>

On Friday 28 January 2011 16:52:57 Marco Pessotto wrote:
> John Culleton <john@wexfordpress.com> writes:
> > Is there a short, simple guide somewhere that shows how to use
> > TTF and OTF fonts in Context? I downloaded the new Fonts chapter
> > but it goes deep into the weeds on typescripts etc.  I am looking
> > for a method that allows me to do in Context what I can already
> > do in most other DTP programs: simply designate for use a font or
> > font family that exists in /usr/share/fonts without typescripts,
> > complex and confusing aliasing schemes or tfm files.
>
> http://wiki.contextgarden.net/Fonts_in_LuaTex
OK I used this guide and have access to one of the fonts in
/usr/share/fonts/Type1 but not the rest. Courier is in the database. 
AGaramond is not.  The wiki paper seems to state that Type1 fonts 
should be available via the database and \simplefonts. AGaramond is in
the
/usr/share/fonts/Type1
directory and is listed in the
/usr/share/fonts/Type1/fonts.dir 
file. It does not show up in the mtxrun generated data base.

set shows the following entry:
OSFONTDIR='/usr/share/fonts;/home/safe/.fonts'


Now if Type1 isn't included the font data base yet I can be cool with 
that. But in that case the wiki needs to be corrected.

-- 
John Culleton
Create Book Covers with Scribus:
http://www.booklocker.com/p/books/4055.html
Typesetting and indexing http://wexfordpress.com
book sales http://wexfordpress.net
Free  barcode: http://www.tux.org/~milgram/bookland/

___________________________________________________________________________________
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:[~2011-01-29 16:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 21:39 John Culleton
2011-01-28 21:52 ` Marco Pessotto
2011-01-29 16:53   ` John Culleton [this message]
2011-01-30 15:34     ` Curly quotes was " John Culleton
2011-01-30 15:52       ` Wolfgang Schuster
2011-01-30 16:29         ` John Culleton
2011-01-30 21:52           ` Wolfgang Schuster
2011-01-31 20:45             ` John Culleton
2011-01-31 21:35               ` Wolfgang Schuster
2011-02-01 14:02           ` Mojca Miklavec
2011-01-29  5:42 ` David Rogers
2011-01-29  8:55   ` Wolfgang Schuster
2011-01-29  9:17     ` John Haltiwanger
2011-01-29  9:46       ` Hans Hagen
2011-01-29  9:51       ` Wolfgang Schuster

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=201101291153.20782.john@wexfordpress.com \
    --to=john@wexfordpress.com \
    --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).