ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Cc: mailing list for Aleph <aleph@ntg.nl>
Subject: Re: OpenType fonts
Date: Sat, 17 Dec 2005 10:58:08 +0100	[thread overview]
Message-ID: <43A3E130.7050702@elvenkind.com> (raw)
In-Reply-To: <op.s1wdpft8nx1yh1@walayah1.wildblue.com>

Idris Samawi Hamid wrote:
> Hi all,
> 
> OpenType fonts are all the rage today. Are there any critiqes of the  
> format, or discussions of its limitations?

Despite it's apparent "smartness" and a lot of media hype, OpenType
is still just a collection of glyphs and metainformation.

XeTeX makes OpenType look intelligent, but that is because the program
logic is wholly embedded in Mac OS X. At the core level, the real big
difference with TTF and Type 1 is just that there is *more* metainfo
(I am over simplifying it a bit, but not much).

Aleph, or pdfetex, for that matter, will need extensions to make
actual use of the extra metainformation. Whether that needs a new
kind of OpenType-Font-Metric file or whether it can be done in
macros/primitives is not clear yet (at least not for pdftex)

> How many typesetting applications can actually take full advantage of  
> opentype fonts?

There is a table at:

   http://www.opentype.com/html/opentype.aspx

but how up-to-date that is, I do not know.

> What are the chances that OpenType (at least some of its advanced  
> features) will go the way of MultipleMaster fonts?

Do you mean "embedded metaness" or "terminated for marketing reasons"?
the first, I doubt (too many font vendors involved with the spec; they
can make more money from selling separate fonts) the latter is, of
course, always possible but seems unlikely in short and medium time.

Cheers, Taco

  reply	other threads:[~2005-12-17  9:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16 22:21 Idris Samawi Hamid
2005-12-17  9:58 ` Taco Hoekwater [this message]
     [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=43A3E130.7050702@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).