How do I get rid of false claims of using unknown characters in unknown fonts?

[JanG]

I am using Publisher in Version 2.0.4 on a Mac with a plain though formated text document generated in Word (Version 16.71). At first everything looks normal in Publisher. Yet, when i look for the checklist, I get a disturbing result. My Problem is most simply illustrated by a screen shot:

The file I am working on is using the Garamond Premier Pro font from start to bottom (Bahnschrift is a font I am using just for the footnotes in the text. the text behind the first appearance of Garamond Premier Pro in the image means in English: 'Usage of unsupported characters'. This is really strange as the word file opens and reads without any problems and the publisher file has been created from scratch with defining master pages and then importing the word file. Of course, the font is fully installed on my computer. So, what is going on here? Where does this problem come from? And how to get rid of it?

 

Furthermore I have problems with the numbering of the footnotes in the text. In the text everything looks fine. But although I have been using just the standard settings for footnotes all footnotes get an additional digit. For instance  footnote 1 in the text is numbered as 1.1 in the footnote body (s. 2. image). And this although I have tried to set the numbering to document (and book and all the other settings wide). The only thing that helps is to delete the place holder for the footnote number (#). But in this case I lose the upward positioning and size reduction of the numbering.

What is going on here? Can anybody help me?

Thanks!

[thomaso]

3 hours ago, JanG said:

unsupported characters

I wonder whether the word document contains any (possibly invisible) character which is not supported by Garamond Premier Pro. – Can you detect a specific spot in the document which has a missing character? If yes, does the Font Family field show an "!" or an "?" in front of the font name – or a warning triangle?

If not: Can you try in a smaller document:

• Copy/paste a text frame of the current document into a new test .apub
• copy all text (text tool) from the pasted text frame
• paste in a new TextEdit document (unformatted | .txt, not .rtf)
• copy/paste back into APub without having any object selected (it creates a new text frame)
• then assign Garamond Premier Pro
• preflight.

Any different result?

[walt.farrell]

Double-clicking the Preflight error message should take you to the relevant text.

[thomaso]

In addition to Walt's hint: This works to me only for a "missing character" preflight message, while a "missing font" opens the font manager window.

There I can select an "unsupported character" entry + click "Locate" which jumps to the frame with the specific text selected. Then pressing "Locate" again selects the next instance (if there is any).

[JanG]

Thanks for your help!

Unfortunately, locating the missing character does not help at all, because there is none – neither visible nor invisble. Even if I delete the whole paragraph (with some characters before and some after the critical location) from the publisher file nothing changes. The same is true if I delete the passage in Word before importing.

Somehow Word has managed to replace all fonts called 'Garamond Premier Pro' into files called "Garamond Pemr Pro'. And not even reinstallatin of the fonts changes anything. It is really frustrating.

BTW, is there a way to make command characters show up in Publisher (like it is possible in Word)?

[thomaso]

22 minutes ago, JanG said:

Unfortunately, locating the missing character does not help at all, because there is none – neither visible nor invisble.

I think APub gets the info about fonts from your layout, respectively from the Word data. What do you mean with your two mentioned "if I delete"? That an empty text frame still causes the preflight notice?

What does preflight report if you assign your available font to a new frame in a new APub document, without any text from Word?

20 minutes ago, JanG said:

BTW, is there a way to make command characters show up in Publisher (like it is possible in Word)?

Menu Text > Show Special Characters (der vorletzte Eintrag).

[kenmcd]

23 hours ago, JanG said:

Somehow Word has managed to replace all fonts called 'Garamond Premier Pro' into files called "Garamond Pemr Pro'. And not even reinstallatin of the fonts changes anything. It is really frustrating.

Word uses the "style group" family names from the fonts.
For the basic Regular, Italic, Bold, Bold Italic style group this is "Garamond Premr Pro"
Affinity and other DTP applications typically use the Typographic Family.
Which is "Garamond Premier Pro" in these fonts.
Current font development "best practices" says these should be the same.
Because it can cause issues like this.
So part of the issue is how Adopey built these fonts.

Additionally the Affinity applications do not handle the style groups properly.
Which causes problems when importing Word docs (among other things).

 

[JanG]

Thanks again for your input.

To make the font issue more clear: I opened a template for the layout (no issues) and than imported text from a word file (red warning with Garamond fonts). Next I tried to switch the font in publisher and to change the fonts in word to some well known font (Times New Roman) by searching and replacing the Garamond settings. After import to Publisher I immediately get the red warning. So something in the file seems to be strange. Unfortunately, I am not able to do a search for "Garamond Pemr Pro" as this font does not show up in the list I have to choose from.

Publisher shows the issue to be  located in the first line of the heading. So I cut it out, wrote the headline by hand again in Publisher as well as in Word. Still I get red warnings. So I cut away the full first page and replaced it (red warning). Then I opened the word file in two other programs (Pages, Libre Office), checked for issues ad exported it again as Word files. Red warnings in both cases (WTF).

So for the moment I have retired to ignoring the warnings – but I hate doing so.

Something with this file seems to be completely corrupted ...

Does anybody of you have any ideas concerning the footnote numbering?

Thanks! 

[walt.farrell]

2 hours ago, JanG said:

Does anybody of you have any ideas concerning the footnote numbering?

Can you supply a sample .afpub document that behaves this way?

[thomaso]

5 hours ago, JanG said:

Something with this file seems to be completely corrupted ...

Which one: the Word.doc or the .afpub? – Can you upload an affected word.doc?

Did you try this test via TextEdit, to possibly avoid any character that may make APub fail (hidden?) in your case?

19 hours ago, thomaso said:

Can you try in a smaller document:

• Copy/paste a text frame of the current document into a new test .apub
• copy all text (text tool) from the pasted text frame
• paste in a new TextEdit document (unformatted | .txt, not .rtf)
• copy/paste back into APub without having any object selected (it creates a new text frame)
• then assign Garamond Premier Pro
• preflight.

Any different result?

[kenmcd]

6 hours ago, JanG said:

So for the moment I have retired to ignoring the warnings – but I hate doing so.

Something with this file seems to be completely corrupted ...

It could be that APub is so confused by the font names it is simply wrong about the missing characters.

One way to check for font name confusion is to Export to PDF and closely check the text for what font is actually embedded in the PDF.

If you would be willing to test, I could make you a set of test fonts with a modified, simplified, fixed naming scheme. Same fonts, just modified so even APub can understand the names.

[kenmcd]

The Garamond Premier Pro (GPP) names were worse than I thought.
They even include an old "Mac only" name field which is the same as the Windows style group names. That is really bizarre.

To test I made a text document with all the styles (see image below).
Made the doc in LibreOffice, saved it as a DOCX, and checked it again in Word.
Then Placed the DOCX into a new APub doc.
It matched exactly ZERO fonts.
So clearly the way GPP is named has APub totally confused.

 

So I renamed the fonts to fix and simplify the way they are named.
Made four separate Typographic Families to match the style group families.
Made a test DOCX again with the newly renamed fonts (see image below).
It matched the R/I/B/BI group in each family correctly now.
But the Light, Medium, and SemiBold fonts were still all not matched.
Really bad. This should be simple the way these are named now.

These font mis-match issues are compounding any other issues.

 

[thomaso]

10 hours ago, JanG said:

After import to Publisher I immediately get the red warning. So something in the file seems to be strange. Unfortunately, I am not able to do a search for "Garamond Pemr Pro" as this font does not show up in the list I have to choose from.

Below another example for a font that causes strange missing reports in APub if used in a placed Word.doc, apparently by its various names.

While the font manager app shows different "Font" / "PostScript" / "Family" names for this two fonts, (which seem to differ in the preview in the kerning for the dot . character only) …

… Word uses different names in its font menu:

The Word.doc placed in APub creates confusion / a missing font:
(note the two font names for the not-missing font with short AND long version as name)

Also the APub font menu entries appear confusing for both fonts:

… but if re-assigned the missing status is solved:

[JanG]

Thank you all for your most valuable input again.

I am sorry that I have to ask you for some more patience as I am simply too busy to reply for the moment. Please give me a few more days. Thank you. 🙂

[JanG]

Thanks for your patience. Meanwhile I have tested the file with an Rtf-version of my Word file – And it works! Not only no corrupted fonts anymore, bu also the footnote numbering is no issue anymore. This seems to be a way to work around these problems. Thank you all for helping me.