Kent Davis Posted December 13, 2024 Posted December 13, 2024 Mac can read as well and something wrong on your app for Font. Do not use Windows. I do use MacOS 15.2 and only for Mac. Should work on extension and without extension. 1. (no dot) 2. ttf 3. ttc 4. oft 5. and etc. see Designer font something wrong. Quote
Old Bruce Posted December 13, 2024 Posted December 13, 2024 23 minutes ago, Kent Davis said: Mac can read as well After a lot of thinking and re-reading your post I think I may have parsed your post correctly. Zapfdingbats do not have glyphs for the letters a-z, A-Z, etc., therefore there is a fallback font used to show what you have typed. You will need to add the Zapfdingbats using the Glyph browser. Window > Text > Glyph Browser. The Wingding and Webding fonts will use the letters to enter their glyphs. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
kenmcd Posted December 13, 2024 Posted December 13, 2024 The version of Zapf Dingbats which comes with macOS has the glyphs in the normal text locations - A-Z, a-z, 0-9, etc., etc. I just tested the Apple font (ZapfDingbats.ttf, v13.0d1e2, from macOS 14) on Win10 APub 2.5.6 and ADesigner and it all appears as expected - I see only dingbats. So something odd is going on with his ADesigner. Quote
Kent Davis Posted December 13, 2024 Author Posted December 13, 2024 Ok there font is Chicago, ZapfDingbats, Zapfino since from 1983 Mac 128, 256, 512, Plus, SE from System 1.0 to 7.xx and MacOS 8.0 many years. Quote
kenmcd Posted December 13, 2024 Posted December 13, 2024 If you look at the codes for those characters they are for normal Latin text. Such as A = the six-pointed star. You should be able to see these in ADesigner. Here is an example in APub Quote
kenmcd Posted December 13, 2024 Posted December 13, 2024 You should be able to see the same thing in ADesigner that you see in APub. I wonder if it is because the encoding is the old MacRoman (and a very old Unicode). There is no Windows encoding in that old macOS font. This is ADesigner 2.5.6 on Win 10. Same upper text with Zapf Dingbats applied is the lower text. So not sure why you are seeing the text. If you have access to the old Adobe Font Folio, the ITC Zapf Dingbats is more current Unicode - most of the characters are in the actual Unicode Dingbats block. You will need to use the Glyph Browser to select from there. Quote
Kent Davis Posted December 14, 2024 Author Posted December 14, 2024 I am not use Adobe font any more. I hate Adobe force me login appear font. When I leave logout cause font disappear. Yes its old font come from Mac never change forever. Quote
Kent Davis Posted December 14, 2024 Author Posted December 14, 2024 I will send report a ticket to Apple corp and they will work on font everything match. Thank you for share with me about that. Let's close a ticket. Quote
Oufti Posted December 14, 2024 Posted December 14, 2024 24 minutes ago, Kent Davis said: I will send report a ticket to Apple corp There is definitely something strange with this font. On my Mac, using the Apple FontBook application, when I choose Zapf Dingbats and show the standard presentation all dingbats are OK but if I choose the personalized view, all characters are missing even if I type simple ABC abc… kenmcd 1 Quote Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To I apologise for any approximations in my English. It is not my mother tongue.
kenmcd Posted December 14, 2024 Posted December 14, 2024 2 hours ago, Kent Davis said: I am not use Adobe font any more. I hate Adobe force me login appear font. When I leave logout cause font disappear. Yes its old font come from Mac never change forever. Not the online fonts, I meant the old Adobe Font Folio 11 font library which came on a CD. No subscription needed. AFF11 includes the ITC Zapf Dingbats version of the font (which is actually more modern than the version from macOS). Thought everyone has AFF11. Pretty easy to find the ISO. Quote
kenmcd Posted December 14, 2024 Posted December 14, 2024 2 hours ago, Oufti said: There is definitely something strange with this font. On my Mac, using the Apple FontBook application, when I choose Zapf Dingbats and show the standard presentation all dingbats are OK but if I choose the personalized view, all characters are missing even if I type simple ABC abc… That is very strange. Appears there is something weird going on with macOS. Seems work fine on Win10. Could be an encoding issue. The ITC version uses standard Unicode code points - so I would expect no issues. And it has cross-platform encoding. Another thought - what is the Personal View? Quote
Kent Davis Posted December 14, 2024 Author Posted December 14, 2024 Yes I agree with you. you are correct. Thank you for explain me. we can report a ticket "feedback associate.app" about that. Quote
Kent Davis Posted December 14, 2024 Author Posted December 14, 2024 Miss Character of font I notice. Quote
Oufti Posted December 14, 2024 Posted December 14, 2024 8 hours ago, kenmcd said: Another thought - what is the Personal View? Sorry, I didn't know how to say it. It's a view where you can type the characters you want to be displayed. In my 2d screenshot, I typed ABCDE… (Should be the same as the 1st screenshot (standard view) which is always displaying A…Z a…z 1…0.) kenmcd 1 Quote Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To I apologise for any approximations in my English. It is not my mother tongue.
Oufti Posted December 14, 2024 Posted December 14, 2024 19 hours ago, kenmcd said: If you look at the codes for those characters they are for normal Latin text. Such as A = the six-pointed star. Not on Mac, where the corresponding Unicode code is the appropriate (and exotic) one for that glyph: On macOS, this is a better description of what happens: 19 hours ago, Old Bruce said: Zapfdingbats do not have glyphs for the letters a-z, A-Z, etc., therefore there is a fallback font used to show what you have typed. You will need to add the Zapfdingbats using the Glyph browser. Window > Text > Glyph Browser. 19 hours ago, Old Bruce said: The Wingding and Webding fonts will use the letters to enter their glyphs. To do this on macOS, they take the G+code and assign it a private area U+code. Quote Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To I apologise for any approximations in my English. It is not my mother tongue.
Kent Davis Posted December 14, 2024 Author Posted December 14, 2024 Oh I see no problem. I did send "Feedback Assistant.app" complete. They apple corp will work on it to fix bug about font match on Macintosh. Your Affinity app is fine. Oufti 1 Quote
Oufti Posted December 14, 2024 Posted December 14, 2024 15 hours ago, kenmcd said: Could be an encoding issue. In fact, I prefer the way Zapf Dingbats behaves : for a given Unicode code, it always present the expected glyph — even if it's missing in that font. Quote Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To I apologise for any approximations in my English. It is not my mother tongue.
kenmcd Posted December 14, 2024 Posted December 14, 2024 1 hour ago, Oufti said: Not on Mac, where the corresponding Unicode code is the appropriate (and exotic) one for that glyph: That is not what is in the Zapf Dingbats 13.0d1e2 font from macOS 14. And the macOS 15 Sequoia font list still shows Zapf Dingbats 13.0d1e2. https://support.apple.com/en-us/120414 That code point above is the same as what is in the ITC Zapf Dingbats font. That font uses the actual Unicode code points in the Dingbats block. So it looks like Apple is converting the code points. IIRC we saw this same thing with another old font, which I cannot remember. Quote
kenmcd Posted December 14, 2024 Posted December 14, 2024 5 minutes ago, Oufti said: In fact, I prefer the way Zapf Dingbats behaves : for a given Unicode code, it always present the expected glyph — even if it's missing in that font. It is not the font that is doing the fall-back replacements. It is the application or the operating system. Oufti 1 Quote
Oufti Posted December 14, 2024 Posted December 14, 2024 12 minutes ago, kenmcd said: That is not what is in the Zapf Dingbats 13.0d1e2 font from macOS 14. Perhaps not when open on your computer but this very same version is the only one on my Mac, and I observed what the screenshots above show: Quote Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To I apologise for any approximations in my English. It is not my mother tongue.
kenmcd Posted December 14, 2024 Posted December 14, 2024 3 minutes ago, Oufti said: Perhaps not when open on your computer but this very same version is the only one on my Mac, and I observed what the screenshots above show: Take that font and open it a font editor. U+2721 does not exist in that font. The Star of David is at U+0041 - which is normally the uppercase A. That is in the Basic Latin block. It appears Apple is replacing the old codes in that font with the actual newer Unicode code points which are in a Dingbats block (which was probably added years after the original font was converted from Type 1). What you are seeing is not in the font. Apple is replacing the code points. Quote
Oufti Posted December 14, 2024 Posted December 14, 2024 1 hour ago, kenmcd said: Take that font and open it a font editor. U+2721 does not exist in that font. The Star of David is at U+0041 […] What you are seeing is not in the font. Apple is replacing the code points. Thank you for this explanation. I don't know how to interpret this but once again this is what I see when I open the font as suggested. Is it also because Apple replaces the code points? I'm sorry if I'm slow to understand. kenmcd 1 Quote Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To I apologise for any approximations in my English. It is not my mother tongue.
kenmcd Posted December 14, 2024 Posted December 14, 2024 1 hour ago, Oufti said: I don't know how to interpret this but once again this is what I see when I open the font as suggested. That is really strange - and not what I expected. I would not expect either Birdfont or FontGoggles to display that code point. Could you please send me the font via PM? I have not yet gone thru the pain of installing macOS 15 in a VM to get all the fonts. Gotta do that, but bleah, wadda PITA. Been putting it off. The font list shows their same fake version number, but the font may have changed. So I would really like to see the macOS 15 font. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.