On Wed, Mar 28, 2012 at 10:20 AM, Alex Harui <aha...@adobe.com> wrote:
> > On 3/28/12 5:31 AM, "olegsivo...@gmail.com" <olegsivo...@gmail.com> wrote: > > > Yes Martin, I understood the legal problem. I was just wondering what is > > particular about the code that it cannot be replaced by other (modified) > > font managers. As you probably know, there are 4 managers currently in > SDK > > which can encode fonts using somewhat different techniques, but only one > > can encode them in a way they fit for the use with the FTE classes. This > > is, I assume, the one Alex is talking about. So my question was rather: > > > > what if we take on of the existing managers and modify it so it will > > generate DefineFont4 tags - how much of an effort will it require? Or > maybe > > the technology itself is patented (I doubt this very much... but you > never > > know)? > > > I'm still trying to make sure I understand both the technical and legal > issues. I see specs for CFF and DefineFont4, but there are rumors that the > conversion is currently done via proprietary algorithms. If we (Apache > Flex) just write our own, there may be a quality issue. > > Does Falcon come with support for CFF Fonts? When it is open-sourced, will it be gimped in the same way when it comes to fonts?
