ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: [NTG-context] font size and style
Date: Fri, 26 May 2023 21:38:08 +0200	[thread overview]
Message-ID: <2B06211F-2AC1-43D2-A596-34CAAF4E11DC@ziggo.nl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]

Calling "\bf\tfa  TEXT" for example leaves the TEXT not in bold because \tfa does not respect the current style. As does \small, etc.
Shown by looking at the meaning of for example \small:
\small=protected macro:\triggergroupedcommand {\setsmallbodyfont \tf }

and

\tx=protected macro:\currentxfontsize \plusone \ifmmode \scriptstyle \orelse \ifconditional \c_font_inherit_scale \font_scale_inherit_x \else \font_scale_defined_x \fi \al­ ways\let \tx \txx

Thus in contrast \tx and \txx do respect the current style setting.

My question: It seems most convenient if I could retrieve the current style and reset that after a size command. I rather would refrain from tinkering with those. Since there is a \currentxfontsize is there an analogue for the style?

dr. Hans van der Meer

[-- Attachment #1.2: Type: text/html, Size: 1412 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
___________________________________________________________________________________

             reply	other threads:[~2023-05-26 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 19:38 Hans van der Meer via ntg-context [this message]
2023-05-27  5:56 ` Wolfgang Schuster 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=2B06211F-2AC1-43D2-A596-34CAAF4E11DC@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).