ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Bruce D'Arcus" <darcusb@muohio.edu>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: ConTeXt and expert fonts
Date: Thu, 8 Aug 2002 10:19:26 -0400 (EDT)	[thread overview]
Message-ID: <10139745.1028816366614.JavaMail.darcusb@muohio.edu> (raw)

Jens-Uwe Morawski wrote:

>IMO, the main problem is that there is no standard encoding
>for those glyphs. The most common font encodings texnansi and
>ec do not include oldstyle figures and other interesting expert
>glyphs.

What I did to get it working with LaTeX was to modify the encoding 
files I used to create the tfm and vf files to map what I need 
(smallcaps, superiors, monospaced figures, etc.) into the standard T1 
encoding.  The issue isn't the fonts (since I have them working in 
LaTeX); it's how to tell ConTeXt how to use them.  What I want, in 
essence, is to define things like SerifFootnote (serif, because it 
shouldn't be specific to Hoefler Text), SerifMonoLining, SerifMonoOSF, 
etc., and then to tell ConTeXt: "use the footnote font for footnotes, 
the monoOSF fonts for tables, etc."

I'll send a simple sample file later, per Hans' suggestion...

Bruce


             reply	other threads:[~2002-08-08 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 14:19 Bruce D'Arcus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-15 22:02 Bruce D'Arcus
2002-08-14 15:50 Bruce D'Arcus
2002-08-15 16:09 ` Hans Hagen
2002-08-10 15:02 Bruce D'Arcus
2002-08-09  2:09 Bruce D'Arcus
2002-08-09  9:17 ` Jens-Uwe Morawski
     [not found] <3978810.1028738892491.JavaMail.cpadmin@nassol01.mcs.muohio .edu>
2002-08-08  7:10 ` Hans Hagen
2002-08-07 16:48 Bruce D'Arcus
2002-08-07 18:02 ` Frans Goddijn
2002-08-08  9:01 ` Jens-Uwe Morawski

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=10139745.1028816366614.JavaMail.darcusb@muohio.edu \
    --to=darcusb@muohio.edu \
    --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).