Bug 692305 - pfbtopfa fails with /invalidfileaccess because it has -dSAFER
Summary: pfbtopfa fails with /invalidfileaccess because it has -dSAFER
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Regression (show other bugs)
Version: 9.02
Hardware: PC Linux
: P4 normal
Assignee: Default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-28 01:31 UTC by William Bader
Modified: 2011-06-29 02:11 UTC (History)
2 users (show)

See Also:
Customer:
Word Size: ---

Attachments
proposed patch to pfbtopfa 9.02 to remove -dSAFER (311 bytes, patch)
2011-06-28 01:31 UTC, William Bader 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description William Bader 2011-06-28 01:31:51 UTC 
Created attachment 7613 [details]
proposed patch to pfbtopfa 9.02 to remove -dSAFER

gs 9.00 added -dSAFER to the gs command line in pfbtopfa.
pfbtopfa needs to read and write files and fails with /invalidfileaccess.
Comment 1 William Bader 2011-06-28 03:21:21 UTC 
I think that wftopfa has the same problem, but I don't have a way to test it.

I have TrueType and OpenType fonts that I need to convert to pfa.  I've found web sites that can do it, but does gs have any way to script it?
Comment 2 Alex Cherepanov 2011-06-29 02:11:08 UTC 
The flag is removed from pfbtopfa and wftopfa scripts by the rev. c6a8de32823db74a0da27187b7fb049b337c2573

Good conversion from TrueType to PFA is rather difficult. TrueType uses a
program that does hinting and, sometimes, completely rearranges the glyph
outline. Type 1 fonts use declarative hints.

OpenType font can contain TrueType tables or CFF tables. The latter can be
converted to PFA but Ghostscript doesn't provide any tools to do this.