[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ft-devel] Two questions about TT and TTX
|
From: |
FontGuy |
|
Subject: |
[ft-devel] Two questions about TT and TTX |
|
Date: |
Wed, 17 Jun 2009 13:33:21 -0700 (PDT) |
Hope this isn't too far afield from FreeType topic:
Doing a little noodling with fonts, I see two funny things that happen when
you send a font through TTX and back out:
(1): TTX seems to set bit 1 of the FLAGS in the <head> section.
! <flags value="00000000 00011001"/>
! <flags value="00000000 00011011"/>
TTX changes a bit in the FLAGS field of the header, specifically bit 1, the
penultimate LSB.
The official definition in
http://developer.apple.com/textfonts/TTRefMan/RM06/Chap6head.html
Says:
” If bit 1 is set to one, the x-position of the leftmost black bit is
assumed to be the left side bearing. “
Any idea what this means? The font does have left side bearing values,
always equal to the xMin value.
-----------------
(2) Similarly:
! <maxComponentDepth value="1"/>
! <maxComponentDepth value="0"/>
Quoting from: developer.apple.com/textfonts/ttrefman/rm06/Chap6maxp.html:
The maxComponentDepth refers to the number of levels of recursion used in
constructing the most complex compound glyph.
In TrueType 1.0, the maximum legal value for maxComponentDepth is one.
If there are no components within components, all compound glyphs can be
deemed simple and this field can be set to the value one.
---
I assume this means that Depth=0 is illogical, as you always need at least
one level of definition, and so TTX is just “improving” this value.
Any hints, references, or complaints appreciated.
--
View this message in context:
http://www.nabble.com/Two-questions-about-TT-and-TTX-tp24081516p24081516.html
Sent from the Freetype - Dev mailing list archive at Nabble.com.
- [ft-devel] Two questions about TT and TTX,
FontGuy <=