From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: MetaPost label font size
Date: Wed, 6 Jul 2022 14:36:38 +0200 [thread overview]
Message-ID: <6939a7f6-c670-9b89-7213-e662372958aa@freedom.nl> (raw)
In-Reply-To: <a268b357-3714-fa1c-8ae6-21264ec9c646@fiee.net>
On 7/6/2022 1:36 PM, Henning Hraban Ramm via ntg-context wrote:
> Am 06.07.22 um 12:45 schrieb Hans Hagen via ntg-context:
>> On 7/6/2022 12:19 PM, fv leung via ntg-context wrote:
>>> My stupid way to get labels of different sizes:
>>>
>>> \starttext
>>>
>>> \startMPcode
>>>
>>> label("normal label", (0, 0));
>>>
>>> label("\setsmallbodyfont small label", (0, 18));
>>>
>>> label("\setbigbodyfont big label", (0, -18));
>>>
>>> \stopMPcode
>>>
>>> \stoptext
>> nothing stupid about that ... it's how i would do it
>
> Okay. So there’s really no possibility to adapt whatever defines the
> label font size except defaultfontsize inbetween? Strange.
>
> My solution so far was to split the picture and re-combine it afterwards.
well, if there would be another way you would find it strange there if
that would interfere with whatever else goes into a label text because
we support arbitrary tex ... no way to figure out what struts, line
distances, spacing, either of not adapt to current situation, delayed vs
immediate inclusion, etc ... you can't have both worlds
if course you can make some macro (or define a highlight) and use that
in the labels
Hans
-----------------------------------------------------------------
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 / 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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-07-06 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 23:00 Henning Hraban Ramm via ntg-context
2022-07-06 5:17 ` Aditya Mahajan via ntg-context
2022-07-06 9:23 ` Henning Hraban Ramm via ntg-context
2022-07-06 10:19 ` fv leung via ntg-context
2022-07-06 10:45 ` Hans Hagen via ntg-context
2022-07-06 11:36 ` Henning Hraban Ramm via ntg-context
2022-07-06 12:26 ` fv leung via ntg-context
2022-07-06 12:36 ` Hans Hagen via ntg-context [this message]
2022-07-06 13:24 ` Fabrice L via ntg-context
2022-07-06 15:21 ` Henning Hraban Ramm 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=6939a7f6-c670-9b89-7213-e662372958aa@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).