Summary: | Mystery behavior for .origdefinefont, .origundefinefont, .origfindfont | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Nancy Durgin <nancy.durgin> |
Component: | Resource | Assignee: | Chris Liddell (chrisl) <chris.liddell> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chris.liddell |
Priority: | P4 | ||
Version: | master | ||
Hardware: | All | ||
OS: | All | ||
Customer: | Word Size: | --- |
Description
Nancy Durgin
2019-01-31 16:03:04 UTC
Just a note that adding a bind to the definition of /definefont in gs_fonts.ps allows the: /.origdefinefont /definefont load def line to be removed. I assume that doing the same for /undefinefont and /findfont would work similarly. This *may* be the solution, but we'd all like to understand a bit better what's going on before accepting that. Bumping over to Chris for handling -- seems like he's already had a look into it, and fonts are in his area of expertise. Of course, closing as WONTFIX seems reasonable since other than a point of confusion it doesn't seem to cause any harm (or expose any dangerous operators). |