Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email.
We should not have to enter alt codes which are non-intuitive, must be memorized (or slow), and unstable (often font dependent):
Add Here in Creo. Could even have extended menu options.
Are we talking about font.fnt or TrueType fonts?
ALL characters are font dependent, so we need to determine which font(s) PTC will drive us to use in the future.
We have switched from font.fnt to isofont.fnt because it handles the differences between 'l' (lower L) and 'I' (upper I) and '1' (one) as well as between '0' (zero) and 'O' (upper O).
Maybe this an area that all CAD vendors could fund and develop a universal CAD drafting TrueType font that could be used by NX, CATIA, Creo, AutoCAD and others.
@BenLoosli, I think that it is a brilliant idea for CAD vendors to unite (if that is even possible!) to create a standard. However, I don't think that this necessarily relates to this idea. This idea is simply about extending the extra characters that are used in Creo. As I understand it PTC made these special characters somewhat font independent. If I am mistaken on this please correct me with details to help me understand how.
All of the font files (*.fnt) are custom files created by PTC and only useable in Creo. Any characters in these files is dependent on what PTC put in the files. The issue you get with 'special' characters is what keystroke do you use to 'call' that character from the font file?
I think the direction that PTC is headed is to do away with these out-dated font files and utilize 'industry standard' TrueType font files that are also used by Microsoft applications.
I am not sure what that implies. Are you saying that these special symbols will then take care of themselves in the TTF and OTF fonts and we will be able to use them as TTF/OTF? Or are you saying because they are going to TTF/OTF that this will be a hinderance?
I think we need PTC to chime in here and gives us a direction on where they are going with fonts and how much longer they will be supporting the font, isofont and other *.fnt files. If you look at a .src file for a font, you will see it is basically gerber pen commands of Up, Down and Move. Most of the .src files where created over 25 years ago.
Any font file used will need some alt-<char> to get a symbol as most symbols are not on a standard keyboard. There is no 'equal or less than' or 'equal or greater than' key, etc.
True Type fonts are not much different, someone had to design the character and give it an identifying character, wither a key or a special alt-<char> to find the information in the file.
@PTCModerator, can you help get us connected to the correct PTC person?
Arial is the default TTF for templates per these comments:https://community.ptc.com/t5/Creo-Parametric-Ideas/The-Number-quot-1-quot/idc-p/453389/highlight/true#M8043
Obviously Arial has some serious drawbacks. Fonts have also been discussed at the links below:
Inconsolata was mentioned as a close alternative.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.