| Summary: | pfbtopfa fails with /invalidfileaccess because it has -dSAFER | ||
|---|---|---|---|
| Product: | Ghostscript | Reporter: | William Bader <williambader> |
| Component: | Regression | Assignee: | Default assignee <ghostpdl-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | alex, williambader |
| Priority: | P4 | ||
| Version: | 9.02 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Customer: | Word Size: | --- | |
| Attachments: | proposed patch to pfbtopfa 9.02 to remove -dSAFER | ||
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? 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. |
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.