From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: new upload
Date: Wed, 16 Aug 2023 10:07:15 +0200 [thread overview]
Message-ID: <fee41dda-9145-4651-20a8-334684707ff1@freedom.nl> (raw)
In-Reply-To: <eaad62f9-75e4-57c3-8c66-4a6a4201d9a0@gmx.es>
On 8/15/2023 10:54 PM, Pablo Rodriguez wrote:
> On 8/15/23 22:16, Hans Hagen via ntg-context wrote:
>> On 8/15/2023 9:27 PM, Pablo Rodriguez wrote:
>>> [...]
>>> I wonder whether we could have (current) frame width and height as unit.
>> we can have
>>
>> fw fh fo lw (width height offset linewidth)
>>
>> but keep in mind that only properties that are set up have a meaningful
>> value (so with autoheight it is zero)
>
> So 1fw is equal to 2fo + 1lw, isn’t it? (I mean, frame width is left and
> right offset [given that all frames have the same length] plus line width.)
fw is more like width-2offset-2linewidth
> Sorry, this is to be sure I’m getting this right.
we can also have (available)
lh lineheight
sh strutheight
sd strutdepth
and maybe (pick up from font or have extra font dimens)
fa font ascender
fd font descender
fc font capheight
and the css (easy)
ch width of zero
and then a kind of periodic table of units
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 / 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-08-16 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 17:08 [NTG-context] " Hans Hagen
2023-08-15 19:27 ` [NTG-context] " Pablo Rodriguez
2023-08-15 20:16 ` Hans Hagen via ntg-context
2023-08-15 20:54 ` Pablo Rodriguez
2023-08-16 8:07 ` Hans Hagen via ntg-context [this message]
2023-08-16 17:46 ` Hans Hagen via ntg-context
2023-08-17 13:39 ` Pablo Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2023-09-04 17:22 [NTG-context] " Hans Hagen
2023-09-04 17:37 ` [NTG-context] " Pablo Rodriguez
2023-07-18 20:12 [NTG-context] " Hans Hagen
2023-07-18 21:53 ` [NTG-context] " Rik Kabel
2023-07-19 6:37 ` 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=fee41dda-9145-4651-20a8-334684707ff1@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).