Re: /f + /h, color box -- Re: Fix multiplot problem with epslatex terminal

[Petr M. <mi...@ph...>]

> So, the combination of `set palette defined` _and_ special-case treatment of 
> postscript causes anti-aliasing problems.

I did some tests and this proposed patch:

-"/f {rlineto fill} bind def\n",
+"/f {rlineto gsave stroke grestore fill} bind def\n",

-"/h {rlineto rlineto rlineto gsave fill grestore} bind def\n",
+"/h {rlineto rlineto rlineto gsave stroke grestore gsave fill grestore} bind def\n",

does not fix it. Try:

set pm3d map
set samples 200,200
set isosamples 100,100
splot x

set term post color; set out 'a.ps'
replot
set term pop; set out

and then you see spurious lines also with "set palette gray" or whichever 
palette you want.

Actually, it does not depend on the palette at all!!!
Put this below the current definition of /g:

/g { pop 0.5 setgray } bind def

=> you see a sputious network of lines again.


Further try this shell script to convert the postscript file to png or pdf:

a=a.ps

#A="-dTextAlphaBits=4 -dGraphicsAlphaBits=4"
#A="-dTextAlphaBits=4"
A="-dGraphicsAlphaBits=4"

# Choose either of two:
D=png16m
#D=png256

gs -q -r50 $A -sDEVICE=$D \
 	-dSAFER -dNOPAUSE -dBATCH -sOutputFile=$a.png $a -quit

ps2pdf $A $a $a.pdf

gqview $a.png


=> the output is clearly full of lines (png16m) or dots (png256). The pdf 
file does not raster at all under gs 8.5, and with empty area under gs 7.07.

So, the question is what's the simplest postscript file showing this 
behaviour? See next mail...

---
PM