From: "Yue Wang" <yuleopen@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: typescript and font features bug?
Date: Sun, 21 Sep 2008 13:36:49 +0800 [thread overview]
Message-ID: <68bfdc900809202236j1f37dbcblca8c6e72168169fe@mail.gmail.com> (raw)
In-Reply-To: <48D4D7E9.5010108@wxs.nl>
> remark: using those st ligatures is pretty annoying (ok for older docs
> in french etc)
Maybe that's why text in The Elements of Typographic Style disable the
dlig feature?
(In fact I love them and always enable dlig in my documents)
>
> the funny punctuation is probably due to the frac features .. i found
> (in other fonts) that frac is a rather weird feature in the sense that
> it has to be applied very selectively if only because the contextual
> analysis definitions might not be complete at all
>
But it is strange that other engines render it well...
> for me it makes such features rather useless and i'll probably cook up
> my own solution by simply parsing the node list and replacing glyphs; on
> the other hand, even then we end up with suboptimal outcome
>
___________________________________________________________________________________
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:[~2008-09-21 5:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 13:35 Zhaopeng Xing
2008-09-19 13:36 ` Zhaopeng Xing
2008-09-19 13:39 ` Zhaopeng Xing
2008-09-20 11:00 ` Hans Hagen
2008-09-20 16:24 ` Zhaopeng Xing
2008-09-20 17:53 ` Jianning Dong
2008-09-21 5:26 ` Yue Wang
2008-09-21 16:07 ` Hans Hagen
2008-09-21 5:36 ` Yue Wang [this message]
2008-09-21 7:23 ` Yue Wang
2008-09-21 16:03 ` Hans Hagen
2008-09-20 10:54 ` Hans Hagen
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=68bfdc900809202236j1f37dbcblca8c6e72168169fe@mail.gmail.com \
--to=yuleopen@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).