[PDF builds ignoring some kerning]

What font are you using?

You mention "OpenType styled superiors" so I assume you are using OpenType Superscripts applied from the Typography Panel, and that the font supports this OpenType feature, and the font has the proper glyphs, and actual kerning pairs for those substitute glyphs.

Not a lot of fonts have full OpenType superscript lowercase support (with substitute glyphs).
And even fewer have the full actual Unicode superscript lowercase characters.

All of these could be interacting with what Affinity is doing with the superscripts.

And if you have used the Transform panel instead, or mixed that in...

It would be helpful to see an actual document, and the resultant PDF.

[Fonts from package are not activated]

Did the correct fonts end up in the package?

The Package Fonts list only shows the family name, not the styles.
So it appears to be confused about the names at some point.
Confused when putting the fonts into the package? or
Confused when trying to get the fonts from the package?

The GT America super-family has a particular names/weights/styles configuration that may be confusing Affinity.
One of the old Bebas Neue families has a similar structure and it has been the source of some other fonts confusion issues.
And it only has five fonts, not 84.

What are the six fonts/styles you actually used?
Maybe I can try it here.
Do you have all 84 fonts installed on the source machine?

[Expanding ligatures in search]

6 hours ago, philipt18 said:

I'm sure there are some other similar ligatures, especially if you start looking at other languages and alphabets.

Most search and/or spell-check apps understand that the fi (U+FB01) single character ligature is the same as f+i - two separate characters.
And they work either way.

Same with the other legacy ligatures which have a single code point.

So your request is not that odd.
Some apps may already do this for œ etc.

Same thing happens with characters with/without the accents.
Many apps accommodate it either way.

Note: if you look in the spellcheck dictionary files used in Affinity apps you can see how they handle the ligatures.

[How to fix "missing font" when exporting publisher to PDF?]

5 hours ago, Alfred said:

Aptos is a font which is made available to Microsoft Office products, so it’s probably a ‘cloud’ font that isn’t intended to be used outside of MS Office.

Right now Aptos is Office 365 only.
You do not even get it with Office 2024 (normal install).

And being a cloud font it is not available to other applications like Affinity.
So Aptos is always going to be "missing"and will need to be replaced.

@Joansz 
They did make available a few (10) of the Aptos fonts here:
https://www.techspot.com/downloads/7566-aptos-font.html

That does not have all the styles, but it does include the Regular you appear to be using.
Those will be available in Affinity.

You may have to un-install the cloud versions or you may have name conflicts.
 

And... you can find the cloud font files, and select them all, and then right-click, and select Install for All Users.
That installs them in the normal Windows Fonts folder.
Then delete the cloud fonts folder for that family.

[placed PDF file fail to be included when exporting affinity publisher document to PDF]

@bici  What is your required format? I assume the printer has one.

The ad PDF does include transparency. So I converted it to PDF/X-1a and it looked the same.

Several of the PDF editors can convert the format.

[Affinity v2 Apps Won't Launch in Windows 10 -Fonts?]

@Pauls
Why are all fonts listed three times?
You mentioned above that there are two for "internal contexts."
I sorted the Log file by the Font Name (column 39), and cut out everything else.
Log.Font.Cache.sorted.by.Font.Name.txt

 

@demonweasel

Have you checked your Windows Fonts folder for any duplicate files?
Look for any duplicates with a number suffix (such as arial_01.ttf, etc.)

Also do you have any fonts installed in your User Fonts folder?
(not a good idea)
It can also contain duplicate font files.

[Affinity v2 Apps Won't Launch in Windows 10 -Fonts?]

4 hours ago, walt.farrell said:

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.

Cascadia Mono variable is two font files (which are style-linked).
So what you are seeing is the default master name for each style weight.
Regular × six weights.
Italic × six weights.

Sitka is now variable in Windows 11.
The instances are organized by six optical sizes.
And each optical size includes three weights (so 6 × 3 = 18 total).
Plus the Italic font is style-linked.
Again you see the name of the default master.
So...
18 × Text
18 × Text Italic

Segoe UI Variable is only roman, no italic.
Three optical sizes.
Five weights.
3 × 5 = 15 of the default master - Regular

[placed PDF file fail to be included when exporting affinity publisher document to PDF]

It would help to see the v1.4 PDF if possible.
Then we could take a look at what is actually in there.

 

[Fonts not working]

On 11/29/2023 at 11:59 PM, whatmedia said:

I’m still having this problem: Installed font not showing in font picker.

I Installed font (Bebas) through designer>settings>font and also tried with iFont app. Font works in Procreate and Pages.

Which version of Bebas Neue?
And where did you get it?

There are a few different versions of the Bebas Neue family out there.
And some of them are configured rather oddly.
So I wonder if that odd configuration is confusing Affinity.
(I have seen other issues where Affinity showed nothing in the font list)

I have a version which has been "fixed" if you would like to test those.
(then we would know if this is actually the issue)

 

[full font family not showing up after upgrade to Mac OS Sonoma]

Marion is now an Apple "Document-support Font" in Sonoma.
See: https://support.apple.com/en-me/HT213773#document

Quote

These fonts are available only to documents that already use the font, or to apps that request the font by name. Some are older fonts that were included with earlier versions of macOS or Apple apps.

Affinity does not support these Apple font controls.

The Marion.ttc file previously included with macOS only had three styles.
Regular, Italic, and Bold.
Since you also have BoldItalic we can assume you actually own the full font family.

So Apple in their unbelievable arrogance are blocking fonts you actually own.

The only solution is to change the name of the fonts.
(the commercial fonts available from MyFonts, etc. have the same names).

There was a previous discussion about the Marion fonts, and changing the name.

 

[font compatibility problem on Affinity publisher]

Moving between macOS and Windows can cause line height issues (depending on the font), but usually the same OS should not be an issue.

Can you post a PDF or image of how it looks on both systems?

I assume Helvetica is the one included with macOS?

And Blenda Script from Dafont? (or some other free font site)

Which version of Ubuntu?

[font compatibility problem on Affinity publisher]

3 hours ago, Sandy5767 said:

Font formatting jumps.

I assume that means there is some difference in the line height
which can cause reflow and fit issues.

What font?

Is macOS on both systems?
And is it the same version?

Generally setting a fixed leading (line height) can avoid this.
(and you should have the same version of the font)

 

[Text spacing issues.]

This looks like text that came from a PDF.
Where the tracking is all messed-up by APub guessing at the spacing.
(which is made harder if the text was justified or had tracking applied)
And some space characters are missing or extras (which appears after fixing the tracking).

The fix in the previous cases has been:
- select all the text and set the tracking to 0
- delete double spaces or add needed actual spaces
- delete extra paragraph breaks, or line breaks

 

[Font weights unavailable in Windows app (TTF)]

8 minutes ago, yashbutno said:

I hope Microsoft still makes it available through some means. Will look more into it.

Also, if you have access to Office 365 you can probably coax it into giving you the static versions from the cloud fonts.
Worked with Bahnschrift.

[Font weights unavailable in Windows app (TTF)]

This font family was changed to variable with Windows 11.

If you have access to a Windows 10 system, these fonts are static versions.
Included with the Windows 10 Pan-European Supplemental Fonts Pack.
But it only has 6 styles vs. the 16 style instances in the variable fonts.

https://learn.microsoft.com/en-us/typography/fonts/windows_10_font_list#-pan-european-supplemental-fonts

 

[U&lc bug: PDF export from Publisher 2.3.1 -> import Photo 2.3.1]

@Mark Favreau

I tested WildWords and it does work.
Re-opening the PDF in Affinity looks correct.
But only because the font has uppercase glyphs in both the uppercase and lowercase code points.

I tested text that is:
- All Uppercase
- Uppercase and Lowercase
- Upper and Lowercase - with All Caps applied.

The actual text codes for the text in the re-opened PDF are:

WildWords (not WildWords Lower)

All Uppercase
CONnECtED

Uppercase and Lowercase
ConNecTed

Upper and Lowercase - with All Caps applied
CONnECtED

But it still looks the same because of the font:

 

@AdamW
The substitutions are done differently in the WildWords font,
but there are still quite a few errors in the embedded text (or ToUnicode table).

[Font Rendering Issues]

Playball has Positional Alternates which Affinity has set to On by default.
Other applications set these to Off by default for Latin script.
Which is why other applications do not have this problem.

In the Typography Panel find the Positional Alternates section and turn those Off.
Playball has Initial Forms (init), Final Forms (fina), and Isolated Forms (isol).

[U&lc bug: PDF export from Publisher 2.3.1 -> import Photo 2.3.1]

4 hours ago, Hangman said:

@kenmcd,

Out of pure interest, why do all (at least the several I’ve tried) PDF Readers display the respective CC Wildnames Lowercase ligatures ‘correctly’?

PDF Readers just display the shape that is there for that text object.
Which is exactly what they are supposed to do.
Show me the shapes.

The shape that is placed in the PDF (and connected to the Unicode code point) can vary based on the OpenType features applied.
For example you could apply the swash feature to the T in The and OpenType will substitute an alternate big swashy T glyph (shape) for the original plain T glyph (if the font has this OpenType feature).
That swashy T shape is what gets embedded in the PDF.
The underlying Unicode code point remains the same.
So if you copy and paste that swashy text you will still get "The".

When Affinity opens a PDF it is opened for editing, so for text objects it reads the underlying Unicode code point, and then goes to the font to get the character (and the normal shape associated with that character).
Since there is no OpenType feature applied to that text, you see the normal shape.

Same thing happens with small caps.
The underlying character code point remains the lowercase character.
If you copy-and-paste small caps from a PDF, you will get lowercase text.

So what shape gets embedded/displayed in the PDF can be multiple different alternate shapes - for one same Unicode code point.

In this case the characters should have all been converted to uppercase code points - but for one character it displays/embeds the "correct" uppercase glyph (shape), but applies/embeds the lowercase code point.
Something is not working correctly.
My guess is that there is some odd interaction between the All Caps feature and the OpenType ligatures.

Make sense?

[U&lc bug: PDF export from Publisher 2.3.1 -> import Photo 2.3.1]

@Mark Favreau
You could use the CC WildNames font (not CC WildNames Lowercase).
It is all caps and the ligatures/alternates are handled differently.
The lowercase is all caps also, but the shapes are different from the uppercase.
And the OpenType code for the alternates works differently.
The substitutions are between the uppercase and lowercase versions,
not with any oddly named ligatures.

That font may work-around these issues.

[U&lc bug: PDF export from Publisher 2.3.1 -> import Photo 2.3.1]

42 minutes ago, walt.farrell said:

So this isn't the usual Affinity issue that occurs with ligatures when the Export uses font subsetting?

No, does not appear to be.
In those cases it is completely off (like the character mapping is off).

In this case it appears to be some weird interaction between the All Caps function and the OpenType replacements - and those ligature names.
My WAG is some code does not play well with those glyph names.

[U&lc bug: PDF export from Publisher 2.3.1 -> import Photo 2.3.1]

The error is in the creation of the PDF from APub.

CC WildWords Lower has ligatures for uppercase characters when there are two of the same character next to each other.
Like: CONNECTING
The NN is replaced by a ligature in which the two Ns look slightly different.
The name of that ligature is n_N.
All of the ligatures are named like that. a_A, b_B, c_C, etc.
This appears to be confusing APub.

Note: these are Standard Ligatures (liga) so they are On by default.

APub should embed in the PDF two uppercase characters.
But the code behind the first character is instead for the lowercase character.
It is embedding the Unicode for: COnNECTING
When opened in APhoto for editing it displays that lowercase character.

So the fix has to be in how APub creates the PDF.

Work-arounds...
Actually convert it to uppercase - but you will lose the pseudo-random characters.
Turn-Off Standard Ligatures - but you will lose the pseudo-random characters.
Place the PDF as pass-through.
Convert the PDF to curves.

 

[Affinity Designer 2.3.1 always complains about missing fonts]

53 minutes ago, deepblue said:

The font used is Myriad Pro. Unfortunately, when I open the document in Affinity, I always get the message that the document is missing the Myriad Pro Light font. If I check and check that in the MacOS 14.3 font collection, everything is fine. What could be the reason?

Did you happen to use the Myriad Pro Semibold style?
The Light and Semibold styles are in an R/I/B/BI style group together,
and Affinity applications do not handle style groups correctly.
So it could simply be confused (annoyingly).

What Myriad Pro styles did you actually use in the document?
Would it be possible to post the document so we can take a look?

You could do as @walt.farrell suggested and open the doc in APub
and see if you can find where that font is used.

To test, you could also remove all the fonts you are not using, leaving installed only the fonts actually used, and see if the error goes away.
That would confirm that the application is simply confused.

Nothing wrong with the fonts.
Affinity apps just do not know how to handle style groups correctly.

[How to open a PDF and keep the original letter shapes?]

47 minutes ago, thinsoldier said:

I need to open a pdf from the government and increase contrast so it will print properly on a dodgy black and white laser printer and add one line of text and a photo but every Affinity app changes the fonts!

What is the cause of the contrast issue? Is the text gray or a color?
You can use GhostScript (free) to convert all the text to black.
Or is there a background or something else?
Can you attach the PDF file?

You may be able to make the text black, place the PDF as pass-through,
and then add your text and image on top.

[Placed PDFs disappear (Publisher on Windows)]

1 hour ago, David Still said:

If a page has already disappeared, then I can't remove the background rectangle. After embedding the file and double klicking it to enter edit mode, the missing page is just a small square with no contents at all in the layers panel (see screen shot above). But if I remove the white background before the page disappears (i.e. directly after placing the document, but before saving and reopening), it seems to fix the issue (at least so far), so that still points to the background being at least part of the problem.

No, I meant removing it from the originals before placing them.

Note: I examined the original PDF and removed the background shape using
PDF-XChange Pro. So I also recommend that application.

[Placed PDFs disappear (Publisher on Windows)]

1 hour ago, David Still said:

That's when I discovered that if I edit an embedded PDF that has a page missing (by double clicking it) the missing page in the edit view really is missing - it has no contents in the layers panel, and the size is just a tiny square. See attached screenshot. I don't know if that tells us anything.

It may. I remember a previous issue where APub confused the stacking of the objects in a PDF, and then just showed the blank area. IIRC the thinking was if all of this is hidden it does not need to be shown or even processed so APub appeared to just drop it (it is not visible why even deal with it).

You can test this by removing that shape from some more of the other missing-pages PDFs and see if they also now show correctly. If every one you remove the shape from now shows correctly that would be pretty good evidence that is the issue.