[swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
spjwebster at gmail.com
Tue Jul 25 09:14:02 EDT 2006
> > DefineFontInfo3 and DefineFont3 are complex beasts which contain
> > hinting information for font glyph pairs. I wouldn't even know where
> > to start with this.
> i suppose you mean kerning, not hinting? kerning was/is already supported with DefineFont2, it was simply unused by the FlashIDE until flash8. the late players seem to interpret it fine (see http://0xdf.com/?p=50 ). So unless it's really "hinting", DefineFont3 would be interesting only for swf2xml magic. I wouldn't know where to get hinting info from-- TTF supposedly contains a turing-complete hinting language, which is patent-encumbered. i doubt flash supports much like that (tho i might be mistaken).
It really is hinting - sort of. The new DefineFontAlignZones tag
(which we're calling DefineFontInfo3) defines the borders of each
glyph to use pixel snapping. Don't know where I got the 'pairs of
glyphs' bit from - I might have skipped a page onto the kerning
information. Full hinting is seemingly beyond the capabilities of the
> Personally, i'd be fine with the current (minimal) DefineFontInfo3/DefineFont3 support. It means those tags can be imported fine, and that should be what matters most. But then again, i'd personally be fine without any flash8 tags (it would decrease me having to resort to wine :)...
> if anyone requires swfmill to fully understand those tags, please at least come up with a usage scenario :)
I agree with this. At the very least now they will round-trip from swf
=> xml => swf
More information about the swfmill