From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Luatex fails to load a font
Date: Tue, 16 Sep 2008 23:29:58 +0200 [thread overview]
Message-ID: <3DF8C593-9991-474C-866A-CE2380A50818@fiee.net> (raw)
In-Reply-To: <6b36c7890809161129k2ec37eb0r5a12700b585c6861@mail.gmail.com>
Am 2008-09-16 um 20:29 schrieb holzminister:
> I thought that OpenType is quasi an extended TrueType. Wikipedia says:
> "OpenType Filename extension .otf, .ttf". So it isn't obvious why one
> schould not mix the two parts in one directory.
OpenType can internally use TrueType outlines or PostScript outlines
(different algorithms). OpenType with PS outlines normally use
the .otf extension; OpenType with TrueType outlines are valid TrueType
fonts and therefore normally use the .ttf extension. But OpenType
fonts are never valid PostScript fonts.
By far not every TrueType font is OpenType compatible: OT-TT fonts
have their characters encoded in Unicode and may use OT features;
"normal" TT fonts often use default/custom one-byte encodings.
The ordering in the TeX tree is probably a matter of taste, but you
would even more confused to find .ttf fonts within the "truetype" as
well as "opentype" folders, for you can't know (without tools) what's
really in the font's guts. And don't you think it would be
questionable to draw a line between Unicode encoded TrueType fonts
with and without OpenType features?
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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-16 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 11:10 Eyke Höft
2008-09-16 12:11 ` Taco Hoekwater
2008-09-16 12:30 ` holzminister
2008-09-16 13:29 ` Thomas A. Schmitz
2008-09-16 14:03 ` holzminister
2008-09-16 14:25 ` Arthur Reutenauer
2008-09-16 18:29 ` holzminister
2008-09-16 21:29 ` Henning Hraban Ramm [this message]
2008-09-17 6:57 ` holzminister
2008-09-17 7:09 ` Wolfgang Schuster
2008-09-17 12:29 ` holzminister
2008-09-17 12:38 ` Wolfgang Schuster
2008-09-16 14:41 ` Hans Hagen
2008-09-17 7:08 ` holzminister
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=3DF8C593-9991-474C-866A-CE2380A50818@fiee.net \
--to=hraban@fiee.net \
--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).