From: "Idris Samawi Hamid" <ishamid@colostate.edu>
Cc: mailing list for Aleph <aleph@ntg.nl>
Subject: OpenType fonts
Date: Fri, 16 Dec 2005 15:21:05 -0700 [thread overview]
Message-ID: <op.s1wdpft8nx1yh1@walayah1.wildblue.com> (raw)
Hi all,
OpenType fonts are all the rage today. Are there any critiqes of the
format, or discussions of its limitations?
How many typesetting applications can actually take full advantage of
opentype fonts?
What are the chances that OpenType (at least some of its advanced
features) will go the way of MultipleMaster fonts?
The answers to these questions have a bearing on my own advanced Classical
Arabic script project. For example, the ovf+ocp mechanism of Aleph seems
much richer than what otf offers, so should I bother with otf at all or
just stick to enriched Type1 fonts (>256 glyphs, used by LatinModern)?
I may be mistaken, but it seems that the Aleph utilities need updating to
take full advantage of enriched Type1 fonts (not to mention otf fonts).
Right now I am still building ovf's from a series of standard type1's.
Here is one possible limitation of otf (please correct me if I'm wrong):
While an otf can contain an alternate glyph of a given character, it
cannot tell the typesetting application that, if there is the equivalent
to underfull paragraph spacing, replace the default <glyph>.1 with
<glyph>.2. This sort of thing is common in, e.g. old Arabic lead-press
books and in handwritten books. TeX should be capable of this, though it
remains to be seen whether this should be implemented at the engine level
(a la pdfetex) or at the macro level.
Best
Idris
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
next reply other threads:[~2005-12-16 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 22:21 Idris Samawi Hamid [this message]
2005-12-17 9:58 ` Taco Hoekwater
[not found] ` <op.s1wituiynx1yh1@walayah1.wildblue.com>
[not found] ` <op.s1wjhmttnx1yh1@walayah1.wildblue.com>
[not found] ` <1134825201.43a40ef110463@diogel.enst-bretagne.fr>
2005-12-17 17:50 ` [Aleph] OpenType-to-TeX and other musings Idris Samawi Hamid
2005-12-18 14:16 ` Hans Hagen
2005-12-18 16:32 ` Idris Samawi Hamid
2005-12-18 20:07 ` Hans Hagen
2005-12-19 17:35 ` [OT] Was: " David Wooten
2005-12-19 19:58 ` Hans Hagen
2005-12-19 20:08 ` David Wooten
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=op.s1wdpft8nx1yh1@walayah1.wildblue.com \
--to=ishamid@colostate.edu \
--cc=aleph@ntg.nl \
--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).