Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of omuppi1@gmail.com designates
 74.125.82.175 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: 
 <149F8129B58B2D418508E63117D9C5419B5B2241EA@nambx05.corp.adobe.com>
References: 
 <149F8129B58B2D418508E63117D9C5419B5B224143@nambx05.corp.adobe.com>
	<CCC6B1D5.4857A%aharui@adobe.com>
	<149F8129B58B2D418508E63117D9C5419B5B2241C2@nambx05.corp.adobe.com>
	<CAOHe5BHdg-cL0Am4z5wdEqsHcKAuYY+oh=fjbXOJV=6ybh++2w@mail.gmail.com>
	<149F8129B58B2D418508E63117D9C5419B5B2241EA@nambx05.corp.adobe.com>
Date: Mon, 12 Nov 2012 20:23:33 -0800
Message-ID: 
 <CACK5iZc_LgC=Hepn6Em4cqMtgLdwQBG8w__cDqv=tUvjEh0aPw@mail.gmail.com>
Subject: RE: [FALCON] Fonts Question
From: Om <bigosmallm@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016e6dbe932f83f9704ce58c72e

--0016e6dbe932f83f9704ce58c72e
Content-Type: text/plain; charset=ISO-8859-1

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
> >
> >
>

--0016e6dbe932f83f9704ce58c72e--