Skip to main content
E
eslotty1-Visitor
1-Visitor
December 17, 2012
Question

ASCII.scr/ASCII.fnt files.....

  • December 17, 2012
  • 7 replies
  • 2217 views
Hello gurus...



For years we ran a script to replace the ascii.src with an edited on
that added tics to the "1" and "I"... The updated file does not seem to
be working.... I'm suspecting the resulting ascii.fnt file is in a
different location for Wildfire 4. It compiles correctly (I think) and
is placing an updated ascii.fnt file in the
"C:\loadpoint\x86e_win64\text\usascii\" directory.



Thanks, and Happy Holidays (and Merry Christmas)!



GE Healthcare Technologies

Clinical Systems

Monitoring Solutions

Eric R. Slotty

Mechanical Designer

8200 W. Tower Avenue

Milwaukee, WI 53223

    7 replies

    M
    msteffke15-Moonstone
    15-Moonstone
    December 17, 2012
    We still copy ours to that location in WF5/Creo elements
    Pro(loadpoint\x86e_win64\text\usascii\). I found that for 64bit, you
    need to compile the font with a 64 bit version of Pro.
    Mark Steffke
    Engineering System Administrator
    The Delfield Company
    Manitowoc Foodservice
    T 989.775.9215 or 989.773.7981, ext 12484
    Integrity, Commitment to Stakeholders, and Passion for Excellence

    E
    eslotty1-VisitorAuthor
    1-Visitor
    December 17, 2012
    Interesting...



    Our system guy says we are running 64 bit Pro/E (WF4, M220 or M220) on
    HP Z800's.... I'm using this command to compile the font:



    "C:\loadpoint\x86e_win64\obj\compile_font.exe
    c:\loadpoint\text\usascii\ascii.src
    C:\loadpoint\x86e_win64\text\usascii\ascii.fnt"



    Does this look OK?



    Eric Slotty

    - <">mailto:->

    414-362-2552


    M
    msteffke15-Moonstone
    15-Moonstone
    December 17, 2012
    Have you seen this on the PTC KB?
    Font files get improperly compiled on Windows 64-bit. Error message in
    Pro/ENGINEER Wildfire 4.0 : Font xxxx.ndx can not be loaded
    D
    dgallup1-Visitor
    1-Visitor
    December 18, 2012

    Wouldn't it be nice if PTC would just fix their fonts? I submitted that as an enhancement request but PTC turned it down. Afraid that it would negatively affect someone. I can't see any down side to this font change myself. Perhaps if we get enough people asking for it thei will fix their fonts by 2030. Unfortuntely, world will probably end first.

    In Reply to Eric Slotty:


    Hello gurus...



    For years we ran a script to replace the ascii.src with an edited on
    that added tics to the "1" and "I"... The updated file does not seem to
    be working.... I'm suspecting the resulting ascii.fnt file is in a
    different location for Wildfire 4. It compiles correctly (I think) and
    is placing an updated ascii.fnt file in the
    "C:\loadpoint\x86e_win64\text\usascii" directory.



    Thanks, and Happy Holidays (and Merry Christmas)!



    GE Healthcare Technologies

    Clinical Systems

    Monitoring Solutions

    Eric R. Slotty

    Mechanical Designer

    8200 W. Tower Avenue

    Milwaukee, WI 53223
    T
    TimMcLellan12-Amethyst
    12-Amethyst
    December 18, 2012
    PTC could simply provide both fonts so the Customer could choose which one to use. Heck the install could simply have an option for which to use (copy the file... done).
    Tim McLellan
    Mobius Innovation and Development, Inc.
    M
    msteffke15-Moonstone
    15-Moonstone
    December 18, 2012
    Agree. From day one we have customized our font as described below,
    plus we also slash the zero. We use alpha-numberic parts, as many
    companys do. Why not eliminate any possible ambiguity while reading the
    drawings?

    Mark Steffke
    Engineering System Administrator
    The Delfield Company
    Manitowoc Foodservice
    T 989.775.9215 or 989.773.7981, ext 12484
    Integrity, Commitment to Stakeholders, and Passion for Excellence

    T
    TrainStopper12-Amethyst
    12-Amethyst
    December 18, 2012
    If they made it that easy they might have to call it SolidWorks 😉

    Regards,
    Walt Weiss
    Terms & ConditionsAccessibility statement