Search the Community

At this point I'm starting to think they're holding back important features like variable fonts and webp support to put into a 2.0 release we have to pay to upgrade to.

@walt.farrell It turns out GF does have the current axis registry listed in a user friendly way. It is at the bottom of their variable fonts list - there is an Axis definitions tab. https://fonts.google.com/variablefonts#axis-definitions Those are just brief descriptions. The GF Knowledge info in-progress will expand on that with demo images, etc.

Since you had a previous version of Office installed, with fonts included, and now you have M365 in which Calibri is probably now a cloud font, I wonder if you have some sort of font cache issue. On Windows if you have a font actually installed it will not download the cloud font. For example to get it to download the static cloud versions of Bahnscrift, I had to delete the Bahnschrift variable font (which is protected). I would check to see if Calibri is in the CloudFonts cache folder. And I would check to see if Calibri is still installed in your normal fonts folder. APub can see the font like it is a normally installed font, so I assume it is there. If it was only a Cloud font, only Office apps could see it (like Word). I cannot check all this - we need some other Mac users with Office and Calibri. Ugh, cloud fonts, wadda nightmare.

Thank you very much for pointing to PDF format and for the link. So to avoid using variable fonts with APub or InDesign or whatever, it would be helpful to KNOW which fonts are variable and which ones are not. To be quite honest I haven't thought about this separation of fonts up to now. As Dov Isaacs writes it could take years until the PDF specification takes care of variable fonts. So there is no other way than avoiding these fonts, isn't there?

@walt.farrell Because nothing has happened regarding this in the "official" repo, Google Fonts established their own Axis Registry for their own use (and their web font API) and to provide some clarity to the entire variable font ecosystem. https://github.com/googlefonts/axisregistry It currently has 23 axes accepted into this registry. https://github.com/googlefonts/axisregistry/tree/main/Lib/axisregistry/data And there are many more axes proposed in the issues tracker: https://github.com/googlefonts/axisregistry/issues And there a few other proposals scattered around the GF repo. They do not treat this as "this is our way" but more of a place to get ideas, and feed back, and then to propose clear definitions of each axis to help everyone going forward. For example every one needs to be on the same page in defining the Italic axis vs. the Slant axis. So users will know what to expect when they encounter a font with these. There is also guidance on the "best" scale(s) to use the various axes, and why. I know this registry is not very helpful regarding clarity for the end user right now. But GF is currently working on an update to their GF Knowledge pages which will provide good descriptions of every axis - which will be very helpful for all end users. I see their updates and discussions almost every day as they work on this. You can see some examples of that here (they call it GFK): https://github.com/google/fonts/search?q=GFK&type=issues I am not sure of the timeline for publishing that, but they are diligently working on it. Since it is CC licensed we will be able to share it in different forms.

I want to use fonts downloaded from google fonts, and they download as a variable font ttf. So, without this feature, I'm restricted in design options. They do correctly load in kind of, in so far as the list of weights is the same length as the weights in the family, but one weight takes place for every single one. I'd consider this a bug. I see the topic goes back two years. In absence of the feature, can anybody recommend solutions to extract the individual weights from the ttf as a workaround?

@walt.farrell don't forget that they are still very useful for folks exporting to bitmap and vector (via curve outlines) formats, providing them with additional flexibility to customize and tweak their text elements using the various axis provided. This is especially useful as doing significant vector manipulation of outlined fonts in Designer is not exactly a pleasant experience currently, and having to redo that work should the text change makes me weep. The importance of being able to retain those text elements as editable text shouldn't be overlooked just because the output is rendered static (without variable fonts).

You're welcome. I am not sure what you mean by "picture in picture", but here is a clip showing what I mean by duplicating placed pages and cropping them so that parts that need to be updated are clipped out. In this case the year 2021 is updated to 2022 by using an existing "2" from a copy of the page, but basically fixes would need to be made by using installed fonts (or their close "relatives"). The idea, however, is to show that by using "Passthrough" you can reproduce (re-export) a production PDF without touching the original, which in this case was created in QuarkXPress 2018, using legacy Type 1 font [not basically "supported" anymore by the high and mighty] and having itself placed PDFs created in InDesign (Arabic text) and VectorStyler (variable font and warped text, which were vectorized already when initially creating the exported PDF by VectorStyler). The production PDF that was used in Publisher was created in PDF/X-1a:2001 (not reproducible by PDFLib that Affinity apps are depending on when producing PDFs), which needs to be exported using "PDF (press-ready)" to avoid rasterizations. The clip shows that nothing is rasterized, and parts that were initially fonts, are fonts still when exported from Publisher, and that all colors, including spot colors, are passed through. Attached are the source PDF, Publisher document, and fixed PDF. As mentioned, an easy alternative would be using a professional PDF editor like Adobe Acrobat Pro [still purchasable based on "perpetual" license model whatever that means especially on macOS platform] or PDF/X-Change, and directly change the year "2021" to "2022", and just save. PDF Expert (the macOS editor I purchased) could not do it, because it would not keep the spot color (and would not keep even a CMYK color). It would still be a useful tool when replacing, inserting or deleting single pages, arranging pages, or merging PDF files, disregarding the color space, and doing annotations and text editing RGB files.

I was reading the Microsoft docs page on that font and that seems to be the case. Even from a font managing standpoint, I am absolutely for abolishing separate, dedicated weight files. It could be interesting to have a “snap to weight” flag/checkbox, too. And the same goes to “snap to width” (on that subject why wouldn't you care for variable width? It would also simplify things on that department). Then again, that should become an OpenType and UX standard of sorts. IMHO, the only styles that could still be separated into their own files are the italics. Then again, it's not like there couldn't be a convention of sorts, a more restricted, glorified stylistic set of sorts, which could still allow for parametric changes to angle. That way, you could indeed have an instant upright italic, an oblique version, etc., all in the same file. Yeah, I got a bit lost there. I think as a type designer and font editor teacher, so this is just me creatively rambling at this point. In any case, Serif could and should be at the forefront of typographic innovation, instead of just focusing on illustration and classical DTP. I know it will take years for them to match Adobe's Single- and Multiline composers, RTL support, yadda yadda, but variable fonts are really just easy pickings, even if they're just based on a bunch of custom parameter sliders at this point. It's the standardization further down the road that really matters, and the only way for them to partake on that is to enter that market ASAP. Also, thank you for pointing me to that Microsoft font. I had absolutely no idea they were toying with variable fonts already. That makes me extremely hopeful for an eventual appearance of variable font support in Microsoft Office, and not just at the OS level. That would solve so many headaches, really…

Been sitting here looking at all these tools and thinking about this. There are another 4-5 online tools which also support variable fonts. Most of these tools really need a User Guide to get the most out of them. To do that properly would take quite awhile. A good idea, but time consuming. Think I will just do an Online Font Tools post - a kind of summary of all the tools. That would get people the web links and a good tool summary fairly quickly. Gawd I hate doing half-a$$ed docs; it is painful. Really needs lots of pics. But I guess it is good to get the info out there in some form sooner, rather than later.

Be warned though that Affinity applications cannot use Variable Fonts nor can they use Colour Fonts. You can use any font that is on your computer. There is no import/open of fonts in any of the Affinity applications. They all use the fonts which are on the computer. If you do not have the Lucida font on your computer you will have to find it and purchase it in order to use it in any application.

There are essentially 5 kinds of fonts in print. Windows offers 934 of them for free. A lot of them are not recognized by the Affinity suite. Opentype Collection: correct screen display | correct printing | buggy PDF export OpenType CCF: correct screen display | correct printing | correct PDF export Opentype TTF standard: correct screen display | correct printing | correct PDF export Opentype TTF variable: buggy screen display | buggy printing | buggy PDF export Opentype Truetype: correct screen display | correct printing | correct PDF export Here is an Affinity Publisher file showing an example in each case. To get all the free fonts for Windows, just go to the menu Customize/Fonts/Download fonts of all languages. You can also add the free fonts from Microsoft Store from the menu Get more fonts in Microsoft Store. fontes.afpub

In the light of the upcoming changes to the Apple platforms, the request for variable font support seems to get more importance than it may have had in the past. I guess there will be a day when Apple decides to remove the current non-variable styles of their San Francisco UI fonts from the developers page and leave only the single variable font file for download. And when that happens, design applications that do not support variable fonts will be difficult to use for developing apps intended for the Apple ecosystem. So, in a way, I have the impression it would make sense to start looking into this. Big Sur isn’t so far away anymore. 😀

Variable fonts are not supported i.e you can use the font under it's style such as bold condensed but you cannot change the weight of that style. Affinity also does not support Colour fonts, they will display as a single colour which can be a bit of a mess when the colours define the shape of the font.

Thanks, Hens. The PDF has been generated on my own computer, so uses the same OS. I think the software I'm exporting from may possibly use variable fonts. But I should still be able to substitute for static fonts, shouldn't I? I believe I have these installed for the font family in question.

If / when you can count on the support for colour svg fonts and variable var variable fonts? MAC and WIN systems recognize them, even AD shows them on the menu but then they are black

It appears InDesign does truly variable weights and not just predefined weights, if understand what variable is all about. I just downloaded a random variable font from Google Fonts and tested it out in InDesign. The font I picked only had variable weight apparently, but InDesign allowed me to put in values between 100 to 900, and when zoomed in, I could tell that there was a subtle difference between 100 and 101, for example. The PDF points you bring up may be a significant concern. I haven't experimented beyond that quick test above (and then I am intend to delete the font right away, lest I get it mixed up in Publisher unaware that support is not really there).

A HUGE thanks to the team for this upgrade. Have been wrestling with my first large Affinity Publisher book project – since moving from InDesign – for a couple of months. The file is north of 400 MB with hundreds of illustrations across 317 pages. Just moving through the file by scrolling in the Pages panel took several minutes, and threw up more beach balls than a record attempt in Florida. Updated to 1.10 this morning. Completed an author's correction that would have taken several frustrating minutes in less than half-a-minute. This update is a game changer for those of us working with large files. Ten times faster – seems an understatement. So well done. And now we know where all that developer effort has been directed for the last several months. With that work done, can I put my hand up for some developer attention to supporting variable fonts? An increasing number of new fonts, such as through vendors like MyFonts, include a variable option as matter of course. In the works?

Thanks Walt. I'm not clear on how these are variable fonts, to begin with, there are no variants; e.g., light, condensed, regular, etc.

Figma now has support for RTL fonts (for Arabic, Persian, Urdu, Hebrew etc.) and has supported variable fonts — through a plug-in — for some time already. Over the last few years I’ve been a big Affinity fan, and supporter, but Affinity is slipping behind when it comes to typography (there are still some rough edges with font support, especially for those with lots of alternatives and contextual features). Type is central to what most of us use Affinity applications for (especially Publisher) and I’d like to see their type handling be ahead of the curve, rather than perpetually languishing behind it.

Wow. Finally got access to all the Big Sur fonts. Wadda mess. Just being old or from a Type-1 conversion is not a good reason to be crap - there are hundreds of old Type-1 conversions and old font families in MyFonts and they are configured correctly. Commercial font vendors care that their fonts work correctly for the widest audience of buyers. It takes about five minutes to fix the fonts to work properly in all OSs and applications. And there is no downside to configuring them properly. Helvetica Neue - that is one bunch of bizarre fonts. Because of the language coverage I thought it may be a version of Helvetica Neue World. But it has a really odd collection of languages which is obviously custom. It even has Cherokee, but it is from some other serif font (looks like Plantagenet Cherokee). Very weird. There is no rhyme or reason to the style group settings. Which would seem to be on purpose. Avenir Next - again quite odd. And again completely messed-up style group settings. Again, there does not appear to be consistency in how the style group settings are wrong. It just seems random. There are larger font families which are correctly configured (such as Seravek). But are we to believe New Peninim MT came from Monotype already messed-up? Helvetica Neue, and Avenir Next are not going to work properly. And New Peninim MT, and Arial HB, etc. As you mentioned, this also causes problems with apps on the Mac such as Affinity apps, and others. Shipping broken fonts is a really bad practice. Also I find it quite amusing that while the static versions of San Francisco and New York are somehow broken, the variable versions of San Francisco and New York magically have all correct instances. They cannot sabotage the variables or they will not work correctly. 🤣

You've installed a Variable font, but the Affinity applications only support Static fonts.

I think this is going to be font related. If you see the attached screenshot, Affinity is picking up some of the text as being in a font called: Source Sans Variable It does appear there is a variable font called Source Sans Variable HOWEVER as we don't support Variable Fonts at the moment, i suspect this is why the text is removed. If you have access to the AI file, you should be able to edit the Text and change it to a non-variable Font, re-save as PDF and that will open fine in Designer.

Is the missing font the "a specific font"? One source of missing fonts in things I have worked with are 'empty paragraphs' (just a carriage return) from imported text files which specify a particular font either in a Paragraph Style or just set in the word processor application. There are some fonts which don't work with the Affinity Applications, Coloured fonts Variable fonts and original PostScript fonts to name a few.

Welcome to the Affinity forum! Is it possible, that you installed the variable font version? Right now the Affinities do not support variable fonts. So as a workaround you have to install the static version of this font and uninstall the variable font version.