ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \definefont problem with latest beta (mkiv)
Date: Wed, 12 Nov 2008 12:20:00 +0100	[thread overview]
Message-ID: <491ABBE0.20403@wxs.nl> (raw)
In-Reply-To: <491AB7B6.6070507@gmx.net>

Peter Rolf wrote:
> Taco Hoekwater schrieb:
>> Peter Rolf wrote:
>>> I followed that one. But my problem is more the *wrong strut height*,
>>> e.g. using a \totalstrut value of 12pt with a 8pt font. The strut height
>>> is simply not adapted to the actual font size anymore (even if I use
>>> \setstrut).
>> I can understand why you think this is a different problem, but both
>> struts and interline spaces depend on the value of "1ex", which has
>> changed in an incompatible way. Perhaps you should post a complete
>> minimal example.
>>
> But (unless the font data is really bad) we are talking about slight
> differences. And you can't call a 12.6pt strut for a 8pt font a slight
> change. :)
> 
> I will (try to) make a minimal example...

\showstruts
     \start
         \tf  \setstrut tf:\strut
         \tfa \setstrut tfa:\strut
         \tfb \setstrut tfb:\strut
         \tfc \setstrut tfc:\strut
         \tfd \setstrut tfd:\strut
     \stop
     \start
         \small
         \tf  \setstrut tf:\strut
         \tfa \setstrut tfa:\strut
         \tfb \setstrut tfb:\strut
         \tfc \setstrut tfc:\strut
         \tfd \setstrut tfd:\strut
     \stop

looks ok to me (at least on my machine)



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-11-12 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 13:37 Peter Rolf
2008-11-11 13:48 ` Wolfgang Schuster
2008-11-11 14:03   ` Peter Rolf
2008-11-11 16:40   ` Peter Rolf
2008-11-11 16:51     ` Wolfgang Schuster
2008-11-11 18:47       ` Peter Rolf
2008-11-12  9:47         ` Taco Hoekwater
2008-11-12 11:02           ` Peter Rolf
2008-11-12 11:20             ` Hans Hagen [this message]
2008-11-12 12:11               ` Peter Rolf
2008-11-13 15:22             ` Peter Rolf
2008-11-13 15:50               ` Wolfgang Schuster
2008-11-13 16:26                 ` Peter Rolf
2008-11-13 21:30               ` Hans Hagen
2008-11-14 13:54                 ` Peter Rolf

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=491ABBE0.20403@wxs.nl \
    --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).