ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Oliver Mihatsch <oliver.mihatsch@mchp.siemens.de>
Subject: Re: Multiple Problems with font handling
Date: Thu, 28 Feb 2002 17:38:18 +0100	[thread overview]
Message-ID: <200202281638.g1SGcI8E008370@zaire.mchp.siemens.de> (raw)
In-Reply-To: <5.1.0.14.1.20020227204629.02b2ca48@server-1>

On Wednesday 27 February 2002 20:51, you wrote:
> can you download the beta version (some time ago i changed some things so
> that 'preloaded' font defs are okay now).

After downloading the newest beta (the real one :-) ) the situation changed 
quite a lot. However, there are some problems remaining ....
(ConTeXt  ver: 2002.2.25  fmt: 2002.2.28  int: english  mes: english)

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

The minimal example I provided works perfectly now. However, when using \tfa 
the hanging puntuation breakes. E.g.

     \setupoutput[pdftex]
      \usetypescript[serif][hanging][pure]
      \setupalign [hanging]
   \definetypeface[modern][rm][serif][computer-modern][default][handling=pure]
      \showframe
      \starttext
         \modern
         \input tufte  \par             % ok hanging punctuation works
         {\tfa\input tufte \par}        % no hanging punctuation :-(
         {\switchtobodyfont[big]\input tufte \par} % ok again
         {\tfx\input tufte \par}                            % ok
         {\switchtobodyfont[small]\input tufte \par} % ok
      \stoptext

Interestingly,  \tfx does not switch off the hanging puntuation.
Also, \switchtobodyfont[...] seems to be  ok.
(Btw. Is it normal that neither \tfa nor \tfx adapt the interline spaces?)

> >2.  \usetypescript[ptm]  does not reslove the fontname.
> >      The following minimal example
> >
> >     \setupoutput[pdftex]
> >       \usetypescript[ptm]
> >       \setupbodyfont[ptm]
> >       \starttext
> >         \input tufte
> >       \stoptext
>
> also works here, so before i look into it, can you try the beta?
>

This problem persists.

Greetings,
Oliver


  parent reply	other threads:[~2002-02-28 16:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 11:06 Oliver Mihatsch
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 [this message]
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=200202281638.g1SGcI8E008370@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).