With the next build of TransType 4, we hope that it already will be the best "build machine" for fonts: open an UFO, VFB, OTF, TTF - and generate OTF, TTF, WOFF, EOT, consistently, easily and quickly.Ģ.
I don't want to bore you with technical details, because it's not something the audience here is interested in. We've cleaned up the Adobe code internally, so problems like the inconsistencies mentioned above will no longer occur. TransType 4 and the upcoming products), it looks like it's finally going to be different. Which is, for example, why in current FontLab Studio, you'll get slightly different results if you make an OTF and a TTF from the same VFB.
Pretty much everyone in the business right now (FontLab Studio, Glyphs, RoboFont) has, in some way, been using that spaghetti code, so parts of font generation has been "out of control" of the font tool makers. It was not trivial, because the industry-standard solution to compile OTF is Adobe FDK, which we're also using, but in its current incarnation it's very tough spaghetti code which "does things" to font files on top of generating the "CFF" table and the OpenType Layout tables. It's interdependent: the fact that we're simplifying many things allows us to do the job more consistently and correctly, while speed is just a most welcome by-product for us.įor example, I've just learned from our developers that we'll be able to finally ship OTF generation in the next build of TransType. I should have said something like, "in addition". "Above all" was not the right I was meaning to use.
So far, I'm really happy with the progress. It includes quite a few brand-new inventions never seen in type design applications, which we think quite a few type designers will love.īut of course, developing a full replacement for an application as complex as FontLab Studio takes more time than redoing TransType - so we went with TransType first, to test our new development workflows. Our new font editor is quite well under way as well. Since then, it took us some 3 months to clean up some inner workings are get rid of the initial implementation bugs, but still - the speed we’re able to develop using Victoria is nothing short of amazing. We implemented the user interface and all of its internal algorithms within 5 weeks. By mid-October, it was a fully-functional "alpha quality" app. in form of a spec) at the beginning of September. And as an example of the efficiency: TransType existed "on paper" (i.e. But most importantly, it allows us to implement new functionalities much more quickly - and reduced the effort to port applications between Mac OS X and Windows from about 40% of the overall development time to about 3%.Īs an example of the speed: Victoria opens a large CJK UFO font in about 20 seconds, while it takes 15 minutes (!) to open the same font in an existing font editor with UFO support. It's much faster and much more reliable than our old codebase "Leningrad", on which FontLab Studio, TypeTool and the old TransType is based. So, TransType is a first step in the new direction. TransType is built on a new technology platform codenamed "Victoria", which will also be the foundation for our new type design applications. So is more flexible control over autohinting, and more control over webfont-generation, plus some more useful features.Īs Thomas has pointed out, some three years ago we've decided to rewrite our applications from scratch. including the ability to subset OpenType Layout features - which is something most tools that perform subsetting don't support). $amount = (double) number_format($transaction->getAmount(), 2, '.Subsetting (reducing the character set) is on our to-do list, done the right way (i.e. If (!is_numeric($transaction->getAmount()) || $transaction->getAmount() setOrder($transaction->getId()) Public function capture(CreditCardTransaction $transaction) * \Ilis\Bundle\PaymentBundle\Entity\Transaction\CreditCard $transaction
0 kommentar(er)
