Search the Community

Hi @BarbaraSki, Thanks for the link... When you download the font from Google Fonts and Unzip the file you 'should' see the following, i.e., both the single 'Variable Font'... along with a folder labelled 'static'... If you've installed the variable font, i.e., just the single .ttf file then you have the variable version installed. If this is the case, if you remove this in your font manager and then install all the static versions of Frank Ruhl Libre and reopen your Publisher file, it should automatically substitute the static versions for the variable version but if it doesn't because of the variable font settings used in your Publisher file you will need to re-apply the static versions accordingly... Once you've done this you should find that exporting your Publisher file to a PDF will display the fonts correctly...

That's part of the issue with Variable fonts: they're not supported in PDF files. Instead, the application needs to generate Static versions of the fonts to embed in the PDF file, and Affinity doesn't do that.

The solution is to avoid using Variable fonts; only Static fonts are supported in the Affinity applications. Your client will need to provide a statis version of that font, or you will need to use a different application.

I think that is a bit of an over reaction saying "I can't even do basic graphic design tasks that involve any text...". While variable fonts are great and a nice addition, there are still hundreds of thousands of fonts to do all sorts of great and wonderful things. I like the idea of variable fonts but rarely ever use them as most font families cover all my needs. I do agree it is something that should be added, it will be the future of fonts for sure, but I don't think there is going to be a big tidal wave and everyone stops using traditional fonts as we use them now, it is just going to take a while as new fonts are created and new standards set.

In my example above it was a font from Adobe Fonts (not a variable one). The bug also occurs if I replace it with Montserrat. I attached a test file. test.afdesign

The variable bundle includes the static fonts, from what I have read on that site:

Agreed, along with variable fonts, and this has been brought up many times in the past. For something like this particular example you can use a normal font and make the text a mask for a picture (in this case of a flag) behind the text, but it would obviously be more convenient to use a pre-rigged font like that, and other examples of color fonts may not be quite so easy to mimic in that manner.

You have a number of Variable fonts installed, I think. That probably does not account for startup problems, but they aren't supported in the Affinity applications and won't work properly in them. Compare the Style listings for Calibri and Nitalove, for example. There are others like Nitalove that show multiples of the same Style. I'm not sure how to explain what Cascadia Mono shows, unless this means you have multiple copies of the font installed. Again, I would not expect that to cause startup problems, but could cause issues working with the font in the Affinity applications: Sitka also looks odd, to me. And several others. I'm also seeing multiple sets of listings for some of these fonts (including Cascadia Mono, Sitka, and Segoe UI Variable), and I don't know how to explain that.

Thanks for responding, Walt! I looked a bit more into the particular font files, and they indeed are variable. Each file is meant to be a different "instance" of the variable font. I tested it in MS Word just to be sure, and it also breaks there. However, MS Word does render the Black weight of the font correctly, and some other weights incorrectly. Hopefully a future version of Affinity will support variable fonts.

Adobe seems to support them just fine. Of course, they are both the creators and main implementers of the PDF format, and creators, distributors and heavy promoters of variable OTF fonts, seeing how it's just a development of their old Multiple Master format (seriously, the other day I was playing around with a really old version of Illustrator, running on System 7.6 on top of Basilisk II, and I was absolutely shocked at just how similar the interface for manipulating Type I MM fonts was to their current implementation), so they obviously have their work cut out for them. Unless Adobe, Corel et al. have some sort of weird patents, it should be just a case of opening their files and reverse-engineer them. Voilá, presto! Anyway, and AFAIK from my own look into it way back when, Adobe's apps just take whatever interpolated values you picked and export the end result as bespoke, automatically-generated and embedded fonts for the relevant text strings (yes, a separate one for each combination of variables), so there's no need for converting stuff to curves, losing the ability to select text or ballooning file sizes, the works. Of course, when reimporting, you absolutely must have also an embedded Illustrator file stream, otherwise you're completely screwed. Perhaps you could look into making your own implementation of PDF files with embedded .afdesign or .SVG streams, or just metadata for the relevant text strings to save on file size, so that one could in theory reconstitute those multiple resulting fonts into their parent variable OTF fonts/styles? As others have said, variable OTF fonts are just not going away; not this time, and especially not with the might of Adobe TypeKit and Google Fonts behind them. Heck, even I wrote a paper on those; you can check it out in my ORCiD page in my bio if you want. And, as I've said before, my students are really using them in earnest (… as attested in said paper), which means that when they leave the Uni and enter the workforce, they'll either keep using Adobe CC, or switch to something else altogether, like Sketch. I know you don't like to hear this, and please don't shoot the messenger, but… I did warn Serif (a company called, of all names… SERIF!) years in advance of just how relevant and pervasive they would become. 🤷‍♂️ I cannot stress this enough, and to all the people rightly clamouring for RTL support: variable OTF font support should be included in a splashy v.2.x update (not a v.2.x.x one, but a full-blown point update, and maybe even a jump to v.2.5 for good measure), and RTL could very well wait for v.3… Allow me to explain: the RTL market is not even considering Affinity apps at the moment, at all, so they're not exactly invested in them, whereas a lot of designers, be they young and aspiring or established veterans, may have bought Affinity 1.x (let alone 2.x, because this thread and all related discussions date back to the v.1 days, if I may remind you all), with the expectation of it being a professional package somewhat approaching feature-parity with its peers (in their Latin-centric bubble, for sure, but it is undeniable that the vast majority of the design market in the West indeed doesn't need RTL; and full disclaimer: I'm a type designer with two finished but as of yet not commercially available fonts which support Arabic, so I fully understand what's at stake and feel RTL users' pain). And variable fonts being an external development, long in the making and over which Serif does not have much control, they are something third-party developers must adapt to and properly support, ASAP, and not the other way around. As I've said, the penalty can actually be people switching back to whatever software package they were using before, or to a different alternative to the proverbial 800lb gorilla in the middle of the room, just so they can stay up-to-date and competitive. The best way Serif can ensure people stay in the Affinity bandwagon for v.3 is to give them the bare essentials, and typography being the basis of design (think about it; other media and visual resources such as, say, photography or illustration can exist in standalone form, but not typography, or not to the same extent), yep, supporting the most popular formats available is as essential as being able to import and export in all popular vector and bitmap formats. Would you like being limited in what camera, or drawing tablet, or brush packs, or whatever you could buy for your creative endeavours because your supposedly very much up-to-date software package of choice refused to support them? Now extend the same exercise to something as basic as typefaces…

QuarkXPress comes in at a significantly higher price point than the entire Affinity suite, and they do not seem to fully support variable fonts yet either (though they have said it is on the roadmap for several years now).

I really want variable fonts myself, but your example is unfortunate and I am afraid doesn’t help the cause. The font of these posts is Inter, and while it is now available in variable form, this forum software is requesting the static forms from Google: <link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&display=swap" rel="stylesheet"> Edit: the above is mostly true, but it may still be delivered from Google as variable anyway (see next post). I would delete this post, but as some may have already seen it, I need to correct it instead.

Note that Affinity does not support Variable/Colour Fonts yet. – Compare this recent thread with possible workarounds:

I get that, Thomas. Even the simplest things are often significantly more complex than we think. Honestly, I’d rather see R&D budget prioritized for something important that has no workarounds like variable fonts instead of it going to on a tool like vector tracing that we can workaround doing by hand.

I had to revert back to the terrible Illustrator just because of lack of variable fonts support in Designer. I almost forgot how outdated the Illustrator really is. Sure they have this 'awesome' text-to-vector 'AI' (huge selling point to some), but the UX and the user experience is awful. Adobe even messed up the variable fonts support in the newest InDesign 2024. So yes, please, make the variable fonts possible across the Affinity Suite. Please!

It's not "one feature is unsupported". Variable fonts and Static fonts are quite different in construction. To use that font in Affinity you must uninstall the Variable versions you currently have installed, and install the Static versions instead.

I had a similar problem. I created a layout with Raleway (Google Font). I had downloaded the variable weight font file from Google. Everything displayed correctly in the Affinity Publisher app. When I went to export the PDF, it just showed regular Arial font. I deleted the variable weight font file and downloaded the individual font files from Google and restarted the app. I had to replace the fonts in my file with the new Raleway fonts and boom then it exported fine. It took about an hour of frustration before I figured this out. I hope this helps someone else.

Let me take these responses in order: 1. Variable Fonts? I don't think so. These are TTF, not OTF. 2. "No longer maintained". There are probably hundreds of thousands of fonts that are "no longer maintained." They are not operating systems. Are you suggesting that Affinity will only work with fonts that are currently being maintained? Even with some extremely old font collections, from WordPerfect 2000, MS Office 97, Lotus (1995), Harvard (1994), and the Bitstream Font CD (1993), I almost never see problems. The Libertine/Biolinum fonts are not crude fonts hacked together in someone's basement. They are fairly full-featured unicode replacements for Times New Roman and Arial, supporting many codepages, ligatures, and internal support for smallcaps, as well as other typographic features. 3. "several glyph errors throughout the font family." Are you saying that these glyphs are what is causing Affinity to choke on the italic font? Or are the glyph errors in some unicode chinese characters that are not even being used? Is this relevant to the problem being experienced? 4. "Libertine Initials and Italic have the same postscript name." Are you suggesting that opening the font in a font editor and changing the postscript name will fix the problem? 5. "...old fonts from SourceForge have errors in the name fields. That is what is most likely causing your errors." See #4 above. Are you saying that if I fix the name fields in a font editor, it will all work? This opens another question. Why is it that LibreOffice, Gimp, Inkscape, Foxit Phantom, and Abbyy FineReader have no problem with these fonts, and do not confuse the initials and the italic versions, and do not radically mess up the font kerning for the Italic face, like Affinity does, even though apparently, these two fonts (italic and initials) have the same internal postscript name. How is it that these other software avoid having this problem, but Affinity cannot avoid it? It seems to me that there is a weakness in the method that Affinity is using to identify the fonts. Wouldn't it be better to fix this? 6. "I would un-install all the G fonts." Yes, I would like to do this, but I can't, because I have many books on my website, that still have those fonts, and I eventually need to load them and replace the fonts. Some of them have carefully placed images, and if the font used does not exist on the system, it may get substituted, and the paragraphs reformat, throwing the pictures askew. To prevent having to do even more work, I keep both font series installed, do a search and replace on font format, and this way the pages and paragraphs stay pretty much the same. It's the least disruptive way (that I know of), and saves headaches. 7. "The Libertinus font family is an updated...version..." I wasn't aware of that. I have downloaded and installed it. I will tentatively experiment with it. I can't immediately jump into a font replacement without careful consideration, as I have hundreds of books, some of them over 1000 pages, that would all need to be redone, and that is probably a years work or more. So I have to move carefully. If you change the foundation on a grass hut, you can do it in one day, and change it again the next. If you have to change the foundation on a skyscraper, it requires much more thought and careful planning! I read on a wikimedia post that OTF does not display on screen as well as TTF. The post was from 2015 though, so maybe this is no longer the case? This would be a concern for me, as most of my PDF's are primarily for reading (on computer or iPad/Tablet), and only secondly for printing. I wouldn't want to compromise the reading quality. *** So I tried my test document with the "Libertine G" series of fonts and opened it in Affinity Publisher. It was even worse. See the attachment. The missing characters are one of the reasons I switched from "Libertine G" (or "Libertine O" on Linux) about 4 years ago. When I used them in the past, the G fonts looked fine in a PDF, but if you attempt to copy out the text, some PDF viewers would leave out characters, especially where ligatures were involved. I think it was Chrome and Foxit Reader that had problems, whereas Edge and Adobe Reader worked (I might be mixing these up). I also tested the same document, this time using "Libertinus". The result was successful, but interestingly, I had to choose font substitutions first (which I didn't have to do with the other Libertine/LibertineG fonts), as it could not find the original fonts (because when they are stored in PDF, somehow the name is combined without spaces (LibertinusSerifRegular) and so does not match any installed fonts. Affinity would have defaulted to Arial, but once I picked the substitutes, it worked fine.

Hi @BarbaraSki, Is the font in question static or variable? If the latter this will be because Variable fonts are not supported in Affinity apps so you would need to use a static version for the file to export correctly. Also, note that the PDF spec doesn't support variable fonts... If this is not the case, could you let us know which font is causing the issue for you?

Hi @Christopher808 and welcome to the forums. Can it be that Apple changed the font from static to variable in Sonoma? The Affinity programmes can't use variable fonts. And it seems to me that this has changed.

I see no issue with the ... replacement with the ellipsis using your Karla font (v2.002, 2020). Same in your document. It appears to work fine. It only replaced it with Arial when the Karla font was not available. I noticed you included the Karla variable fonts above. You cannot have the variable fonts installed at the same time as the static fonts. Google Fonts configures the variable fonts instance names to be same as the static fonts style names - so they conflict if both are installed at the same time. This could be your problem if you have both installed. Affinity applications can get confused by the duplicate names - with unexpected results. Such as treating a font as missing and thus replacing with another font. So if you have the variable fonts installed, un-install them. The underline is changing with the replacement font change. Fix the replacement font issue and that should fix itself. That is inside the font. The point is that how the font designer has set this may affect the vertical metrics. Wow. Basic desktop publishing knowledge appears to be lacking here. Check the docs and other DTP info sources about "leading". Affinity does not have control over the "auto" - only you and the font designer do. There are multiple settings within the fonts and they are used differently by different operating systems (and by different applications). That was the point I tried to make above. "auto" takes the default leading set by the font designer. The problem is that "default" is often calculated differently by different operating systems. So the solution is to use a fixed leading measurement which is the same no matter the OS. Your Karla font (v2.002, 2020) does have "Use typo metrics" set to On. Which means that measurement should be used on both OSs. What could be happening is that since you have "auto" set for leading when the font is replaced it is picking-up the leading from the replacement font (which is obviously different). Using a fixed leading would also fix that. So first, do not have the variable fonts installed - that may be the main problem. If that is not the issue, I am out of ideas. Note: there is a Karla v2.004, 2023 available now (but that should not affect this).

Why? For the same reason it doesn't handle Variable fonts, probably.

Hi @Komatös, thanks for responding. I'm unfortunately unable to access invidual weights. I'm not interested in variable axes. See available weights here: https://learn.microsoft.com/en-us/typography/font-list/neue-haas-grotesk-text-pro When you inspect it through Control Panel > Fonts, it appear that the font files are somehow 'linked' together. It also mentions 'Open Type Variations', which suggests that the type family might indeed be variable https://learn.microsoft.com/en-us/typography/opentype/spec/otvaroverview Shouldn't the default behaviour be to list individual weights, and not break all functionality because one feature is unsupported?

This post covers the main bug fixes that are included in 2.4.0. The fixes are organised by operating system. (A) Bug fixes which affected all platforms Rounded rectangle and standard rectangle share corner settings [AF-1628] Purple Coloration in some raw files [AF-1593] & [AF-1571] Malformed names of ICC profiles embedded in PDF-X exports [AF-1883] Failing to open .ARW file from ILCE-7M4 (A7-IV) [AF-1670] Layer Effects, 3D Effect: setting Fill Opacity to 0% doesn't turn the fill transparent [AF-1668] ASE palette file fails to import correctly, no name or colours Exporting to PDF fails when document contains a BMP with transparency [AF-751] Users TGA file opens with the wrong colours [AF-547] SVG crashing app when Opening/Placing [AF-286] Changing Language of text and updating Text Style does not remove red squiggly spellcheck lines under text in a separate frame until reopening file [AF-50] (B) Bug fixes which affected Desktop (Windows and macOS) Bounding Box shows incorrectly on a resized picture frame when using 'Lock Children' [AF-1757] TGA Export and Import is inverting a single pixel value [AF-478] Incorrect name ligature type [AF-1680] Crash when trying to export book (with lock files present for chapters) Outline FX, Fill Style > Contour: changing the Gradient Mid Point does nothing in Affinity Photo [AF-1636] Some PDF files not opening Variable text field in running header does not export to PDF [AF-1583] Crash when right-clicking a misspelt word after navigating to the spelling mistake through Preflight [AF-1489] [User File] Placing DXF file crashes Windows, creates a 0x0 size object on macOS [AF-1488] File exports with error if rasterising nothing with tagging enabled Layer States - long state names cause the UI to get pushed off Data Merge can no longer parse JSON files [AF-1429] Find and Replace panel - Fields tags remain untranslated [AF-1396] Edit Wrap Outline remains enabled when switching to the Move Tool, then back to the Node Tool without deselecting the object [AF-1344] Running headers incorrectly imported in Designer [AF-1320] Edit in Publisher errors and file closes after exporting a Password Protected PDF in Export Persona Users Docx file, Bullet points not importing [AF-1269] Scrolling Pixabay can result in a "Connection failed" message Transform Origin with multiple objects on a multipage document causes the origin point to jump around the page when moved Redraw issue in Develop persona when undoing Red eye removal tool Redraw issue in Develop persona when undoing blemish removal tool with clarity set [AF-1140] It's possible to set Show in Both Panels for character text styles [AF-740] Exporting to PDF with Endnotes set to End of Book correctly Hyperlink from note number in story text to Endnote, but not from Endnote back to note in story text [AF-709] Updating Linked resource in-app does not visually update linked file, remains as 'OK' in resource manager with no option to update Large TIFF file opens with half the design cut off and a transparent canvas [AF-630] [User File] Exporting to PDF does not complete, locks up app. Embedded PDF in file appears to be missing all data [AF-624] Overlay Paintbrush crash when holding shift after undoing Overlay Gradient Creating artboard in embedded document breaks both the embedded and parent file [AF-549] Unable to select child objects inside Open Curves with no fill [AF-464] Custom filler text is applied to all categories of English filler text [AF-372] Enable Transform Origin for 2 node line objects are offset from the object on multi-page spreads [AF-352] (C) Bugs fixed which specifically affected Windows Floating windows resize automatically incorrectly, switching between active documents continuously zooms out from canvas [AF-2005] Crash on close of application after opening a package Opening FIT/FITS files directly causes an app crash [AF-507] Manually changing the % scaling of a placed resource results in unexpected values [AF-388] Adjustment windows pop up behind floated documents instead of above [AF-335] Find and Replace Recent dropdown only displays one character from the search term [AF-1944] MS Store build crashes if when running second app if first instance is in a 'licence' screen Changing Stroke values from Context Toolbar without force committing does not apply the values until the dialog is next opened Anchor list now uses grey text, which makes entries appear disabled [AF-1685] Copy and pasting Artboard with Frame Text into Publisher converts to Artistic Text and changes text size Export Persona 'Export Options' Studio Preset list is incorrectly Centre Aligned Character Panel - 'Outline' numerical value does not update when adjusting the slider [AF-1640] Right clicking inside a text frame will trigger an app crash if the document window is floated [AF-1604] Custom filler text entrybox is too small on Windows Can't edit colours in second document palette [AF-1545] Dragging a Layer whilst auto-scrolling the Layers Studio then releasing the selection can cause the layer to be moved to a random location in the layers stack [AF-1537] States Panel: Scope label isn't level with the dropdown text Layer States: Filling the 'Layer name is' field can push the UI out the panel ALT + F4 does not close the app if a studio panel/window is actively selected [AF-1485] Locating missing resource on file load incorrectly reports them as missing in pre-flight check [AF-1471] Layer states: Toggle buttons in Light UI could do with more contrast Layer States: Hovering near a toggle button makes it change appearance States Panel: Scope is white in Light UI mode and hard to read [AF-1452] Layer States: Clicking around the Regular expressions padlock causes a scroll Add Pages from File- Page number value cannot be specified [AF-1438] Customer cannot see custom Curves Adjustments after updating to 2.3.0 [AF-1430] ASE Palettes do not import as Spot colours [AF-1428] File > New Batch Job > Add defaults Explorer to use 'Affinity Files' extensions only [AF-1426] Scrolling Mouse Wheel in New Document dialog increases value based on UI decimal settings unexpectedly Customise tools list is incorrectly labelled [AF-1421] Edit Brush icon in Brushes Studio does not function .Afbook files cannot be exported with bleed included [AF-1349] Single clicking (not dragging) a Quick Shape label will make an entry appear in the History Panel Adjusting Spiral Tool's angle sliders with 6 decimal places seems off Styles Panel: Remove Category should be Delete Category [AF-1299] My Add-ons Font filter doesn't show any results on Windows [AF-1296] Certain custom date formulas from XLSX are not importing correctly into fields [AF-1284] Crash dragging a table fixed Text Frame Panel: Stroke: None is clipped in German Renaming Nested Anchors Moves them [AF-1278] Book chapters open as read only after being printed Keyboard input should be ignored when floating dialogs are open [AF-1224] Hyperlink panel clips descenders in text Closing app with Book & Chapter documents open simultaneously prompts twice for Book Selection Brush Tool Mode icon remains on Subtract, even though the tool has reset to Add [AF-1062] Recent dialog- Pinned documents are automatically unpinned when opened [AF-951] Preflight Profile Editor cannot be resized on Windows Embedded PSD cannot be Collected or Linked, after Linking all other resources in 2 files, zooming in the document causes a hard crash [AF-722] User file - app hard crashes when undoing unit change Crash when switching between PSD export options The Font search box can expand to fill the width of the context toolbar when typing [AF-56] (D) Bugs fixed which specifically affected macOS Floating and redocking a document creates an empty floating window which cannot be closed [AF-1499] Last renamed style name is not saved, Style returns to default name on restart Text using PostScript Type 1 outline fonts are being converted to curves when exporting to PDF [AF-1387] Full screen app then close and reopen causes UI to appear behind OS menu bar and dock [AF-315] 'Normalise Breaks on copy plain text' setting does not stick on app restart [AF-1684] Layer FX- Bevel/Emboss default blend modes display the incorrect blend mode [AF-1381] Drag-dropping a masked child layer out to the parent stack without releasing the mouse button causes a crash [AF-977] Saving a file with a PSD/SVG embedded automatically switches the policy to linked when re-opening the file [AF-1416] Unable to Copy and Paste Artboard layers into Publisher Inserting a Figure Space results in a 0 being inserted [AF-1656] Find and Replace: Searching for Character Style when Scope is set to Story or Selection [AF-1609] Renaming Anchors without pressing enter after renaming can cause edited anchors to revert to old name [AF-1544] States Panel: Text labels are not clickable on macOS Crash when clicking Sync Before after enabling Noise Reduction [AF-1419] Dragging document to 2nd monitor prevents you from closing it and can display graphical issues [AF-1417] MAC Affinity Photo crashes if the windows is closed before developing a RAW file [AF-1408] Exporting to PDF from Book panel fails to generate preview Error message appears after cancelling an IAP Affinity Store linked content in My Add-ons doesn't have a white heading on macOS [AF-1297] Text doesn't reflow when adding/removing items in a group Text frame ruler flickers when adjusting the text indent on multi-column frames which span >1 page [AF-1251] Shift click not working in hyperlink panel on Mac [AF-1212] Metal Compute: Proc Tex Cell Noise functions not working [AF-1197] Place Image Panel doesn't show when drag drop multiple images while holding Option [AF-1004] Sonoma - Popup Control: Delay in Showing the Popup Updating a global colour applied to objects across multiple chapters fails to update the objects when synchronising [AF-656] Move cmd+K (Find in Layers Panel) from Misc to Layer in Shortcuts Layer States: Text labels clipped using Large Font UI Size [AF-141] Should we add an ellipsis when we purposely truncate text? (E) Bugs fixed which specifically affected iPad Adjustment Interface and Image placement menu flicker when iPad is held/Positioned at certain angles [AF-1306] Changing Resize settings breaks UI or crashes app [AF-912] Files containing SVGs crash on open [AF-1413] iPad Keyboard will show, or dialogs will close based on the angle of the iPad (seemingly accelerometer controlled?) [AF-1599] Creating/opening a file or navigating to Settings crashes app with relation to "Affinity::CloudServices::Content" [AF-612] When Find bar is left open, selecting different text and then the Find command again doesn't refresh the Find bar When editing a text style, first option in the right pane overlaps iPadOS's status bar Selecting Import Styles on the Text panel crashes the app The Edit menu's Paste commands are unexpectedly unavailable 2.2 & 2.3 files containing embedded SVGs show as missing linked resource when opened Next Style is not being applied Behaviour when placing two or more text files via drag and drop is different than Document menu > Place Affinity Windows applications include the fixes in lists (A)+(B)+(C) (A) Bugs fixes affecting All Apps + (B) Bug fixes affecting desktop Apps + (C) those fixes affecting Windows Affinity macOS applications include the fixes in lists (A)+(B)+(D) (A) Bugs fixes affecting All Apps + (B) Bug fixes affecting desktop Apps + (D) Bug fixes affecting macOS Affinity iPad applications include the fixes in list (A)+(E) (A) Bugs fixes affecting All Apps + (E) Bug fixes affecting iPads. These list are just the highlights of the many (~200) fixes made during the recent 2.4.0 beta cycle, which are listed in full in this post . If you have reported a bug and it is not yet fixed, please do not report it again. More fixes will be made in the forthcoming 2.5 beta cycle.

https://forum.affinity.serif.com/index.php?/topic/170391-variable-fonts-support/#comment-977485 @curtf add your vote in this thread if you want variable fonts which is what you want to have better font control.