incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [FALCON] Fonts Question
Date Tue, 13 Nov 2012 04:31:39 GMT
Actually, I am suggesting writing enough code to not require the Adobe font
jars anymore.  First, it complicates the install, second, it is one more
dependency on Adobe, third, it requires everyone to re-tool their
application build scripts, making it another reason not to switch.

The backup or interim plan would be to leverage the Adobe font jars by using
code from MXMLC.

Either way, the transcoding should be stored in a "meta" file and simply
injected at link time.  In the end, it is just a DefineFontXXX in the SWF.

But if others think our customers won't mind having that extra step then
I'll go with that.

-Alex


On 11/12/12 8:23 PM, "Om" <bigosmallm@gmail.com> wrote:

> I agree that the ttf to swf transcoding does not have to happen during
> compile time.   We could build tooling separate from the compiler to make
> this conversion easier.  Such tooling can take advantage if the fontswf
> utility from Adobe.
> 
> At some point, when we write our own transcoder, we can revisit the
> question of whether we want to do that during compile time or not.
> 
> Thanks,
> Om
> On Nov 12, 2012 7:42 PM, "Gordon Smith" <gosmith@adobe.com> wrote:
> 
>> I don't recommend this for a new compiler because font transcoding is so
>> slow that it should really be done only once, before compilation.
>> 
>> - Gordon
>> 
>> -----Original Message-----
>> From: Gordon Smith
>> Sent: Monday, November 12, 2012 7:41 PM
>> To: flex-dev@incubator.apache.org
>> Subject: RE: [FALCON] Fonts Question
>> 
>> Alex is suggesting writing a transcoder tor Falcon that uses Adobe's
>> proprietary font JARs. He says this is what Apache's version of the old
>> compiler has.
>> 
>> - Gordon
>> 
>> -----Original Message-----
>> From: Cyrill Zadra [mailto:cyrill.zadra@gmail.com]
>> Sent: Monday, November 12, 2012 6:42 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: [FALCON] Fonts Question
>> 
>> So basically for flash we've got following options:
>> ** create swf fonts from the ttf fonts and rewrite the mustella tests to
>> use the swf fonts
>> ** write an own transcoder from ttf to swf For html we don't need anything
>> like that because it already supports a bunch off font format like ttf, svg.
>> 
>> Did I got that correct?
>> 
>> 
>> On Mon, Nov 12, 2012 at 4:18 PM, Gordon Smith <gosmith@adobe.com> wrote:
>> 
>>> I'm not sure. The engineer who did the font embedding for Falcon left
>>> Adobe recently.
>>> 
>>> We felt that the compiler shouldn't be doing font embedding because it
>>> is inefficient to transcode the font more than once.
>>> 
>>> - Gordon
>>> 
>>> -----Original Message-----
>>> From: Alex Harui [mailto:aharui@adobe.com]
>>> Sent: Monday, November 12, 2012 2:02 PM
>>> To: flex-dev@incubator.apache.org
>>> Subject: Re: [FALCON] Fonts Question
>>> 
>>> 
>>> 
>>> 
>>> On 11/12/12 1:46 PM, "Gordon Smith" <gosmith@adobe.com> wrote:
>>> 
>>>> Then you would have a compiler that you couldn't distribute because
>>>> it required Adobe JARs.
>>> No, that's the way Apache Flex distributes MXMLC today.  Everything
>>> compiles and runs, but embedding doesn't work if you haven't gone out
>>> separately and downloaded the Adobe font jars.
>>> 
>>> I'm just wondering if how hard it would be to re-purpose some of that
>>> code from MXMLC into Falcon.
>>> 
>>>> 
>>>> - Gordon
>>>> 
>>> 
>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>>> 
>>> 
>> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Mime
View raw message