If I remember correctly one of the main reasons we started embedding fonts was to be able to rotate text on reports. The other being a consistent font no matter the platform/browser. We had to embed a normal font and a bold one. To make a smidge smaller, we used the "unicode-range" in the CSS.
-Mark -----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, December 07, 2015 12:41 PM To: dev@flex.apache.org Subject: Re: Mustella fixing (was Re: Next Flex SDK release) On 12/7/15, 9:07 AM, "Kessler CTR Mark J" <mark.kessler....@usmc.mil> wrote: > > To me it makes to have mx labels in the MX charts. If we create >some spark charts, using spark labels would make sense. However you >would have to embed the fonts again. The downside to not embedding the >fonts and just using what your default font is, the tests would show >bitmap compare issues more frequently. Right now it looks like the >majority of the failures are bitmap comparisons. Right, the failures are bitmap failures because there are slight differences in the way TextField vs TextLine render text. I don't know if that matters to anyone or not. If we decide not to support embedded fonts for Spark Label, then someone can just cut new baselines and the bitmaps will compare again. More background: Back in the Adobe days, there wasn't enough time on the schedule to create a whole new set of Spark Charts, plus I believe that the thinking was that because Charts already provided a consistent approach to customization of every aspect of the visuals, there wasn't much to be gained by trying to create a whole new set of components on top of SkinnableComponent. IOW, the actual chart component itself (PieChart, BarChart, etc) doesn't have anything to be skinned, and it wasn't clear that was much to be gained by having the things like the Axis and lines and bars and wedges and other pieces be SkinnableComponents. So, a bunch of code was added so that, if there is a Spark Label linked into the SWF, the Charts would default to using that, otherwise in a pure MX project, they use MX Label. I think that was done so you could use Charts in Mobile projects which are supposed to be Spark-Only (and other Spark-only desktop and web projects). Maybe the better question is: Do any of you actually create Spark-only apps? I don't know what the cost of embedding a font twice is for the larger unicode fonts, but I thought that folks building out Mobile apps were trying to make them Spark-only. But maybe you don't embed fonts in Mobile apps or the additional size isn't a problem? And as I mentioned earlier, I don't know if right-to-left text actually would work in Charts with Spark Labels and whether there are other things you can do with embedded CFF fonts that folks won't be able to use in Charts that matter either. So from a capabilities standpoint, I think we should support Spark Label and embedded CFF fonts, but from a practical standpoint, I'm unclear whether it is worth it. -Alex
