[gs-devel] Re: [gs-cvs] rev 7133 - trunk/gs/src
Igor V. Melichev
igor.melichev at artifex.com
Tue Oct 31 02:39:36 PST 2006
Dear SaGS,
I'm not sure what happens here.
Have you got a test case when GS behaves incorrectly ?
If so, please open a bug in bugs.ghostscript.com and
attach the test case, other details and your patch to there.
Thank you.
Currently we're making an adaptation for a new
big customer within a short time frame.
Please excuse a possible temporary feature degradation.
If you observe a degradation, please open bugs.
We'll fix them as soon as possible.
Igor.
----- Original Message -----
From: "SaGS" <sags5495 at hotmail.com>
To: "gs-devel" <gs-devel at ghostscript.com>
Sent: Tuesday, October 31, 2006 11:42 AM
Subject: [gs-devel] Re: [gs-cvs] rev 7133 - trunk/gs/src
> ----- Original Message -----
> From: <stefan at ghostscript.com>
> To: <gs-cvs at ghostscript.com>
> Sent: Monday, 30 October 2006 16:54
> Subject: [gs-cvs] rev 7133 - trunk/gs/src
>
>
>> Author: stefan
>> Date: 2006-10-30 06:54:34 -0800 (Mon, 30 Oct 2006)
>> New Revision: 7133
>> ...
>> gsargs::arg_push_string changes the parsing algorithm to parse on
>> spaces. This is a side effect of changing the depth of the arg_list.
>> Currently only the postscript -c option uses this parsing scheme.
>> ...
>> + * NB: pushing args has the side effect of changing the parsing algoritm
>> to
>> + * space delimited instead of argument string delimited.
>> ...
>
> There currently is a spaces-and-quotes bug connected to
> gsargs.c::arg_push_memory_string(), the effects being that quoting is
> ignored in the 1st switch after "-c <tokens>", GS_OPTIONS, and GhostPCL
> input file names. If you are interested in a fix, and don't already have
> one, I can post a patch I created some time ago.
>
> _______________________________________________
> gs-devel mailing list
> gs-devel at ghostscript.com
> http://www.ghostscript.com/mailman/listinfo/gs-devel
>
More information about the gs-devel
mailing list