From: Hans van der Meer via ntg-context <ntg-context@ntg.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Cc: Hans van der Meer <havdmeer@ziggo.nl>
Subject: Re: [NTG-context] font style and size interaction
Date: Tue, 30 May 2023 12:24:46 +0200 [thread overview]
Message-ID: <36021F03-2DEF-45A6-8B1C-C09E92926AA6@ziggo.nl> (raw)
In-Reply-To: <6715df8a-18a4-1ef3-cfe2-dbde42548036@freedom.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2007 bytes --]
Hans,
I see this as a no with respect to changing the behaviour of \small and friends. Which I can well understand: changes on this level may trigger a lot of unwanted problems.
But now I can program around it with a clear conscience;-)
dr. Hans van der Meer
> On 30 May 2023, at 11:33, Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:
>
> On 5/30/2023 10:18 AM, Hans van der Meer via ntg-context wrote:
>> There is -- in my perception -- a problem with the interaction between font style and font size changes.
>> The order of calling for example \it\small matters because \small\it leads to a different result.
>> I would however reason that size and style changes should be in orthogonal spaces, that is: the one should have no effect on the other.
>> Cause of this behaviour seems the \tf call included in small. See the accompanying example.
>> I can try to program around this, but I would prefer not to. Is there a possibility that this behaviour will be changed to \it\small and \small\it giving the same result?
> \small does a (massive) bodyfont switch and therefore you end up with regular tf
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 2765 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-05-30 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 8:18 Hans van der Meer via ntg-context
2023-05-30 9:33 ` Hans Hagen via ntg-context
2023-05-30 10:24 ` Hans van der Meer via ntg-context [this message]
2023-05-30 12:14 ` Hans Hagen via ntg-context
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=36021F03-2DEF-45A6-8B1C-C09E92926AA6@ziggo.nl \
--to=ntg-context@ntg.nl \
--cc=havdmeer@ziggo.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).