From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: thinrules width
Date: Mon, 14 Dec 2020 21:08:08 -0500 [thread overview]
Message-ID: <4deda32b-0570-45af-227e-5c84395dd17e@rik.users.panix.com> (raw)
Hello list, and developers in particular,
I note that thinrules (and its setup, setupthinrules, and relatives
thinrule and hairline) does not have a width setting, and always sets a
rule (or rules) the full width of the text area (less any text set on
the same line.
No problem, but I do see (non-authoratative) references in the mailing
list to such a parameter, and more problematically, I note that the
default ConTeXt template for Pandoc includes the line:
\setupthinrules[width=15em] % width of horizontal rules
Before reporting an issue to the Pandoc team, I just want to confirm
that this is, in fact, both the case (as reading the source and my
testing indicate) and the intent (which I cannot attest).
I would further suggest that Pandoc should be using setupblackrule with
appropriate height, depth, rulethickness, and width. I suspect that
Pandoc typography is not sensitive to control of the actual placement
relative to the baseline, as ConTeXt supports, but a pointer to a clear
explanation of the interaction of height, depth, and rulethickness would
be welcome.
--
Rik
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2020-12-15 2:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4deda32b-0570-45af-227e-5c84395dd17e@rik.users.panix.com \
--to=context@rik.users.panix.com \
--cc=ntg-context@ntg.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).