limitcheck due to Japanese characters.
- From: kmullin@xxxxxxxxxx
- Date: Mon, 12 Nov 2007 15:03:27 -0800
I have a postscript file that has a lot of these statements:
/JPString (#$@#$) def
(Those strange characters are actually japanese, which I can't copy
paste into this very well)
I get this error when I try this.
Error: /limitcheck in -file-
Operand stack:
JPLiquidationInformation
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--
Dictionary stack:
--dict:1052/1123(ro)(G)-- --dict:0/20(G)-- --dict:
104/200(L)-- --dict:11/26(L)-- --dict:11/14(ro)(L)-- --dict:
51/53(L)-- --dict:6/10(L)-- --dict:96/100(L)-- --dict:
216/257(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 238753
GNU Ghostscript 7.05: Unrecoverable error, exit code 1
and the offset this is reporting, 238753, is nowheres near my code.
If I comment the line out, it runs, it has othere errors because it
can't find JPString, but thats expected.
What is this 'limitcheck' error? In my copy of the Postscript
Reference Manual, it talks about exceeding integer sizes, or real
sizes, or number of gsaves, but I'm not doing any of that. I can only
speculate that it doesn't like the japanese characters, but I have
other postscript files where it works. Can somebody see my problem?
.
- Follow-Ups:
- Re: limitcheck due to Japanese characters.
- From: Alex Cherepanov
- Re: limitcheck due to Japanese characters.
- From: Aandi Inston
- Re: limitcheck due to Japanese characters.
- Prev by Date: Re: Ghostscript file creation
- Next by Date: Re: limitcheck due to Japanese characters.
- Previous by thread: NEW -> typesetterforum.com
- Next by thread: Re: limitcheck due to Japanese characters.
- Index(es):
Relevant Pages
|
|