ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christoph Dreyer <reyerd@t-online.de>
Cc: ntg-context@ntg.nl
Subject: Re: fonts fonts and fonts
Date: Tue, 13 Mar 2001 00:11:34 +0100	[thread overview]
Message-ID: <01K156WYRVOU9AS7ZF@wkap.nl> (raw)

Hi!

On Mon, Mar 12, 2001, Hans Hagen wrote:

> Fonts is still one of the more complicated areas in tex. I have written a
> perl script that can do some of the tasks needed to install a 'commercial'
> font under context. 

Are you using fontinst for this? This should imho be the best way to do
it, because you can also use the font for tex/latex.

> There are several issues that need to be taken care of: 
> 
> - copying fonts the right location in the texmf-local tree

tetex keeps all font-related files in subdirs foundry/fontname, e.g.
fonts/tfm/adobe/minion.

> - generating a map file for pdftex 

This should be easy. But pdftex needs to know about the map file.  For
tetex you have to edit the script updmap and place the name of the new
map file in a variable. After that you need to call updmap, which will
create a new map file for dvips and pdftex.

> - generating font synonyms

The user should tell the script if it's a serif, sansserif or whatever.

> Now, i'm thinking of setting up a font tfm/vf/map repository but first i
> want to knwo if there is any need for that. 

A repository for what? 

> An important issue is the encoding and naming. I know that there are all
> those predefined kb font names, but i never work that way: i just use the
> original names and one encoding. So, we need to make choices as well as
> provide methods, auto map file inclusion etc. It's not that hard actually
> but i can only do this if we agree upon it. I want to get rid of the tex
> font mess -)

Imho it's better to stay with fontinst. But this certainly needs
an easy-to-use frontend. If you tell the user, after fontinst has
completed, that he can now use Minion by \setupbodyfont [minion], then
he won't see anything of the "tex font mess". So the user should use the
real name of the font, but the software the kb names.

> How many of you use fonts other that cmr and what fonts? In what encodings?
> In what combinations?  

I have used the standard pdf fonts, Lucidabright, Utopia, Charter and
the Microsoft Core Fonts. All in texnansi encoding, because I still
don't understand how this encoding stuff works... :-(  But I never
had problems with this. Except that some symbols are taken from
the Computer Modern Math fonts.

Hope this helps.

Christoph


             reply	other threads:[~2001-03-12 23:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-12 23:11 Christoph Dreyer [this message]
2001-03-13  9:25 ` Hans Hagen
     [not found] <C21706811338D411A0130090273D20B291AD48@msgmarbio02.bio.dfo .ca>
2001-03-13 14:54 ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2001-03-13 13:38 White, George
2001-03-13  9:05 siep.kroonenberg
     [not found] <pragma@wxs.nl>
2001-03-12 16:50 ` Hans Hagen
2001-03-12 17:07   ` Frans Goddijn
2001-03-12 23:11   ` Christoph Dreyer
2001-03-13  9:33     ` S2P development
2001-03-13 10:12       ` Han The Thanh
2001-03-13 10:35       ` Hans Hagen
2001-03-14 21:32       ` H. Ramm
2001-03-13  7:12   ` Steve Lumos
2001-03-13  9:13     ` Hans Hagen
2001-03-14  0:29     ` Uwe Koloska
2001-03-13 14:35   ` Ed L Cashin
2001-03-14  0:18   ` Uwe Koloska
2001-03-15 21:55   ` H. Ramm

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=01K156WYRVOU9AS7ZF@wkap.nl \
    --to=reyerd@t-online.de \
    --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).