The problem with editing a font file is that now YOU have to remember to carry those files forward to your next release install as well as propogate them to all users.

We solved the issue by making isofont our default. It is a standard windows font, so nothing else is needed to use it.

You can put all the fonts you want in a library directory on your network and add the following to your config.pro or config.sup:

pro_font_dir X:\Engineering\ProE\ProE_Library\fonts (or any directory you choose)

This way you will not have to remember to add new fonts to the install directory as long as you carry over the config files.

PTC needs to fix the "font" font that they distribute with every release.  It's ridiculous to suggest that users should track down the location of the fonts in every release and recompile the font source files in every release and update the system in every release.

The 0 (zero) should have a diagonal line through it, the capital I should have horizontal bars top and bottom, the numeral 1 should have the little diagonal flag at the top.  We should not be still fixing this 30 years after the program came out.

I just went through this with Creo 4.  I had to manually compile strikethru.src even though the same strikethrough.fnt had worked just fine for years.  Then I had to track down every instance of ascii.fnt because it was not using my modified font.  Yes, PTC puts it in more than one place and was not using mine in the text\fonts folder.

While I'm complaining they should provide a strikethru font, everybody needs to be able to strike through text.  And don't tell me to use True Type fonts, not going there.