ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: support for "SUBSCRIPT THREE" etc. ?
Date: Tue, 21 Jul 2009 10:55:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.0907211045110.13326@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <alpine.LNX.2.00.0907211312250.20614@gaston.couberia.bzh>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1688 bytes --]

On Tue, 21 Jul 2009, Peter Münster wrote:

> On Tue, 21 Jul 2009, Khaled Hosny wrote:
>
>> 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.
>
> Hello,
>
> In char-def.lua there is:
>
> [0x2074]={
>  category="no",
>  cjkwd="a",
>  description="SUPERSCRIPT FOUR",
>  direction="en",
>  linebreak="ai",
>  specials={ "super", 0x0034 },
>  unicodeslot=0x2074,
> },
> [...]
> [0x2084]={
>  category="no",
>  cjkwd="a",
>  description="SUBSCRIPT FOUR",
>  direction="en",
>  linebreak="ai",
>  specials={ "sub", 0x0034 },
>  unicodeslot=0x2084,
> },
>
> So I supposed, that the "specials" are for faking or simulating the unicode
> character, for example ² -> \superscript{2} or similar.
> Perhaps, my assumption is just wrong...

I am not sure whethere specials work at all. I am assuming that 
SUPERSCIRPT ONE, TWO, and THREE work because the LM font contain them at 
the right spot. These are less than hex FF. The others, for example, 
SUPERSCIRPT ZERO and SUPERSCRIPT FOUR do not work because they are not 
(AFAIU) mapped to any place in LM fonts. I don't even know if LM fonts 
have these or not. The same is true for SUBSCRIPT.

If you use a opentype font like cambria, superscripts and subscripts work. 
I guess that is because they have these symbols. If you swich to \tt with 
cambria, only sup 1,2,3 work.

So, the easiest solution will be to use a (maybe) virtual font that has 
these glyphs. Otherwise, using the active character trick is the easiest 
option.

Aditya

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2009-07-21 14:55 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
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 [this message]
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=alpine.LNX.2.00.0907211045110.13326@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).