From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Fractions
Date: Sun, 10 Dec 2023 13:24:27 +0100 [thread overview]
Message-ID: <6407fa4a-6117-4e1d-b70b-eb029cbc05e6@fiee.net> (raw)
In-Reply-To: <CAHy-LL-n9kd8LSEv24J=0iD=D+t8S5aFjW3UTUyj91jEt9h0+g@mail.gmail.com>
Am 09.12.23 um 23:30 schrieb Mikael Sundqvist:
> Hi,
>
> On Sat, Dec 9, 2023 at 4:39 PM Wolfgang Schuster
> <wolfgang.schuster.lists@gmail.com> wrote:
>>
>> Fabrice Couvreur schrieb am 09.12.2023 um 17:19:
>>
>> Very clear !
>> In typography for Mathematics books, what choice should we make for the best possible result ?
>>
>> A question better answered by Mikael or Aditya!
>
> Thank you for your trust, Wolfgang. I am not sure I have something
> valuable to say in addition to Adityas suggestion \frac{1/3} in inline
> math. In any case, I attach a passage, with suggestions inspired by
> Lansburgh's book (iin Swedish). Not sure the file size makes it
> through to the list, though.
Thank you!
I usually only need simple inline fractions like 1/n, 1/2 or 3/8 in text.
With these and \frac, the spacing below the numerator (depth) is too
big, while the denominator sticks too tightly to the fraction bar.
(Of course I use regular numbers for fractions, not mediaeval.)
Usually I’d prefer “vulgar fractions”, but \vulgarfraction looks
“horrible” in comparison to the few usual fractions contained in fonts
(like ½ & ¾).
I tried to use the OpenType fraction features to no avail.
So I’m still looking for “the best” solution for simple fractions inline.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-12-10 12:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 13:43 [NTG-context] Fractions (was \placefigure[location=here...] problem) Wolfgang Schuster
2023-12-09 13:57 ` [NTG-context] " Henning Hraban Ramm
2023-12-09 14:47 ` anton.chigurh
2023-12-09 15:13 ` Fabrice Couvreur
2023-12-09 14:52 ` Wolfgang Schuster
[not found] ` <CACyK-ep3tOb5w5pWwqYBt5pOwBFGr=H19vGbJ9pJ61Xmz7zwtw@mail.gmail.com>
2023-12-09 15:39 ` Wolfgang Schuster
2023-12-09 22:30 ` Mikael Sundqvist
2023-12-10 12:24 ` Henning Hraban Ramm [this message]
2023-12-10 13:19 ` [NTG-context] Re: Fractions Gavin via ntg-context
2023-12-11 14:23 ` Henning Hraban Ramm
2023-12-09 15:33 ` [NTG-context] Re: Fractions (was \placefigure[location=here...] problem) Aditya Mahajan
2023-12-10 11: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=6407fa4a-6117-4e1d-b70b-eb029cbc05e6@fiee.net \
--to=texml@fiee.net \
--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).