On Apr 23, 2008, at 12:18 PM, Christopher Barker wrote:
Nathan wrote:
Oh, and if you have any X11-related development questions (libpng,
for
example),
I don't have leopard, so I'll ask you -- does X11 include both
libpng and libfreetype? If so , then I guess that's the way to go
for the Leopard builds -- maybe Apple will make our lives easier
eventually.
-Chris
A couple notes on Apple's X11 Freetype build:
* Strangely, Apple doesn't build Freetype with a few Apple-specific
options (ftoption.h):
- TT_CONFIG_OPTION_BYTECODE_INTERPRETER - to use the TT hinting. As
the ftoptions.h note says for this, the hinting (code?) is patented.
I take the (very possibly naive) view in my framework that since we
Mac users are using this in OSX, we can use this. If others know
better, I can always remove this from my framework builds (maybe the
FT auto-hinter works well enough).
- TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED - affects composite glyphs,
the option is a matter or how Apple vs MS defines offsets. So why
does Apple not build FT with Apple offsets?!
There are some issues in the OSX 10.4 X11 Freetype handling Mac
suitcase-packaged fonts, and I think a couple font package formats
were left out (dfont?). They are probably fixed in Leopard's X11 FT,
since it uses FT 2.3.5. But this leaves a disparity between Tiger and
Leopard as to what is supported.
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"This is a question about the past, is it? ... How can I tell that the
past isn't a fiction designed to account for the discrepancy between
my immediate physical sensations and my state of mind?"
- The Ruler of the Universe
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig