loukash

Where do those "multiple fonts" come from? All from https://fonts.google.com/?query=Astigmatic by chance…? That's not how Unicode works. Each glyph has a unique code for a reason. This is all handled at system level. If the font doesn't provide the glyph you need, modify the font yourself. Been there done that, a few times. Been using TypeTool since many years: https://fontlab.com/font-editor/typetool. (Unfortunately on Mac it seems to be stalled at 32-bit without replacement, save for the "generous" upgrade offer to FontLab. Meh.) There's also FontForge for free as in beer, but, well, you know, open source…

"Confused" @Pšenda? Proč? The pixel preview will show you exactly how the path will look like on export. Before exporting. Which was @MPBCO's question.

My goodness, this has been requested as far back as JULY 2015!

While rebuilding a couple of my old saved presets from Photoshop CS5.5, I've actually had to resort to zooming the display (on Mac: System Preferences > Accessibility > Zoom > Use scroll gesture with modifier keys to zoom) and count the actual pixels by the quarter grid! Sheesh! In 2021?! Feels like 1995 on System 7 again…

+1000!

View menu > View Mode > Pixels or Pixels (Retina)

Horizontal center = red line Vertical center = green line

Osobně bych si nedělal příliš velké iluze, že "odpovědná osoba ze Serifu" bude rozumět tvému českému příspěvku. Mimoto "odpovědná osoba ze Serifu" už v tomto vláknu třikrát sdělila, jak se situace má. Takže dámy a pánové, což se tak při té příležitosti, než se Serif rozhoupe a případně někdy v dálné budoucnosti českou lokalizaci přidá, naopak začít učit anglicky?

No idea. I haven't seen any such setting yet. InDesign (CS5.5 here) does not substitute, but optionally it highlights the missing glyph. I, for one, would definitely expect and prefer a substitution box or highlighting instead of "silent" substitution in a "pro" layout app. Also interesting that @Celeste G's substitution displays a similar typeface, not the system font. That's either a newer feature of MacOS that's not present on my currently active El Capitan partition (note to self: check that out on Catalina!), or a feature of the font manager they're using.

So… Perhaps it's a bug, but this bug is on the designers of the Oregano font.

I'm aware of that: For the record, using Oregano TTF as downloaded from https://fonts.google.com/specimen/Oregano, but I also have a postscript-flavored OTF from another source, showing exactly the same result. The actual U+021B is being substituted with the El Capitan system font on my screenshot.

It's not: The ţ glyph in the Oregano font is a "Latin Small Letter T With Cedilla", U+0163 The ț on Romanian keyboard layout is a "Latin Small Letter T With Comma Below", U+021B There is no U+021B in Oregano. That said, after typing your text, you can substitute the missing ț with ţ by search and replace. In this font, the latter obviously looks very similar. But technically it will break a lot of language functionality like spell checking and hyphenation because it's a different Unicode character. I know similar issues from Czech where non-native writers often confuse the Czech "e caron" ě with "e breve" ĕ. They may look similar but the latter is simply wrong. That said though, back in the pre-Unicode days on "classic" Mac OS System 7 in the 1990s, I often had to resort to the breve ˘ character to manually construct Czech diacritics in PageMaker, QuarkXPress or Word with Latin-1 fonts which lacked the caron ˇ character, let alone proper combined diacritics. That was a p.i.t.a., I can tell you…

Frankly, I wouldn't have known off the top of my head how exactly to proceed either, as this kind of edits isn't something I do very often. But your example reminded me of that dog in that video…

https://affinity.serif.com/en-gb/tutorials/photo/desktop/video/334273469/

I guess those are in this file: /Applications/Affinity Designer.app/Contents/Resources/assets.propcol So you wouldn't have to delete copy those.

Well, perhaps for now you can simply remove the assets.propcol file first and see if the strange behavior stops when creating a new Assets file from scratch.

Alright, so the Assets are stored here: ~/Library/Containers/com.seriflabs.affinitydesigner/Data/Library/Application Support/user/assets.propcol Seems likely that this file is somehow corrupted. So, you may now want to copy all Assets objects to a new Designer document as a temporary storage. Then quit Designer, navigate to that file and move it somewhere else. Relaunch Designer and rebuild your assets. If it helps, then the file was the culprit and you can trash the old one. If not, hm, then possibly one of the actual asset objects within is somehow corrupted per se.

App Store or Serif Store version?

Layer menu > Expand Stroke

Either reset the pressure to have round caps on a simple path, or convert the path to outline = closed path, and use the Corner Tool to make the corners round.

That's the culprit:

https://affinity.help/publisher/English.lproj/index.html?page=pages/Assets/assets.html?title=Using assets

Can you upload the file?

https://affinity.help/designer/English.lproj/index.html?page=pages/Panels/strokePanel.html?title=Stroke panel > "Cap — Select one of the cap style buttons (Round, Butt, or Square) to vary the contour of the line end." In other words, if everything else fails, RTFM (Read The Fine Manual)

If it's on the "wrong" side, click on the Reverse Text Path button in the context toolbar.