ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Oliver Mihatsch <oliver.mihatsch@mchp.siemens.de>
Subject: Multiple Problems with font handling
Date: Tue, 26 Feb 2002 12:06:42 +0100	[thread overview]
Message-ID: <200202261106.g1QB6h8E014771@zaire.mchp.siemens.de> (raw)

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


             reply	other threads:[~2002-02-26 11:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 11:06 Oliver Mihatsch [this message]
2002-02-27 19:51 ` Hans Hagen
2002-02-28 14:05   ` Oliver Mihatsch
2002-02-28 14:13     ` Frans Goddijn
2002-02-28 16:22       ` Oliver Mihatsch
2002-02-28 18:51         ` Henning Hraban Ramm
2002-02-28 16:38   ` Oliver Mihatsch
2002-02-28 18:54     ` Henning Hraban Ramm
2002-02-28 20:56       ` W. Egger
2002-02-28 21:54         ` Hans Hagen
2002-02-28 22:16       ` Hans Hagen
2002-03-01 15:54         ` Henning Hraban Ramm
2002-03-02 12:59           ` Hans Hagen
2002-03-01  0:19     ` Hans Hagen
2002-03-01  9:35       ` Oliver Mihatsch
2002-03-02 13:20         ` Hans Hagen
2002-03-04  9:32           ` Oliver Mihatsch
2002-03-04 10:06             ` Hans Hagen
2002-03-04 14:42               ` Oliver Mihatsch
2002-03-04 18:55                 ` Hans Hagen
2002-03-05  8:18                   ` Oliver Mihatsch

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=200202261106.g1QB6h8E014771@zaire.mchp.siemens.de \
    --to=oliver.mihatsch@mchp.siemens.de \
    /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).