kenmcd

Are the two hyphenation dictionaries the same? Did you compare them? Sounds like the ID version has been improved.

Depends on what they have done to it. An Owner password is easy to remove. A User password is not. Do you have to enter the password to even open the file to view in a PDF viewer or editor? If Yes, that means there is a User password. With a User password they may enable viewing and printing, and at the same time disable editing. When you open the PDF in Affinity it is being opened to edit. If it has an Owner password which is set to prevent editing, that is easy to remove. Some tools may be able to reset or delete the User password, once opened. I have seen the claims, but have not tested this (have not had the need to). They may also Sign or Certify the PDF which means it requires the related certificate to change or edit. I have not seen any way around these (and I've tried). (very annoying when scans of 300 year old documents are signed - so you cannot even add bookmarks) PDF viewers/editors will usually have a Security tab in the Document Properties which may show us what is in there. So a screenshot of that may be helpful. If you can print it, you should also be able to print it to a new PDF using a PDF printer.

@TheZBillDyl How many colors do you need for the fonts? It is easy to change the color palette in COLRv0 fonts (takes minutes). Affinity apps support COLRv0 fonts. And it is relatively easy to convert a monochrome font into a single-color COLRv0 font. So if you needed four colors you could have four fonts. Could you run your merge in four batches? @lacerto Any easy way to swap the font during the merge? --- Edit: Or any way to tag the incoming text so a style could be applied later?

The issue is in the font. Both the Small Caps and the Petite Caps only have the long-tail version of the Q. There is no short-tail version in either - there are no such glyphs available. So, some more odd stuff in there. I like the font. Kinda amazing what he has done with the tools being used. But it really needs a lotta love.

Those are not the names in the fonts you linked to above - which are not broken. Those are the names in one of the very broken versions I mentioned above that are also out there (which should be deleted and never used).

Cannot do this with Affinity apps. The OS keeps track of the "right" font files to use. But Affinity scans the font folders to build its font cache, so if you have duplicates installed... it causes issues like this. So, as I mentioned above, make sure you have no duplicates installed. Uninstall the fonts, then make sure there are no files for those fonts left in the fonts folders, then reinstall the fonts. You should not get any message about "a version is already installed." Shut down any Affinity apps before doing this. Then when they are restarted the Affinity font cache will be rebuilt without duplicates.

Did you shutdown and re-start Affinity? It too has to rebuild its font cache. If it still does not work, make sure you do not have multiple versions installed. And make sure there is only one file for each font - the same files should not be in your user fonts and in the system fonts. If that does not work - I am out of guesses.

That particular version appears to be OK. There are versions of Filson Pro floating around out there which are really bad. So if you had installed those first, you may need to clear your font cache. After checking them.. I installed the versions above and all are listed in Affinity Designer v2.4.1 on Win10. So they appear to be fine.

Did some testing, and it definitely does not work 100% with all Khmer fonts. But some may work. Out of the four Khmer fonts in Google Fonts, two appear to work with your test text. Different fonts use different OpenType features in different ways to create the text. So one of them may work for you now. In Affinity Publisher v2.4.1... Khmer and Konkhmer Sleokchher appear to work with that text. Noto Sans Khmer and Noto Serif Khmer did not. I also looked at the three Khmer fonts that come with Windows. None worked with that text in APub. So that Khmer font from GF may work for you for now. You will need to test more thoroughly. There may be other character sequences which do not work properly. Please let me know how your tests go with those fonts. Obviously more work needs to be done to properly support all Khmer fonts in Affinity.

Please paste your test text here. I would like to do some testing and want to be sure I have the correct characters, and in the correct order.

For me - don't know, don't care. The fonts are purposely broken junk. You should read through the longer explanation posts in the linked thread. Different applications and different operating systems have different text shapers, etc. Given the edge case here - of purposely broken multi-mapped demo fonts - I doubt the Affinity developers would prioritize this issue over many other far more important issues. Would be surprised if this gets "fixed" any time soon, if ever.

Probably the same issue (excessive multi-mapping). But I never did get a look at that particular font. It is mentioned that it is "an all caps font" so it could have the same multi-mapping to the lowercase characters like these ones. I looked at the three KC Leisure Park fonts, and many others from the same developer in a pack of their "free" fonts (61 fonts). Wadda mess. Does the same thing as the fonts in the other thread I linked to - when butchering his fonts to make the free versions, he multi-maps all the glyphs he has removed to the base character. So Aacute is mapped to A, and Agrave is mapped to A, etc., etc. Sleazy. And dumb.

@Dan C This appears to be the same issue as AF-1541. See: https://forum.affinity.serif.com/index.php?/topic/195968-font-rendered-and-exported-differently/ Another case of a font created with Fontself Maker with excessive multi-mapping. The problems with excessive multi-mapping are discussed in the above thread. So basically the problem is in the fonts. Yes, some other applications may handle this, but creating fonts like this is just dumb. Which is why Adobe strongly discourages it, and Google Fonts outright prohibits it.

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)