From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: rscale with auto value
Date: Thu, 27 Sep 2018 11:25:51 +0200 [thread overview]
Message-ID: <e58af670-6a97-52b7-714b-5db73465dfa5@gmx.es> (raw)
In-Reply-To: <alpine.OSX.2.20.1809261130330.71942@nqv-znpobbx>
On 9/26/18 5:31 PM, Aditya Mahajan wrote:
> On Wed, 26 Sep 2018, Pablo Rodriguez wrote:
>> [...]
>> Would it be possible that rscale could have the auto value?
>
> See my answer to a similar question on TeX.SE
>
> https://tex.stackexchange.com/a/450658/323
Hi Aditya,
many thanks for your detailed explanation at TeX.SE.
It seems that \showfontstrip is the way to go. It won’t be easy to
explain to newcomers, but I have to try.
I agree with Thomas that Porson shouldn’t be scaled. But this is mainly
because the font is totally different from other typefaces with Latin
glyphs (such as Palatino or Times).
Hans is right that glyph boldness is to be taken in consideration when
scaling a typeface. In my personal case, what bothers me most is the
different x-height between typefaces. Glyph boldness when scaling is
changed, but I’d say that it isn’t as obvious as different x-height.
rscale=auto would only be a value for an option, not even the default.
Of course, it wouldn’t be mandatory. This would not prevent from scaling
manually (or not scaling at all). But it would make things much easier
when trying to calculate the same x-heights.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2018-09-27 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 15:06 Pablo Rodriguez
2018-09-26 15:31 ` Aditya Mahajan
2018-09-27 9:25 ` Pablo Rodriguez [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=e58af670-6a97-52b7-714b-5db73465dfa5@gmx.es \
--to=oinos@gmx.es \
--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).