JeremyTankard

Oh, sorry, I thought the comment was referring to Variable Fonts. (which can be PS as well as TT outline)

I tried from FL7 and Glyphs with no luck

It will take time as did the change from pre-OpenType to OpenType. Only now is support finally stopping (20 years on).

Obviously this needs addressing and sorting as pretty much all Affinity user base will mostly use PostScript fonts

Yes, all working. Do you mean the superiors on the last page, top few lines? I see that the OT Superscript feature which now seems to only work if the figures are set to default first. (I generally take a 'belt and braces' approach and check all the makes sense to me.) This could be how the FontCreator has interpreted (imported) the feature code and then built the TTF file. This is less of a concern to me as fonts often interpret the OT spec differently. I would push the question of how Publisher is interpreting PostScript as it builds and generates a PDF. I've not tested Designer or Photo, but I suspect they will use the same engine and so will suffer as well).

Try building Minion 3 as a .ttf (OpenType TrueType) and see if this works. I have a suspicion it is PS related and that TTF wil be OK. None of the TTF fonts I tested had the issue

What year was Minion 3 manufactered? I have been told that if I add 'nbspace' (uni 00A0) then this would avoid the problem. However I couldn't get this to work and I double encode space anyway with uni0020 and uni00A0. I noticed that the error 'kind of appeared' when two OT features are applied in combination. i.e. Oldstyle figures AND Tabular figures (mind you Minion doesn't have OS Tab figs, but the features can be turned on in the Typography panel). If you edit page one of the file I uploaded and remove everything from Tab OS figs it should all work OK.

Yes, I've replaced Regular with Medium and the error does occur. And yes it affecrts the font used across multiple pages. Any idea when this appeared in Affinity Publisher (from what version) It does appear from v1.9 onwards. Not looked at v1.8 as I can't open this document in that version.

Mind you I don't understand why it only affects the Regular font.

Was the MinionProTest font an OpenType PostScript font (.otf) and what application did you use to make this test font? Can you explain what you mean by "space characters, and control codes, and how they were multi-mapped." – is this the Unicodes – supported codepages included in the font (Mac/Windows ones) – which ones? – I'm guessing Calibri will be using Windows codepages being a .ttf and MS font and Minion will possibly have basic Windows copepage added? I'd like to see if I can build a working font as you have. This is happening with lots of fonts, I just wanted to try with an Adobe one.

Thanks Garry. I've reposted to Questions.

Is there a way to assign a colour label or other device/mechanism to a Page in Publisher? Similar to InDesign – In a long document it is usefull to be able to locate specific pages. At the moment I'm having to write down Page numbers.

Is there a way to assign a colour label or other device/mechanism to a Page in Publisher? Similar to InDesign – In a long document it is usefull to be able to locate specific pages. At the moment I'm having to write down Page numbers.

Several files are included in the attached ZIP folder. "Notes with examples.pdf" is a walk through other PDFs and .afpub files included — very keen to know what is causing this as I have little faith in making PDFs now (especially for sending to print!) AfPub PDF errors.zip

I'll sort some examples out, screen grabs and PDFs. I've spotted it in various fonts (only Regular weight). I don't think I've seen it in a .ttf font – only looked at .otf. Also only spotted it where many OpenType features are used.

Thanks Thomaso. I tried v1.9.0 to 1.9.2 with same results.

Since v 1.9.3 (Mac OS 14.10.6) I've started to notice odd spacing issues on PDFs Exported from Publisher. Sometimes a space is dropped or added. This seems to occur on a multiple page document. Exporting a single page is OK. Making the PDF via the Print command ( 'Save as / PDF') results in an OK PDF. I'm making heavy use of OpenType features and it may be to do with applying 2 or more features (i.e. Oldstyle & Tabular figures) at once, though I'm not sure – some tests I've tried seem to hint at this, others not. How can I fully uninstall Publisher and reinstall v 1.9.2 to try this one?

I'm running Affinint apps 1.9.1 release and notice that Replacing a resource in the Resource Manager has no effect. Should it? I want to swap (replace) a .afphoto to a .jpg and the only way I can seem to do it is to Place the file again and resize etc.

On a further note: In OpenType font coding the Small Cap feature (smcp) controls lowercase to small cap variants the Caps to Small Caps feature (c2sc) controls capitals to small cap varaints AND related sorts such as bracket, brace, figures, question, exclam Affinity apps list three small capital options Caps to Small Caps Small Caps All Small Caps How does Affinity see 'All Small Caps' behaving? Currently is does exactly the same as Caps to Small Caps. A font can be coded many ways and I guess the OT spec is a little abstract with regard to small cap sorts. Previously the available terms (looking at other apps here) have only listed Small Caps and All Small Caps. All Small Caps isn't a specific OT feature it is actioned by using smcp and c2sc

I'm using all 3 Affinty v1.9 desktop apps on Mac. In Photo I several layers compring images, filters and text. When I group these layers together the text layer increases in size (scales up). This also occurs in Publisher. The only way around this bug is to make a Group out of one layer and then drag the text layer(s) into that group.

Excellent. Nice and simple solution. 👍

I know it sounds daft. But the online postage from Royal Mail is an A4 PDF. I only need the top two A6 elements (the label and the customs form) to print on a 4up A4 label sheet. One option is to drop it onto my label templates (I have various templates set up for labelling). The option currently is to open it in Preview draw a white box over the bits I don't want to print and print it from Preview. But more importantly I place PDFs in Publisher quite a lot and if that PDF contains any typographic OpenType styling (small caps, fractions, swashes . . .) then these are lost. Will take a look at the 1.9 betas

Is there still no proper solution to this? It;s becoming a real pain especially having to buy postage online, download a PDF label to print out and stick. So placing the PDF in Publisher in order to crop and position for a sticky label results in major reflow of the official label. I don't know who to contact at the postal company in order for them to supply their fonts to me (sounds illegal). And placing an image is OK but another step in the process and can reduce bar code quality.

Thanks Dan, As soon as I put up the question I realised I could to that, same as sending to print – using - and , to select ranges and individual pages. I guess continuing the thought, it would be useful if there is a way to mark a spread – by colour or note (under the page number)

Whilst developing a document in Publisher I sometimes have optional page/spread layouts. Is there a way to suppress specific pages so when I Export to PDF they are not included? This would be great for client presentation review as well as general working. I looked under 'ctrl + click' / Spread Properties but there was nothing indicating such a feature or ability.