[bug-gs] No spaces allowed in separation names in /SeparationColorNames and /SeparationOrder |

[Ray Johnston]

Nikolai,

The way to create a name with spaces is to use the 'cvn' operator
on a string. For example,

<< /SeparationOrder [ /Black (PANTONE 347 C) cvn ] >>  setpagedevice

Regards,
Ray
____________________________________________________________________

Nikolai Tasev wrote:
> I am using 8.53 version of Ghostscript and trying to get separate 
> grayscale separtions for every process and spot color in a PDF file. I 
> am using the tiffsep device.
> The problem is that the separation names include spaces in them for 
> example "PANTONE 347 C". But colors are specified to Ghostscript using 
> name elements, which don't allow for separator characters such as a space:
> GSCommand:  -c "<< /SeparationOrder [ /Black /PANTONE 347 C ] >> 
> setpagedevice" -f.
> gives an error
> I tried replacing space with #hh (hex code) and /ooo (octal) as 
> specified in the PDF standard but obviously such conversion is not 
> supported by ghostscript.
> The automatic detection for spor colors works correctly and finds the 
> colors including the spaces in the names, but I can't tell ghostscript 
> which colors to render which is crucial if the pdf has more than 8 
> colors and multiple passes are needed.
>  
> Is there some workaround for this issue which is not documented? Is 
> there a particular reason for which name elements are used and not 
> strings which don't have such a problem with separators.
>  
> Thanks for any help,
> Nikolai Tasev
>  
> PS Reposting this message, I read in sourceforge forum that [xefitra] 
> has to be included in the subject. Why is this not included in the 
> welcome message when registering?
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> bug-gs mailing list
> bug-gs at ghostscript.com
> http://www.ghostscript.com/mailman/listinfo/bug-gs