A couple of questions about fonts:
We have a company font (.RSC) that we use in V8i SS3. That font has a "number" of 1, replacing the generic "WORKING" font. When that font .RSC is now put into the MS_SYMBRSRC path, and we open a V8i drawing in CONNECT, we do not see our font at all in the font list (looking at the drop-down in the General tab of the Text Styles tool). It shows font 1 as being "WORKING". So, in order to figure out why, we've renamed ALL the .rsc files located in the MS_SYMBRSRC path with a .rscX file extension. When we re-open a drawing and invoke the Text Style tool, we can still see the "delivered" .RSC fonts - why? Where are they being read from?
How do we get CONNECT to use our font .RSC file as the "number 1" font instead of using "WORKING" as the number 1 font? We have embedded special symbols into our .RSC font, that when now opened/viewed in CONNECT, are lost because CONNECT is not using our .RSC font and is using the default WORKING font instead, which does not have the special characters...
Well - I just had a thought ! What if even though we renamed the font resource from "Font.rsc" to "Font.rscX", that maybe it was being found anyway by the "filter" of "*.rsc" as specified in MS_SYMBRSRC (we are on Windows 10). So we renamed it "Font.Xrsc" instead, and the results look much better - most of the .RSC fonts are now gone in the Text Styles tool. Now we see only these:
Still not sure where they are being read from, but this is an improvement. It still does not solve the issue of our .RSC font "1" being clobbered by the delivered font "1". Maybe the order in which it is found via MS_SYMBRSRC?
Yep - that was it. Moving our location for the font to the end of the search path has now seemingly "solved" the issue....
Answer Verified By: Bruce Reeves SRNS