Henry, now that the new text component (using the TLF) is in the LFC,
wouldn't it make sense to support the 'embedAsCFF=true' as an optional
property for the font tag?
And another question: Is there support for unicode ranges when
embedding fonts? E.g.
@font-face {
src:url("../assets/MyriadWebPro.ttf");
fontFamily: myFontFamily;
advancedAntiAliasing: true;
unicodeRange:
U+0041-U+005A, /* Upper-Case [A..Z] */
U+0061-U+007A, /* Lower-Case a-z */
U+0030-U+0039, /* Numbers [0..9] */
U+002E-U+002E; /* Period [.] */
}
http://livedocs.adobe.com/flex/3/html/help.html?content=fonts_07.html
On Thu, Jun 24, 2010 at 9:36 PM, Raju Bitter
<[email protected]> wrote:
> Yes, that's the best choice right now.
>
> On Thu, Jun 24, 2010 at 5:51 PM, P T Withington <[email protected]> wrote:
>> Sounds right to me!
>>
>> On Jun 24, 2010, at 11:47, Henry Minsky <[email protected]> wrote:
>>
>> See http://jira.openlaszlo.org/jira/browse/LPP-9140
>> and discussion at
>> http://richardleggett.co.uk/blog/index.php/2009/03/16/definefont4embedding
>>
>> What is happening is that Adobe has some new option for the format used in
>> embedding fonts for use with their new text layout framework.
>> They switched the default for this in the new version of the compiler we're
>> using.
>>
>> We can set this flag when the LZX compiler embeds the font. Setting to
>> CFF=true makes the font only usable in the new framework, setting
>> to false makes it available to the existing TextField.
>>
>> And ... we can apparently embed the font both ways if we wanted to, at a
>> cost of file size.
>>
>> I guess I'm going to make the compiler use the old embedding format for now,
>> until we switch to the new text sprite
>> implementation, and then switch it over.
>>
>>
>>
>>
>> --
>> Henry Minsky
>> Software Architect
>> [email protected]
>>
>>
>>
>
