kenmcd

Are any of the fonts from Google Fonts color fonts? If yes, which fonts?

The OpenType setup is a bit odd. That alternate one is only an alternate of the lining figures one character. It does not appear anywhere else - which is odd. The default figures are proportional oldstyle. And that alternate one is taller, because it is for the lining figures. Normally you would have also have a shorter alternate to match the oldstyle figures. So it may look a bit odd if you do not make all the figures lining. But, you can get directly to that single character. The developer did assign Unicode code points to all alternate characters. The code points are up in the PUA (Private Use Area). That alternate one is assigned to U+E433. Another option - the lowercase dotless i looks like a one. And it looks the same height as the default oldstyle figures. It is at U+0131. This would be my choice for running text. Warning: the name fields in those fonts are big mess (looks like a bomb went off). So if you have them all installed - weird stuff may happen. Only install the exact fonts you are using (to try to avoid name conflicts). And you may avoid issues. Check your PDF output to make sure the correct fonts actually got embedded. If you have issues, and are only using a few of the fonts - I can make you a set which will work without problems.

@stokerg The Windows 11 color emoji font recently added the COLRv1 format in addition to the existing COLRv0 format (which Affinity does support currently). So it is only a matter of time now until an Affinity user asks why their color emojis do not look the same as in other Win11 apps (e.g. Word) which display the COLRv1 versions. Supporting COLRv1 would solve that issue - and this one. Please make a note to the devs in AF-2609.

This folder name will change with every version update. So your link will no longer work. The article linked directly above (by mopperle) shows how to link to a "permanent" alias link (which may or may not always work for all applications). Best solution is to un-install the store version and install the EXE version Then you will have a normal permanent link, and your other apps will work.

To answer my own question... Khmer script appears to be working in APub. I tested the Noto Sans Khmer Regular font with some GF demo text. It appeared to be shaped correctly. Not an extensive test, so there may be issues, but a Khmer expert is needed.

The variable fonts appear to have a different family name - which is normally the case with most commercial fonts - so they can be installed at the same time as the static fonts. No name conflicts expected. Google Fonts makes the variable and static family names the same (so they are interchangeable) which can lead to name conflicts if they are both installed at the same time. So in this case he should be OK with both VF and statics installed.

Depends on the font, and what OpenType features the font developer has included. What font are you using?

Oh, thanks. I installed Sonoma in a VM a couple weeks ago, but have not yet downloaded all the supplemental fonts, etc., etc. Been putting it off. In a lot of the fonts all they do is change the version number (which just appears to be a way to track back to the OS version). And apparently I missed downloading all the Ventura supplemental fonts (missed that one). So I just checked the ones from Big Sur which I did already have.

macOS Mojave 10.12 with Khmer MN.tcc v.14 (2019): Not sure what you are trying to show me here. That is confirmation that it is not working properly.

Confirmed the fonts are the problem. The style-linking is not configured properly. Both the Regular and the Bold are marked as Regular. I cannot fix them without breaking other things. The fonts are not standard OpenType, they are Apple AAT fonts. The features are in tables that are not standard OpenType (e.g. feat, morx, etc.). My tools will either delete these tables, or try to convert them to standard OpenType. Which is going to break some functionality. Note: Affinity does not support fonts like this, so these fonts are probably not going to work as expected. So you should find another font. Another thought: does the Affinity shaping engine even support the Khmer script? And it requires certain OpenType features which may not be supported. Has anyone here seen a user using Khmer?

Have Sonoma installed in a VM now, so I can check the fonts later today. Most likely the style linking is broken. Apple does that.

The version included with macOS (which version), or downloaded from some website? (where)

The Bold and Italic buttons depend on the style-linking inside the fonts. If that is not correct than those buttons may not work properly. What is the font?

Thanks. I have a bunch of them. Including those. But I have not seen one named "open barcode". I have never seen one with that name so I was curious.

Where can one download this "open barcode" font?

You can open them all in LibreOffice.

LibreOffice has a Comments feature which enables you to insert comments at a particular point in the text - and then choose whether or not these are visible (in the margin). When exporting to PDF these are not there - unless you enable LO to convert them to PDF annotations, which you can then see/or not see in the PDF reader. And you can export to .docx - which you can import to APub directly. And there is a delete-all-comments command, so you could do a save-as, and then delete all the comments.

The fonts are a mess. There are multiple duplicates in the style groups. Regular, Bold, and Book are in the same RIBBI style group. Bad. Similar errors with the Thin, ExtraLight, Black, Ultra, etc. These errors can result in the wrong font embedded in a PDF - like you have. And the weight settings are also a mess. Regular and Book are both 400. Thin and ExtraLight are both 250. Some apps use these to sort the font menu by increasing weight. So when they are duplicated things may not sort properly. So... I fixed the style groups. And set the weights sanely (Book is now 450). And changed the family name to GeomanistAF. (so you can install them at the same time as the originals, and they are not confused with the originals) They should work properly now. Will send them to you via PM. Only test I did was install them and check sorting. If you have any other odd issues, please let me know. P.S. Kinda bad selling fonts this badly broken.

Ligatures should be embedded properly with font sub-setting On. That is a bug in Affinity. They do get it correct when embedding the whole font, without sub-setting. But that is a work-around - around the Affinity bug. Other applications do this correctly with font sub-setting On.

Removing the font hinting appears to have had no effect. But, given how little I know about APhoto... Here is the modified font for testing. Renamed to: LiSuAFNH (LiSu Affinity Forum No Hinting) Note: I did not change the Chinese localized font name. So on a Chinese language system there will be a name conflict with the old font. Do not install both at the same time in that case. LiSuAFNH-Regular.ttf.zip

Interesting font. UPM is 256. It does have hinting. Cannot see much else useful - on my phone ATM. More tomorrow.

That looks like a font hinting issue. Exactly what font is that? This "隶书" translates to "clerical script" - which is a CN style of writing. So it could be one of many fonts with that in the name, or description. What exact font? What foundry? What version? A link to a page where the font is available? How big is this text in the document? I only see 8 pixels in height. You may be able to get the same effect by deleting the hinting from the font. And if that works - then to get the same effect Affinity would have to be able to disable the font hinting in addition to disabling anti-aliasing. Which may be what the other apps are doing. Without seeing the actual font, this is all just a big guess.

Yes. And you will get better language coverage and more features. And you will not have other odd issues like this. Are you going to use it for "Display", or for headings, or for text? Because there a other optical size variants which may be more suitable. This explains them all: https://en.wikipedia.org/wiki/Miller_(typeface) I think TypeNetwork sells all the variations. MyFonts only has some of them.

In this particular instance I do not think there is a quality issue with the font. The font was created by an expert. And was created to demonstrate advanced font technology. The font contains three formats: Monochrome (in the glyf table) COLRv1 (in the COLR table) Color-SVG (in the SVG table) My guess is Affinity is confused by the COLRv1. And simply does not know what to do with it, and gets stuck. COLRv0 and COLRv1 are both in the COLR table, but have different formats. My guess is it sees the COLR table, and tries to load it, and chokes on it. Many browsers support COLRv1. Some browsers only support Color-SVG. Browsers should be smart enough to use the format they do support. So that font should provide color text in most browsers. Affinity should be smart enough to not get stuck on a format it does not support.

@nDorte The Outfit font was created for the outfit brand. And it has Standard Ligatures which display its logo text. Standard Ligatures are On by default. There are Standard Ligatures for: outfitted outfitter outfit tt and more... Your "outfitted" is being turned into a single ligature glyph. Some work-arounds: In your text paragraph style turn-Off Standard Ligatures, or Highlight the text (that one word) and turn-Off Standard Ligatures, or Insert a ZWNBS between the tt (which will break the ligature). And then you will not have some odd looking tt in the middle of your text. When you changed the font on the tt you broke the ligature. Like #3 above. (be aware #3 will break search, screen readers, etc. for that word) You could also make a character style and do a search-and-replace if you have a lot of these. Note: During the GF review process I tried to stop this from being allowed. For exactly this reason. But it still got approved as-is. Bad decision by GF.