From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Michael Saunders <odradek5@gmail.com>
Subject: Re: footnote marks fail
Date: Tue, 13 Apr 2010 12:22:20 +0200 [thread overview]
Message-ID: <4BC445DC.9000100@wxs.nl> (raw)
In-Reply-To: <u2u54d7f5601004130316peade7798xdf3fd5e0c7911942@mail.gmail.com>
On 13-4-2010 12:16, Michael Saunders wrote:
> Taco Hoekwater wrote:
>
>
>> I may be missing something on my side, but I can't get sups=yes
>> to work at all.
>>
>> \definefontfeature[default][default][mode=node,script=latn,sups=yes]
>> \switchtobodyfont[palatino,11pt]
>
> It may well be that this palatino doesn't have the sups feature. Let
> me put it this way:
>
> \starttext
> text1\footnote{1footnote}
> \stoptext
>
> This will produce four instances of the numeral '1'. Suppose I want
> them all to look exactly alike. In other words, suppose I didn't want
> either footnote mark to be rescaled or elevated at all. How could I
> do that?
you cannot trust open type features like sups and frac as you can never
be sure how complete these are and if the ruled laid down in the font
are okay; some of these features are really meant to be applied
specifically (select piece of text and apply in dtp)
i have plans to cook up an alternative font handler fot such features
(using shapes but not feature info per se)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| 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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-04-13 10:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 10:16 Michael Saunders
2010-04-13 10:22 ` Hans Hagen [this message]
2010-04-13 10:33 ` Taco Hoekwater
2010-04-13 11:16 ` Peter Münster
2010-04-14 16:20 ` Steffen Wolfrum
-- strict thread matches above, loose matches on Subject: below --
2010-04-13 18:09 Michael Saunders
2010-04-13 10:53 Michael Saunders
2010-04-13 11:24 ` Peter Münster
2010-04-13 17:52 ` Sebastien Mengin
2010-04-13 18:09 ` Wolfgang Schuster
2010-04-13 18:13 ` Taco Hoekwater
2010-04-13 20:07 ` Sebastien Mengin
2010-04-13 20:18 ` Taco Hoekwater
2010-04-14 14:00 ` Hans Hagen
2010-04-12 23:52 Michael Saunders
2010-04-13 6:47 ` Taco Hoekwater
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=4BC445DC.9000100@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=odradek5@gmail.com \
/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).