ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: NTG-ConTeXt <ntg-context@ntg.nl>
Subject: Re: Unicodefonts (Type 1)
Date: Thu, 09 Aug 2001 10:49:10 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20010809104156.02a5cde0@server-1> (raw)
In-Reply-To: <3B71753B.7000307@net-b.de>

At 07:22 PM 8/8/2001 +0200, Tobias Burnus wrote:

>I found this Type-1 Unicode font
>    http://bibliofile.mc.duke.edu/gww/fonts/Unicode.html
>which I would like to use with \ConTeXt.
>
>It consists of:
>Caslon (serif font): roman, oblique, bold, black, small-caps (but no 
>bold-oblique)
>Monospace (~courier): roman, oblique, bold [and no-Type-1 bold-oblique]
>Cupola (~~~Informal): Roman, italic, bold, bold-italic, small caps
>Caliban (~helvetica): Roman(?)
>
>How can I use it best? I'd like to use it as complete replacement for CM 
>for some documents, since has a lot of nice characterts.

A type one font needs to be split into chunks [this is how for instance 
chinese is supported] while a truetype can be used as a whole.

You need to make tfm files for each chunk, as well as enc files [lei wang 
is an expert on this, he also made some scripts]. If you can sort this out 
we can see if we can make this process easy since there are more unicode 
fonts around.

there are two ways to proceed:

(1) create standard (say texnansi,ec) subsets,
(2) use uchar mapping, which means something like:

Eumlaut -> uchar{1}{234}

but then we may loose kerning and so,

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


      reply	other threads:[~2001-08-09  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08 17:22 Tobias Burnus
2001-08-09  8:49 ` Hans Hagen [this message]

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.20010809104156.02a5cde0@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).