LibreTraining

@bscholl There are a few other threads with similar font issues. It appears to be related to the Type 1 fonts and how they are named. See: In that case using TransType to convert the T1 fonts to OTF and update/fix the names appeared to solve the issue. Also make sure you do not have both OTF and T1 fonts installed for the same font family. That definitely causes issues. Keep in mind that Adobe has announced the end of T1 font support in Photoshop next year. The end is nearing for T1 fonts. If you would like to test convert some specific fonts to see if that is the issue, send them via PM.

@RenWaller The Crimson fonts have some odd (wrong) name fields which totally confuses LibreOffice, and APub (it appears). I created a fixed version of the fonts which work properly. See:

Yes, this has been discussed before. Many (most?) applications use the font PostScript Name as the font name in the PDF output. That name field is unique by definition and the logical choice. Some applications use the their own font name style (i.e. Calibri, Bold) in the PDF output. Which makes no sense to me, but we are stuck with it. If you have control over the original source files you can create the PDFs using a PDF printer which does use the better format. The Adobe/MS Office integration uses the PostScript name. Many of the PDF printers out there also use the PostScript name. So you can just use those to make the PDFs and then import. APub should know that Calibri, Bold should be mapped to Calibri-Bold when matching the font names. Other apps do this (you know who) as it is a common problem and a should be a relatively simple fix. Hopefully this will happen in a future version of APub.

A comparison of the space used within the PDFs by various objects. Biggest differences: images, fonts, color spaces

I too would like a detailed explanation on that. It appears that Affinity is using the metrics as designed in the font. Which means if Use Typo Metrics is Off, they use the Win metrics on Windows and the Mac metrics on Mac. If Use Typo Metrics is On, they use the Typo metrics. If I remember correctly InDesign uses the Typo metrics regardless of the settings in the font. It would be really nice to know exactly how this is done in APub.

What type of fonts are these? Are they all old PostScript Type 1 fonts? Or??? Can you provide some of the problem fonts for examination and testing? If yes, please send via PM.

It is my understanding that Affinity is producing the Affinity Publisher Workbook using Publisher. So I assume they are getting firsthand experience with the issues faced by users who produce long documents such as books. Hopefully that will accelerate the introduction of needed/required features. My interest in APub is primarily for producing long documents, so right now I too simply cannot use it. But I love what they are doing, I support them 100%, and I am rooting for them. They are making progress and I expect one day APub will have everything I (we) need.

Properly constructed TrueType fonts which are properly installed should appear in Affinity apps. What is the source of these fonts? Were these fonts bundled with some application? Are these fonts from a fonts CD or something similar? Please name some of the specific fonts which do not appear. Can you attach some of the fonts for testing? (or send via PM) In which other Windows applications do these fonts appear to work?

GreekTransOT-Regular.ttf Let me know if you have any issues with it. Good luck.

@Trevor A The Greek Trans font has the same issue as the Greekth font. Unique Font Indentifier: Monotype:Times New Roman Bold:Version 1 (Microsoft) PostScript Name: TimesNewRomanPS-BoldMT As you would surmise, the Unique Font Identifier field should be unique. Right now you have at least three fonts with this "unique" identifier. The PostScript Name is also required to be unique (otherwise wrong fonts display in the PDF output). I am concerned that there may be more non-unique fonts. If Greek Trans is the last font with this issue, disabling it should eliminate the issue. If it does, then I can fix that font and we should be good. Otherwise, if there are more non-unique fonts, we are going in circles. This happens when pasting text copied from an old non-Unicode font into a modern Unicode font/application. The character codes do not match-up and you get garbage. That may be what is happening here. There was another user here in this forum with a similar issue and using OCR was the solution in that case. OneTouch apparently uses two fonts named - PCSB GREEK and PCSB HEBREW So look for those files in your Fonts folder. I can take a look at them to see what encoding is used if you are interested. I did notice that while the Greekth and Greek Trans fonts do have Unicode encoding, at least in the Greekth font, the characters are not in the standard Unicode codes. Greekth has all the Greek characters in A-Z, and a-z code points. I guess that is to get around having to have a special keyboard. I did see some old MS tech support posts that mention a lack of support for the Microsoft Greek Polytonic keyboard in W10. Has this been fixed? Some Windows 10 fonts which do support Polytonic Greek - Palatino Linotype, Tahoma, also appears Arial, Calibri may work. Open source fonts - Cardo, Carlito, Galatia, Gentium, etc ... These should all work just fine in APub. So you are dealing with some bad fonts, and perhaps some encoding issues. Using newer fonts may solve all your issues in APub.

There could be a few different things happening. Your font cache may be corrupted. You really need to flush it. The Greek trans font may also be broken which is causing fonts cache corruption. Attach that font here and I will take a look at it. You cannot simply rename the Greekth OT font file to have a new name. Multiple name fields within the font file need to be changed. What applications are looking for the old font name? It would be really odd to have a font name hard-coded (in most cases). If some application is installing a bunch of broken fonts that is a big problem. I have seen entire groups of old fonts which are broken. In one case the Unique Font Identifier was the same in 10+ different fonts. The problem is that the font creators often only test their one font on their one application. If it works, they are done. Then someone tries to use the fonts in more advanced applications which expect the fonts to be constructed properly. You may be better off finding newer better fonts which do what you need. For example if your Greek trans is the old font from SIL, they have much newer better Greek fonts. See: https://software.sil.org/fonts/

@Trevor A Attached is a modified version of the Greekth TrueType font. Changed name to: Greekth OT (for clarity and to avoid conflicts with original font) Fixed all the name fields - no more conflicts with Times New Roman Bold. Confusing to have a single weight identified as Bold, so made it Regular. Saved it as an OpenType font, although the only feature it has is kerning. GreekthOT-Regular.ttf Should work fine now in APub, and other apps. Let me know if you have any issues.

Apparently the Greekth font was created from the old open source MS Core fonts version of Times New Roman Bold. When they did this they did not update all the name fields inside the font file. So some of the fields still say Times New Roman which is causing the confusion. This is what I found in one version ... Unique Font Indentifier: Monotype:Times New Roman Bold:Version 1 (Microsoft) PostScript Name: TimesNewRomanPS-BoldMT These errors will cause problems in the app and in the PDF output. @Trevor A If you would like, I can fix the version of the font you have so it works properly. It is open source so you can attach it here. I have found a couple different versions (both broken), but would also like to see the one you have.

These look like some really old fonts from enStep Incorporated. They were "made" around 1998 probably by converting older Type 1 fonts. These are really bad fonts. Some are pre-Unicode, some are Unicode. Pretty sure none of them have any kerning at all. Back in the late 1990's there were a number of companies just copying fonts with new names and selling libraries of fonts. That is probably what these are. You probably installed them with some other software which included a lot of bundled fonts. Also the name fields are bad in them which is probably causing some font cache corruption, and may cause PDF issues.. You should un-install them. They will be nothing but problems, and bad results. EB Garamond only has those Terminal Forms (fina) and most of the Swashes (swsh) in the Italic fonts. That is where you saw the capital T swash, etc. The regular or non-italic fonts only have a few swashes (different Q's). So that may be the confusion. APub tries to follow the OpenType recommendations as to which features are On by default. Terminal Forms (fina) is supposed to be On by default. So if you select an italic font you are going to see that alternate e at the end of a word. Some other applications may not do it that way. It also has a few Initial Forms (init) -- using an italic font type the word "wine" and look at the w.

Brain fart! But, I think the answer is sort of the same. They have to be saving those glyph numbers in the IDML file to be able call them back. ... Which is exactly what you said in your first post ...