Hi, > Well, I'm told that "all" we really need is a way to convert TTF splines > to CFF splines and then read a TTF file and output a CFF blob. There's a > good chance that there is more to those libraries that Flex is actually > using. Sounds easy I'm sure you could knock that over in a day :-) I did take a quick look at the jars there's 1000's of classes involved, and complexities to do with LTR/RTL, CSS styles, different languages (Thai, Arabic + many others) - that been said I have no idea what's the minimal required to get it to work. Do we know what the API we need to implement/what flex actually uses?
> And that's why we need to write our own embedded font library. Time is > ticking on the 5-year commit from Adobe. Open source software (binaries or not) doesn't stop becoming open source just because Adobe decide to no longer support them, yes it would be good to have our own library but right now it's a question of reliable hosting to make usable SDKs, and that IMO seems an easier problem to solve. > If I am successful in creating a separate business to distribute this stuff Why do you need a business to do this? It it because Adobe will only give distribution licences to businesses? Many of us already have our own companies set up and could host the files. The issue then become is it economically to do so - bandwidth may be cheap but it's usually not free. > But really, we should find a way to get rid of that last dependency. BlazeDS is also a dependancy until we make a release of it. Justin
