From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	HTML_MESSAGE,MAILING_LIST_MULTI,NICE_REPLY_A,T_SCC_BODY_TEXT_LINE,
	URIBL_SBL_A autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 18261 invoked from network); 27 May 2023 05:57:30 -0000
Received: from zapf.ntg.nl (5.39.185.232)
  by inbox.vuxu.org with ESMTPUTF8; 27 May 2023 05:57:30 -0000
Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 453571C38A2;
	Sat, 27 May 2023 07:57:06 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl
Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id V28TGu5H5t1N; Sat, 27 May 2023 07:57:04 +0200 (CEST)
Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 2F9071C3218;
	Sat, 27 May 2023 07:57:04 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 7BC9C1C3218
 for <ntg-context@ntg.nl>; Sat, 27 May 2023 07:57:02 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl
Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id E196IG8KNnQP for <ntg-context@ntg.nl>;
 Sat, 27 May 2023 07:57:01 +0200 (CEST)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.208.43;
 helo=mail-ed1-f43.google.com; envelope-from=wolfgang.schuster.lists@gmail.com;
 receiver=<UNKNOWN> 
Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com
 [209.85.208.43])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 917DC1C3166
 for <ntg-context@ntg.nl>; Sat, 27 May 2023 07:57:01 +0200 (CEST)
Received: by mail-ed1-f43.google.com with SMTP id
 4fb4d7f45d1cf-51456392cbbso2785844a12.0
 for <ntg-context@ntg.nl>; Fri, 26 May 2023 22:57:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1685167021; x=1687759021;
 h=content-language:in-reply-to:mime-version:user-agent:date
 :message-id:references:to:subject:from:from:to:cc:subject:date
 :message-id:reply-to;
 bh=8TD7nHhiGvCwHCXa5LMAP4TQz2BGmL1p3gP5cyKOI9U=;
 b=Z37LfxB37mHv7tVQHeSLjT/JYKvEs/Eot4n41LtFG4G6Wo2hD5E6QWzKuxecAlqBkK
 cUNEgE5RPHmbzd78Vxqbn3uHFgkTgYVgL06T1hg48peMm1PfMXeFVzwxHCi9SsQnzS8p
 uAk9JbgQHX1xHKB/aR6VBb4Sqq2V1sf5NX1nWY4yDrGLSnEvxalUw5OydbMAYn0ZLtiH
 gKQ47g/luzrzGMRZn8E3GPO1wsHVQJMIWfJ6ZuT0eag91ZXsVvlc5JaH8n3LiPqpj5NX
 tnpLwLRcuCEHxbCC+LjfjW2+2qs3+t3X6mEa0fZHc+aYVGazwda+baHfwf4DVaILODzF
 66gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1685167021; x=1687759021;
 h=content-language:in-reply-to:mime-version:user-agent:date
 :message-id:references:to:subject:from:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=8TD7nHhiGvCwHCXa5LMAP4TQz2BGmL1p3gP5cyKOI9U=;
 b=bDoaHzJwkOBI6oGO6tLeWBDVtqVThkhpPrvrTYq0b8foa3R6FLOKjh/Vh7rpUS9sdI
 Zxfugs+eBuV207MuMXlI0SptWCP/P6dwLsH1qoD5AmtPwCuzCVbjelyv8Muo3Wctss23
 FJDsNZ2q/9oUSFxHeqg1RCKn7fA04k9LLv6YMfgBRt/9celGl21Vk0NH37Uz3VPDvxIh
 KV+fVxDMhQE07KnBQ1auU28Es0JGcWW02lstrnWm6os/6C0v9iOJ5Pft415V6GAXpBMZ
 17FLGDuQlgJSLdPfJ44tYE/vRu0e5y39lrdJSHKkxhNFxs67b+NP/jCm9MgILjMGHasf
 6rXw==
X-Gm-Message-State: AC+VfDww1+XnjTW7qoVgknd+uLS1CLw04kfcea9U/nBM6SUJqeINYfp7
 yeLYkq4R10p4GTIDkMlBCH2u9mAltfs=
X-Google-Smtp-Source: ACHHUZ6EGNqaEyYf0ve4Sja+/YaP3hV/iz7W7HA2dza7HLpBlUJnlBdJpZ6A0PwXlfugR4lRBJTcQA==
X-Received: by 2002:a17:907:628a:b0:969:9c0c:4c97 with SMTP id
 nd10-20020a170907628a00b009699c0c4c97mr1040351ejc.1.1685167021069; 
 Fri, 26 May 2023 22:57:01 -0700 (PDT)
Received: from ?IPv6:2a02:810d:a8bf:fe08::29cd? ([2a02:810d:a8bf:fe08::29cd])
 by smtp.gmail.com with ESMTPSA id
 z4-20020aa7d404000000b0050bc9ffed66sm635713edq.53.2023.05.26.22.56.59
 for <ntg-context@ntg.nl>
 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
 Fri, 26 May 2023 22:57:00 -0700 (PDT)
To: Hans van der Meer via ntg-context <ntg-context@ntg.nl>
References: <2B06211F-2AC1-43D2-A596-34CAAF4E11DC@ziggo.nl>
Message-ID: <cda5c975-d97b-7b24-4111-8a9dbe6d914e@gmail.com>
Date: Sat, 27 May 2023 07:56:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 PostboxApp/7.0.60
MIME-Version: 1.0
In-Reply-To: <2B06211F-2AC1-43D2-A596-34CAAF4E11DC@ziggo.nl>
Content-Language: en-US
Subject: Re: [NTG-context] font size and style
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.38
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Content-Type: multipart/mixed; boundary="===============6102604335669547866=="
Errors-To: ntg-context-bounces@ntg.nl
Sender: "ntg-context" <ntg-context-bounces@ntg.nl>

This is a multi-part message in MIME format.
--===============6102604335669547866==
Content-Type: multipart/alternative;
 boundary="------------C4152C13D565F0027889C1C8"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------C4152C13D565F0027889C1C8
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hans van der Meer via ntg-context schrieb am 26.05.2023 um 21:38:
> 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?
>

\tf is the switch for the normal upright style and when you have \bf\tfa 
the first font switch is just replaced by the second switch.

To get a larger text in bold style you can use \bfa.

\starttext

text {\tfa\bf text} text

text {\bfa text} text

\stoptext

Wolfgang


--------------C4152C13D565F0027889C1C8
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html theme="default-light" iconset="color"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

</head><body style="color: rgb(0, 0, 0);" text="#000000"><span>Hans van 
der Meer via ntg-context 
schrieb am 26.05.2023 um 21:38:</span><br>

<blockquote type="cite" 
cite="mid:2B06211F-2AC1-43D2-A596-34CAAF4E11DC@ziggo.nl" 
style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: 
after-white-space;"><meta http-equiv="content-type" content="text/html; 
charset=utf-8">
  <div>Calling "\bf\tfa  TEXT" for example leaves the TEXT not in bold 
because \tfa does not respect the current style. As does \small, etc.</div>
  <div>Shown by looking at the meaning of for example \small:</div>
  <div><div class="page" title="Page 3"><div class="layoutArea"><div 
class="column"><p><font face="HelveticaNeue">\small=protected 
macro:\triggergroupedcommand {\setsmallbodyfont \tf }</font><br></p><p><font
 face="HelveticaNeue">and</font></p><div class="page" title="Page 3"><div
 class="layoutArea"><div class="column"><p><font face="HelveticaNeue">\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<br></font></p></div></div></div><p>Thus
 in contrast \tx and \txx do respect the current style setting.</p><p>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 <span style="font-family: 
HelveticaNeue;">\currentxfontsize is there an analogue for the style?</span></p></div></div></div></div></blockquote>

<br>

\tf is the switch for the normal upright style and when you have \bf\tfa
 the first font switch is just replaced by the second switch.<br>

<br>

To get a larger text in bold style you can use \bfa.<br>

<br>

\starttext<br>

<br>

text {\tfa\bf text} text<br>

<br>

text {\bfa text} text<br>

<br>

\stoptext<br>

<br>

Wolfgang<br>

<br>



</body></html>

--------------C4152C13D565F0027889C1C8--

--===============6102604335669547866==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============6102604335669547866==--