Skip to main content
T
thornton1-Visitor
1-Visitor
April 5, 2011
Question

Display of EPS graphics in 5.4 Editor window

  • April 5, 2011
  • 6 replies
  • 1401 views

We recently upgraded to Arbortext 5.4m80 from 5.3 at our site, and the biggest source of consternation seems to be the handling of EPS graphics in the Editor window. In 5.3, Arbortext just displayed the EPS graphic's preview image, but 5.4 tries to render the PostScript on screen. This would be a good thing, except many of EPS files make use of referenced fonts (like "Symbol"), which aren't available in Arbortext's little PostScript environment, and with the fonts missing the display of these graphics on screen is poor. I'm told the same problem affects output from Arbortext's Preview command.


Have others run into this too? PTC says to incorporate the missing fonts into the EPS graphics, but that may not be feasible. I'd settle for an option to go back to the EPS preview image, like in 5.3. Any ideas for working around this problem? (Admittedly this is only an issue for screen display in the Editor; generated PDF output is fine.)


    6 replies

    E
    ebenton1-Visitor
    1-Visitor
    April 6, 2011
    If you go to the "View" menu and de-select (un-check) the "graphics" selection, all of your graphics will just display the little circle/triangle/square graphics icon. You can hover your pointer over the icon to get a tool-tip with more metadata about the graphic.
    C
    ClayHelberg18-Opal
    18-Opal
    April 6, 2011
    Hi Michael-



    Not sure if this will work, since you said you can produce actual PDF
    output OK, but you might want to try the instructions for updating fonts
    given in help topic 22609. (Type "help 22609" on the Arbortext command
    line, or search for "Configuring Fonts for Direct PDF".) The second half
    of the topic gives instructions for updating fonts used in graphics.
    Maybe this will help out with your screen/preview issues.



    --Clay



    Clay Helberg

    Senior Consultant

    TerraXML


    P
    ptc-9533431-Visitor
    1-Visitor
    April 6, 2011
    If Clay's information doesn't work, as you suggested you can always file a
    bug report and request that they add YAV (yea another variable) to the
    preferences to restore the previouse functionality. That will get it in
    the queue, but no guarantee when that fix would be put in place.

    I'd say it is a valid request, but without more users complaining it
    probably won't get much priority.

    ..dan

    > Hi Michael-
    >
    >
    >
    > Not sure if this will work, since you said you can produce actual PDF
    > output OK, but you might want to try the instructions for updating fonts
    > given in help topic 22609. (Type "help 22609" on the Arbortext command
    > line, or search for "Configuring Fonts for Direct PDF".) The second half
    > of the topic gives instructions for updating fonts used in graphics.
    > Maybe this will help out with your screen/preview issues.
    >
    >
    >
    > --Clay
    >
    >
    >
    > Clay Helberg
    >
    > Senior Consultant
    >
    > TerraXML
    >
    >
    >
    M
    mtemple11-Visitor
    1-Visitor
    April 7, 2011

    Thanks for the tip guys - we hit the same issue here & were head-scratching for a while.


    My vote:


    set epspreview = tiffheader


    should be the default

    N
    NancyB1-Visitor
    1-Visitor
    April 7, 2011
    We have the opposite issue: the graphics display okay on screen but not in the pdf (generally these are flow chart svgs). So far, PTC hasn't been able to reproduce the issue.

    Another issue we're having is during the compose to pdf, several svgs result in "exploding" eps files of many gigabytes. Any idea why that might be happening?
    T
    thornton1-VisitorAuthor
    1-Visitor
    April 7, 2011

    We got a further reply from PTC on this, and it turns out there is an environment variable to control this. Setting APTEPSUSEPREVIEWS to "yes" does the trick.


    Thanks to everyone for the replies.


    Terms & ConditionsCookie settingsAccessibility statement