The list you are showing are not necessarily registered fonts. This list is an association between a font directive (e.g. san-serif) using in ODS styles and an actual font name (e.g. Arial). This association is in the regeistry regardless of registered fonts. The true list of registered fonts are under CORE/PRINTING/FREETYPE/FONTS. To see what I mean, search for "Albany AMT". You should get a hit under that directory. If Arial does not show up under there, you will need to get an admin to run PROC FONTREG to update the font list.
Thanks!
Dan
Is the Arial font on your system? If it is, try using PROC FONTREG to register the font to your UTF-8 configured system. Hope this helps!
Well, I'm running SAS on a server so I can't just modify the SAS registry. I ran proc registry to check which fonts were installed and this seems to be the case (duplicates removed)
MTsans-serif-unicode="Arial Unicode MS"
MTsans-serif="Arial Unicode MS"
MTsans-serif-unicode="Arial Unicode MS"
MTsans-serif="Arial Unicode MS"
MTsans-serif-unicode="Arial Unicode MS"
sans-serif="Arial Unicode MS"
sans-serif="Arial"
But the problem doesn't occur on the same server using the Wlatin1 encoding so Arial is definitely on the system. As I understand it, the UTF-8 configuration runs on the same SAS install but uses a different config.sas file. A strange and annoying problem
The list you are showing are not necessarily registered fonts. This list is an association between a font directive (e.g. san-serif) using in ODS styles and an actual font name (e.g. Arial). This association is in the regeistry regardless of registered fonts. The true list of registered fonts are under CORE/PRINTING/FREETYPE/FONTS. To see what I mean, search for "Albany AMT". You should get a hit under that directory. If Arial does not show up under there, you will need to get an admin to run PROC FONTREG to update the font list.
Thanks!
Dan
It seems PROC FONTREG does the trick. As a user, you can specify
* Add fonts to the SAS registry - avoid error Arial replaced by Albany AMT;
proc fontreg msglevel=none;
fontpath 'C:\Windows\Fonts';
run;
This will update the registry for the current session, but it only takes 0.76 seconds.
I think the SAS admin would have to add "usesashelp" and run the program with admin rights. I'll have to check that with SAS support first.
proc fontreg usesashelp;
fontpath 'C:\Windows\Fonts';
run;
Still strange that no warning occurs in a Wlatin1 session
Save $250 on SAS Innovate and get a free advance copy of the new SAS For Dummies book! Use the code "SASforDummies" to register. Don't miss out, May 6-9, in Orlando, Florida.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.