text in idraw gives /rangecheck errors in recent versions of ghostscript
John Heidemann <[email protected]> Fri, 27 Sep 2002 14:31:43 -0700
| Newsgroups | gmane.comp.printing.ghostscript.bugs |
|---|---|
| Message-ID | <[email protected]> |
I've had trouble with old idraw files giving the following error message in recent versions of ghostscript on Redhat Linux. I haven't been able to find any related bug reports in the ghostscript bug list. Specificially, the attached idraw file (created with idraw 1.0.6 with the text string "bar" in it), the gv the file using ghostscript-6.52-9.4 on Redhat 7.3, it gives the following error message: gs ~/NOTES/200208/idraw_failing_in_ghostscript_020808.idraw GNU Ghostscript 6.52 (2001-10-20) Copyright (C) 2001 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Loading NimbusRomNo9L-Regu font from /usr/share/fonts/default/Type1/n021003l.pfb... 2418892 1059509 1622424 328620 0 done. Loading NimbusSanL-Regu font from /usr/share/fonts/default/Type1/n019003l.pfb... 2757092 1364390 1642520 336084 0 done. Error: /rangecheck in --get-- Operand stack: --nostringval-- --nostringval-- --nostringval-- descender 0 --nostringval-- 1 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1035/1476(ro)(G)-- --dict:0/20(G)-- --dict:90/200(L)-- --dict:36/51(L)-- --dict:1/17(L)-- --dict:5/17(L)-- --dict:1/3(L)-- --dict:13/14(ro)(L)-- Current allocation mode is local Current file position is 10606 GNU Ghostscript 6.52: Unrecoverable error, exit code 1 Position 10438 is the first character of the "End" just after the "] Text" line in the file. (FYI, idraw's native file format is postscript with idraw-specific comments. This problem didn't happen on Redhat Linux 7.2, but it persists even if I downgrade ghostview in RH 7.3 to the 7.2 version (ghostscript-6.51-12). (Suggesting perhaps it's a library problem, rather than a problem directly in ghostscript.) The problem persists in rehdat 8.0 beta with ghostscript-7.05-20. (I haven't been able to test gs-7.30.) The idraw folks seemt to think this is a ghostscript bug since the idraw files that used to work no longer do. Is it possible this is a ghostscript bug? Or is it that idraw always generated bad postscript, but that ghostview just got more conservative lately? -John Heidemann