ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: relative scaling for fonts
Date: Thu, 16 Nov 2006 11:54:50 +0100	[thread overview]
Message-ID: <455C437A.8010700@wxs.nl> (raw)
In-Reply-To: <455C27A5.6090205@web.de>

Pablo Rodríguez wrote:
> Hans Hagen wrote:
>   
>> Pablo Rodríguez wrote:
>>     
>>> After using \showfontstrip to get fonts with the same x-height by
>>> calculating the rscale factor, I guess it would be very useful (at least
>>> for me) to have an option that calculates relative scaling automatically
>>> to match both x-heights.
>>>
>>> I think it would be a useful option for rscale.
>>>   
>>>       
>> hm, it's not that hard to do, but then the question is: what is the reference font; also, my experience is that an automated scaling in most cases looks as ugly as no scaling; it's a visual thing; the xheight is a factor but the 'boldness' too 
>>     
>
> The reference font would be the roman font and the automated scaling
> with the same x-height might be wrong in some cases, but it is a useful
> starting point to start learning for newcomers (like me) how to set the
> proper visual scaling factor.
>
> My most common scenario for font scaling is not roman with sansserif or
> typewritter, but roman Latin with roman Greek characters and setting the
> same x-height for both. And I thought there were fine with the same
> x-height for both.
>
> My typographical ability wouldn't let my set other relative scaling
> factor other than 1 or the same x-height for both fonts.
>
>   
Hm. Just typeset fontstrips, scale the doc up/down on the screen and 
find the best visual match. You need to do that only once for a given 
combination of fonts. In most cases i use lm for monospaced and palatino 
for math when combined with other fonts, and my experience is that one 
really need to typeset some text (with e.g. inline verbatim) in order to 
find out what value is best.

The problem is that in that case, we would end up with 4 line 
definitions replaced by 4 line definitions; ok, when we have luatex, we 
can think of some aux macros (\rscaled{"fontname"}) because then fully 
expandable solutions are possible.

Adam Lindsay made/had plans for predefined typefaces and actually that 
is then the best way to go: predefine interesting combinations of fonts 
with optimized values for relative scaling and ht/dp ratios.

Hans

-----------------------------------------------------------------
                                          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
-----------------------------------------------------------------

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

      parent reply	other threads:[~2006-11-16 10:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-12 21:17 Pablo Rodríguez
2006-11-13 20:06 ` Henning Hraban Ramm
2006-11-13 23:38   ` Pablo Rodríguez
2006-11-14 11:15 ` Hans Hagen
2006-11-14 19:34   ` Pablo Rodríguez
2006-11-15  9:39     ` Hans Hagen
2006-11-15 13:53   ` Pablo Rodríguez
2006-11-15 14:12     ` Hans Hagen
2006-11-16  8:56       ` Pablo Rodríguez
2006-11-16  9:05         ` Thomas A. Schmitz
2006-11-16 10:54         ` Hans Hagen [this message]

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=455C437A.8010700@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).