BlogAll Blog Posts | Next Post | Previous Post
Friday, August 4, 2023
Some weeks ago, Microsoft released a new default theme and font for all Office applications, replacing the old Calibri. Yesterday, we updated FlexCel (VCL, .NET, and DLL), so you can now create a new file with those defaults too. It goes without saying, the old FlexCel versions will still work with the newer files, but if you want to make a new file from scratch using the new defaults, go and grab FlexCel 7.18.But in this post, I wanted to discuss something I haven't seen discussed often: at the time of writing, the new Aptos font is not available as a "Windows font" but as a "Cloud font" instead. Cloud fonts are nice in theory, but they have the big problem that they are only available to Office, so Windows (and your app) won't see them. And if your app doesn't find the font, it will use some substitute that will likely have different metrics, causing your layout to break when you print or export to PDF from FlexCel.
As a blog post gets buried by newer posts soon, we also published a new tip on how to deal with the new font here: https://doc.tmssoftware.com/flexcel/vcl/tips/cloud-fonts.html
Now, going back to our problem: The metrics of Aptos are very different from Calibri. Here is some example text to compare them:
first line is Aptos 11, the second is Calibri 11, and just for fun, I
added Arial 10 for the third line. As you can see, Aptos is narrower, so
text that might fit in a column when using Aptos, might not fit anymore
once you see this file with an app that is not Office and that uses a
You can also see in the screenshot that even Excel is not completely nailing this new "cloud font" stuff. If you look closely at column D, the gridline at the right of cell D1 is missing because Excel thinks the text doesn't fit in there even when there is a lot of space. Interstingly, cells D2 and D3 show the gridline, even when the text is wider. Why would Excel think that the text in D1 doesn't fit? Well, likely, it is using the substitute font instead of the cloud font for that measurement. This bug will probably be fixed soon, but I wanted to mention it to show that the whole thing might not be fully mature yet.
Now, let's compare it with what FlexCel sees. But before going into that, as FlexCel mimics a "Print Preview", let's see what Excel shows in Print Preview:
Ok, now the line with Calibri goes well into column E. That's not the same, but that's expected, and we can't do much about it.
So let's compare it with the FlexCel Preview:
What is this? Now the first line is wider than the other two. How is this happening? But before you ask for that deserved refund on your FlexCel purchase, let me say in its defense that it did the best it could. It asked Windows for the Aptos font, but Windows couldn't find it because it is a cloud font, so it returned a "substitute" font that Windows believes might be similar to this Aptos thing it doesn't know about. If you are curious, you can export this file to PDF and use this tip to find out which font FlexCel is actually using. Spoiler alert, the first line is in Arial 11. This same thing will happen in LibreOffice or Google Docs, or any other app that is not Office.
For example, this is Google Docs showing the file:
Note how the Aptos text in A1 was directly replaced with Arial.
So to end up this post, let's try installing Aptos in Windows itself and reopening the preview:
Much better now. That's as near the print preview in Excel as we are going to get. And just for completeness, now with the font properly installed Excel doesn't show the glitch at the end of D1 anymore:
So that's another reason to install the fonts in Windows directly and not use the cloud font approach. We hope the new fonts will be distributed with Windows soon, but until then, it might make sense to wait and stay with Calibri or Arial.
This blog post has received 5 comments.
All Blog Posts | Next Post | Previous Post