From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/7025
Path: main.gmane.org!not-for-mail
From: Oliver Mihatsch <oliver.mihatsch@mchp.siemens.de>
Newsgroups: gmane.comp.tex.context
Subject: Multiple Problems with font handling
Date: Tue, 26 Feb 2002 12:06:42 +0100
Sender: owner-ntg-context@let.uu.nl
Message-ID: <200202261106.g1QB6h8E014771@zaire.mchp.siemens.de>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: main.gmane.org 1035397521 15846 80.91.224.250 (23 Oct 2002 18:25:21 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 18:25:21 +0000 (UTC)
Original-To: ntg-context@ntg.nl
Xref: main.gmane.org gmane.comp.tex.context:7025
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:7025

I just installed the latest context beta and ran into multiple font problems 
with things that used to work before (I think so, at least:-)).

My setting:
   This is pdfeTeX, Version 3.14159-1.00a-pretest-20010806-2.1 (Web2C 7.3.3.1)
   ConTeXt  ver: 2001.12.20  fmt: 2002.2.22  int: english  mes: english

The problems:

1.  Hanging punctuation does not work.
     It simply does not "hang".
    Minimal example:

     \setupoutput[pdftex]
      \usetypescript[serif][hanging][pure]
      \setupalign [hanging]
   \definetypeface[modern][rm][serif][computer-modern][default][handling=pure]
      \showframe
      \starttext
         \modern\input tufte
      \stoptext

2.  \usetypescript[ptm]  does not reslove the fontname.
     The following minimal example

    \setupoutput[pdftex]
      \usetypescript[ptm]
      \setupbodyfont[ptm]
      \starttext
        \input tufte
      \stoptext

     makes kpathsea believe that it needs to create the tfm file  
     Times-Roman.tfm, which fails for obvious reasons.
      .....
      kpathsea: Running mktextfm  Times-Roman
      .... 
      ! I can't find file `Times-Roman.mf'.
      ...

3. Usage of  \usetypescriptfile [type-buy] results in an "Undefined control 
sequence."

   ! Undefined control sequence.
<argument> \processcommalist [\typescriptencoding 
                                                  -itc-officina]

     It seems that the multiply occuring  \typescriptencoding needs to be 
replaced by  \typescripttwo or \typescriptthree depending on the context.

I do not know whether this is supposed to work.
Are these bugs or is it simply wrong usage?

Greetings
Oliver Mihatsch