From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: support for "SUBSCRIPT THREE" etc. ?
Date: Tue, 21 Jul 2009 12:50:32 +0200 [thread overview]
Message-ID: <6faad9f00907210350o2961332eq2d62502d1431caae@mail.gmail.com> (raw)
In-Reply-To: <20090721102734.GA15542@khaled-laptop>
On Tue, Jul 21, 2009 at 12:27, Khaled Hosny<khaledhosny@eglug.org> wrote:
> On Tue, Jul 21, 2009 at 11:54:02AM +0200, Peter Münster wrote:
>> Hello,
>>
>> Is support for unicode range 0x2080-0x2089 planned?
>>
>> Superscript works well, but not the subscript:
>>
>> \starttext
>> x³ x₃
>> \stoptext
>
> Unicode sub/superscripts aren't real sub/superscripts, and there use is
> discouraged. Most fonts will align those subscript glyphs to the base
> line not bellow it, and apparently LM fonts don't have them.
In MKIV one could theoretically fix the (virtual) font with subscript
three containing "\sub{3}" *** or "lowered superscript 3" :)
*** The problem is that you would probably loose "monospace" by doing
that, but maybe you are not using monospace at all.
Mojca
___________________________________________________________________________________
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-07-21 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 9:54 Peter Münster
2009-07-21 10:27 ` Khaled Hosny
2009-07-21 10:38 ` Matthijs Kooijman
2009-07-21 21:09 ` Hans Hagen
2009-07-21 10:50 ` Mojca Miklavec [this message]
2009-07-21 21:10 ` Hans Hagen
2009-07-22 4:42 ` Michail Vidiassov
2009-07-22 5:47 ` Aditya Mahajan
2009-07-22 11:07 ` Hans Hagen
2009-07-22 7:48 ` Hans Hagen
2009-07-21 11:19 ` Peter Münster
2009-07-21 14:55 ` Aditya Mahajan
2009-07-21 11:27 ` Peter Münster
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=6faad9f00907210350o2961332eq2d62502d1431caae@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.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).