LibreTraining

Ugh. Those fonts are really old. And bad. Looks like you are on Windows 10. I can send you the most current Win10 fonts via PM if you want. Glad you got it working.

This is complete nonsense. The OpenType file format is basically the old TrueType file format that they added a couple tables to so they could stuff postscript outlines into it. There is no resemblance whatsoever to the old Postscript Type 1 font structures.

This is not true. The majority (almost all) of the fonts installed with Windows are OpenType fonts with almost all having some OpenType features. Some have a lot of advanced OpenType features. The only actual old TrueType fonts are those used for some system functions (e.g. symbols.ttf), just like the old non-Unicode system fonts on the Mac (e.g. ZapfDingbats). This never-ending PS vs. TT nonsense is just that - nonsense - and it certainly should not be hijacking a discussion about OpenType features. There is ZERO difference in available OpenType features based on the kind of glyph outlines. NONE. I would be happy to point the OP to some fonts with his desired OpenType features if he will just tell us what it is that he is actually looking for.

Can you attach a PDF so we can take a look at it? If not the whole thing then perhaps 2-3 pages which demonstrate the issue.

There are tutorials out there on clearing the Windows font cache. If you are using a font manager it may also have its own font cache. And APub has its own font cache - and I have not found a way to manually delete it. Shutting-down APub and then installing/un-installing some fonts seems to trigger it to rebuild upon restarting APub. That may work. Did you test Arial-Bold export to PDF in another APub document? It could be just the APub cache. You may be able to narrow it down. I would test Arial-Bold in Export to PDF from LibreOffice or other application. If it works there it could just be the APub font cache.

I exported the test file to PDF and it looks fine. The character salad looks like font cache corruption. Note how the Arial-BoldMT Encoding says "Custom" - mine says "Identity-H" like the others. That could be another indication of font cache corruption. Does the Arial-Bold look bad in other exported PDF documents?

The OpenType features available are determined by the font designer, not by Affinity applications. Which "OpenType font feature" are you looking for?

@PeterB. In another thread discussing discussing a similar issue with ligatures I tested embedding the full font rather than just a subset. That succeeded in displaying the correct characters. So you could also try that. Another option would be to create a custom font and avoid the OpenType issues. Raleway is free and open source so we can do what we want. So let's give that a try ... Stylistic Set 01 replaced 10 characters. So I just copied those characters into the original actual Unicode locations. Fixed the side bearings. Deleted OpenType features Stylistic Alternates (salt) and Stylistic Set 01 (ss01). (so AI and ID won't try to set them, and they are not needed anyway) Changed the font name to: RalewayLogo Note: that is a Regular style - do not use any Bold buttons Installed and tested in LibreOffice. Looks OK. Give it a try: RalewayLogo.ttf You can probably set-up that in APub as a font replacement and not even have to change the original files. Let me know how it works out.

OK. I took a look at the Raleway Bold from Google Fonts. There are two OpenType features in that font affecting those characters. Stylistic Alternates (salt) and Stylistic Set 01 (ss01). Both of those features are normally Off by default. Either one will change to the characters you want. They both work the same in this case. So I am not sure how these are being forced On in AI. Should be able to disable either of them and directly insert a glyph. OpenType features settings do not survive in a PDF. So if you have editable text use the Typography panel to re-apply the OpenType features.

That is an issue with the ligatures. Which PDF Export Setting are you using? The PDF (for web) setting does not require embedding All Fonts like the other settings. In another discussion this caused an issue with the ligatures. In that case changing the default to embed All Fonts fixed the issue.

You don't mention what operating system you are using. On Windows the ScreenHunter screen capture application can record video of specific windows even if partially covered, or even minimized. Requires Aero to be On. If you are on a Mac perhaps some other screen capture apps with video capability can also do this.

No, stylistic sets should be Off by default per the OpenType specs. Some fonts will have the same glyphs in another feature like fina or calt which are On by default. Which would both do what you describe. Regardless you should be able to disable all of them. What font is it? I would like to take a look at it. Can you send it to me via PM?

What happens if rather than using an OpenType stylistic set ... you replace those three characters with the actual alternate glyphs directly (using a glyph browser)? I would expect the glyphs to survive in that case. What happens if you open the AI file in Designer, save it as a Designer file, and place that? I would expect OpenType features to be preserved in that case.

This is definitely another example of Adobe special handling to help users. They are mapping the Unicode characters in the new font to the old keys. There is no other reason those characters would appear when you type text. I realized your Mac Zapf Dingbats is a system font like some of the Windows symbol system fonts - and probably has the same kind of issues. I ran into this recently using another Windows documentation software. These old symbol fonts are not Unicode and do not work well cross-platform and on the web. On Windows they use the Wingdings font, the Symbol font, etc. to do some specific things around the operating system. That is why you cannot un-install them. When exporting documentation to different formats such as HTML (web, CHM, ePub) these symbols don't translate/port properly. They are OS specific and non-Unicode and browsers won't support them. So those specific fonts don't work and should be avoided. The documentation application created some special handling to fix these problems. Your Zapf Dingbats system font seems to have some of the same issues. My guess is it may even be a non-Unicode font like the Windows fonts I mentioned. Thus it is not a good font to use in a cross-platform publishing application. The Adobe ITC Zapf Dingbats is a current standards OpenType Unicode font. APub is handling it exactly as it was designed. With all that said, I can see how it is helpful to users to be insulated from the problems created by this situation ... helped by the GreatSatan creating this special workaround. So Affinity folks, please add another wacko font issue workaround to your ToDo list.

I checked the PDF output from APub Windows and the text font is Times New Roman. Looks like that is what you have too (or similar Times font).