Font Mark

[Daisy Hughlett]

I have a issue with sgplot. I have categorical y-axis with text values and numerical x axis. I would want to control the x-axis font size separately from the y-axis, since the x-axis font size is just fine, but my y axis values are so long that I would need to reduce the font size. So far I have found proc template the only way to even change the font sizes. However when I change the 'GraphvalueFont' value it affects both the x and y axis. The problem is that now the x-axis becomes unreadable. So is there any way to control those font sizes separately? Could I somehow initialize a new class for example GraphValueText2 or something? Or is the GTL and sgrender the way to go?

My problem is, since updating Mac to Ventura the other day some fonts in my Publisher documents are now showing Exclamation mark (!) in front of the name and Font Manager says "Unsupported characters used".
I have read some topics here about the issue, I get an idea what the problem is but can't find solution. Just to mention that before upgrade I absolutely did NOT have that issue.

Now suddenly seems like a lots of my fonts on my computer that I used before are not working properly in Affinity. I would say about 30% of fonts are now showing with Exclamation mark?!?

Any idea why is this happening, are you guys aware of the issue, are you working on an update to rectify this.

The exclamation mark indicates, as the message indicated, that you've used a character that is not present in the font. When you do that, either you'll get a "not found" symbol (often an empty rectangle) or, more usually, the character will be substituted with one from another font you have installed that does contain that character.

Could you copy and paste one of the text boxes that shows the issue into a new document and attach it here? I can check it on MacOS 12 as well as 13 and see if the behaviour is different. But as @walt.farrellhas pointed out, normally when you see this, you need to use a font that does have that character or pick a different but supported character.

Just last week I had something similar. That wasn't on Ventura but on [drum roll] El Capitan, but the basic culprit is usually the same since the early days of Mac OS X:
System font cache corruption

Onyx is a free and reliable software that has a "font cache cleaner": titanium-software.fr/en/onyx.html
Try that. Make sure to read the instructions and follow the steps exactly.

@walt.farrell thanks for reply. As mentioned I sort of understand what it means, but the thing is we did not have this problem two weeks ago, it only happened after the update. I am looking for solution. Sure I can change the font and use different but that makes it not really a solution because;-

b) all the artworks that are approved by clients that are saved, all of them will have to be re-opened, fonts in question changed and then sent to clients for another approval which is really not something one wants to go into.

I have tried Preferences>Misc>Reset Fonts in Affinity but when pressing the "Reset Fonts" button, nothing happens. Button clicks/blinks, but you don't see it doing anything. It just blinks very quickly and if that is the function that did no change anything. Issue is still here.

That's what I thought. but he says there was no problem before. so I thought he hadn't seen the exclamation mark until updated the Mac.
Affinity does not show the "fallback" fonts on Ventura.
If it's about Latin characters, it's definitely the fallback fonts problem.

Well, that would be typing the appropriate command to delete the cache files into the Terminal app. If you know what to type in there, that is.
Because that's essentially what Onyx is doing overall. All it adds is a comfortable user interface so that you don't have to type anything, just click a few buttons.

Alright. So, I'm on El Capitan, but with Damascus active, I also see the exclamation mark when selecting text. The actual text appears as Lucida Grande which is (or was? I don't know about Ventura & co.) the standard "last resort fallback font" on MacOS.

In mean time, did select few random fonts on a text, and ones that are appearing with '!' are mostly those arabic type fonts and ones with some sort of 'special characters' etc... So it could be connected with the latin vs arabic vs special characters...

Yeah, I actually set up on that mission now, to Deactivate all the fonts that I know I won't ever need to use... but of course, first five that I clicked on I got "System Fonts Selected - Fonts automatically installed by Apple are selected. These fonts cannot be deleted or deactivated."

Yeah there is going be lot of font's left that are useless, but still in Publisher as options.

Maybe an idea for Affinity to create way to disable fonts inside the Affinity. I mean if software can identify the font by putting '!' in front of it, maybe there is an "easy way" to create function in preferences "disable this font". Just an idea.

The Brand Guidelines provide the Foundation employees and partners with a system for representing the Foundation, and contains guidance on the use of official brand marks, language, photography, colours, typography, and obtaining permissions.

In the preferred version of the Mastercard Foundation signature, the corporate symbol and TM symbol appear in three process colours (Mastercard Red, Mastercard Orange, and Mastercard Yellow). The Foundation wordmark appears in one match colour (Pantone Black) on white or light-colour backgrounds, or reverses to white on black and dark-colour backgrounds.

The grayscale version is used when printing in black ink only. In the grayscale version, the brand mark appears in black and tints of black. The Foundation word mark and TM symbol appear in black on white or light-colour backgrounds. When printing on black or dark-colour background, an alternate gradient is used for the logo. The Foundation word mark and TM symbol reverse to white. Never invert the positive grayscale artwork to create the reverse version, or vice versa.

The line art version is available for special uses (e.g., one-colour printing, premium items). When printing on a white or light-colour background, the logo, word mark and TM symbol appear in black. When printing on black or dark-colour backgrounds, the corporate symbol, word mark and TM symbol reverse to white.

To ensure the signature is never compromised, it must stand alone, surrounded by a minimum free space. Nothing else may be printed in this rectangular free space. The amount of required free space is proportional to the height of the word mark. For print applications, the free space around the signature must be equal to or twice greater than the height of the Foundation word mark. For on-screen applications, the free space around the signature must be equal to or greater than the height of the Foundation word mark.

Issue: While using our machines, the font will randomly change to a series of boxed question marks or a series of As (only in a web browser) We aren't sure what the actual trigger is as Console logs don't really point to anything specific or alarming. (At least nothing out of the ordinary)

I called Apple Enterprise Support and they were puzzled as well. We provision our machines with a 10.12.6 .DMG image that is a conversion of a .app installer from the App Store. Apple Support thought it might be the image we used or something in the conversion from .app to .dmg.

Chris.Tavenner
Thanks for your response! We have the Maintenance Policy available in Self Service ONLY. It's not a policy that triggers on a check-in basis. You have to manually use it however, the specific cache policies you mentioned are indeed active. Most folks at our company don't really use Self Service all that much though which is why I'm doubtful that would have caused it. I will disable them as a precaution.

Sorry for reviving a dead thread here...but I'm curious if anyone else has seen this issue or been able to completely resolve it? This is wide spread across our district and we are in the same exact boat as amohammed.

where are fonts usually stored? when we deployed corporate fonts, we package them into the /Library/Fonts/NewFonts path.
I know some companies have licenses for fonts similar to those of the macOS font (Helvetica, etc), I would double check those conflicts and try to resolve them.

We are not currently pushing any custom fonts or anything like that. Everything font related is default. We've attempted everything amohammed put in his original post (including font validation and fixing errors/duplicates through FontBook) and as he said, it resolves it for the time being, but it always seems to come back. I originally thought this was in place upgrade related, as a number of the machines it started happening on were running Yosemite and were in place upgraded to High Sierra, but we've also seen this happen on fresh Macbook Airs from this summer that were shipped with High Sierra already installed. We also found a payload doing what Chris.Tavenner spoke on, but that has been fixed for months now, yet the issue is still wide spread.

We've had reports that an end user downloaded a heap of fonts in Word for Mac v 16.19 and this resolved the issue for them. We haven't had a chance to find out which fonts were downloaded to fix the issue, nor if this can be looked at for fleet deployment yet.

c80f0f1006