LibreTraining

IIRC enStep was one of the companies who bundled converted Type 1 fonts, and they had a habit of using all caps for the font names. If this is the JOAN font I suspect, it has the old encoding and is a pre-Unicode font. So the characters are not encoded where expected and so you see a fallback font (Arial). Here is a quick conversion to Unicode: JoanAF-Regular.zip Note: these converted Type 1 fonts are really old (1998), are limited to less that 256 characters, often have no kerning at all, and have no OpenType features.

@Anonym Rage Italic (RAGE.TTF) is installed with Microsoft Office. So any version since Office 2003 should install it (far back as I have it). You can also get it from M365 Cloud Fonts (but then you need to do Install for All Users to work).

I tested in LibreOffice and it appears they are showing the characters based on the glyph name. But what really surprised me is the text search actually worked. In early pre-Unicode Type 1 fonts the glyph name was used a lot rather than a specific code. So my guess is this is a leftover from those days when Type 1 fonts were supported. Affinity apps have never supported Type 1 fonts so there would no such leftover. That's a weird one. Hmmm ... did a little digging in the font file. And it appears to be an old Macintosh encoded TrueType file. Type 1 fonts from back then had a specific list of glyph names, and those were always in particular glyph numbers. But those numbers don't match this TrueType font. So I do not know exactly how this is working. 😵 But what I do know is these apps are using some old encoding mapping to be able to work. The glyph names is how FontCreator converts it to Unicode. And that is fairly quick and easy.

That is actually a symbol font, and all of the characters/glyphs are encoded up in the PUA (Unicode Private Use Area). So when you type something you what are seeing is a fallback font (because the characters are not there at the expected Unicode code points). Here is a quick conversion to Unicode: BadwrenchAF-Regular.zip Note: This is a really bad font. The character weights are not consistent at all. But you you should now be able to see it in AF apps.

Yes, as long as the font you choose supports Romanian. Some fonts are not localized for Romanian so be sure to check.

I have never heard of 'scaffolding' used as a term related to end-user font quality assessment. So I guess we need some clarification as to what that actually means. As mentioned already, coverage is a common end-user assessment tool. Font developers use a number of different quality assessment tools, but those would not normally be the kind of thing found in a user app. So I too am interested in what 'scaffolding' means in relation to font quality assessment.

The good thing about Fontself Maker is anyone can make a font. And the bad thing about Fontself Maker is anyone can make a font. 😁

They do - within that particular font. But the point was making is that different mono fonts will have different fixed widths. The width of Courier is different than TheSansMono Condensed, for example. So that ASCII art tool is using a particular font, which has particular horizontal and vertical metrics, and it is fitting the characters into the shape using those metrics. So to replicate the exact aspect ratio and not have a distorted art, you need the same metrics.

To look like the original, you need to use the same font and set the same line height. That way you get the same aspect ratio on each character as the original. Monospace fonts have different widths - think normal vs. semi-condensed monospace. And different vertical metrics. So you also need to set the leading/line height the same to get the same aspect ratio which was used to create the ascii art.

Yes. You are not the first to post this issue.

Affinity apps have an issue matching the fonts when the format of the PostScript Name inside the font is not "correct." The PostScript Name is what is used when the font is embedded in a PDF. I assume that is what is used in the PSD file. What you see in Font Book is the interface display name - Rock Salt The "RockSalt" - with no space - is from the PostScript Name field inside the font. So it appears that is what it is getting from the PSD file when it is opened. That PostScript Name field should be: RockSalt-Regular I looked at the actual font and the PostScript Name field in the font is: RockSalt So that is not correct, but it can be fixed. If you are able to edit the PSD file, I can make a "fixed" font to test with. Save the PSD with the fixed font. Then open the PSD in APhoto. If I am correct - it should now match the font properly. It should be able to match the font anyway. When there is only one font in a font family, the missing "-Regular" should not matter. Let me know if you want to test a fixed font. Edit: If you have access to the PSD try this: RockSaltAF-Regular.zip

Not in this case. Do you have an example where this helped with ligatures? My understanding is that only helps with the basic encoding issue. But OpenType features issues remain.

I am guessing (again) that "selected text" means you are trying to copy this text from the PDF. Affinity apps do not properly encode ligatures in PDFs. So search does not work properly, and copy/paste does not work properly. The only work-around is to disable ligatures. In the Calibri font the ti ligature is in the Standard Ligatures. So disable Standard Ligatures in the Typography panel.

Excessive use of confusing blank space is a known issue when it comes to OpenType features.

Could you please upload the APub file (or just that page? I am guessing that "Definiton" is actually "Definition" and that there is a "ti" ligature involved. What font are you using?