search for: setgray

...rmat, as the resulting images are inferior. Is there something I'm missing here? My current solution to the problem: editing the PostScript by hand. I am no PostScript wizard, so it is not particularly pretty. Here is what the code originally looks like: /ps 12 def /Font1 findfont 12 s 0 setgray 167.68 434.79 (..=0.05) 0 0 0 t 167.68 420.39 (..=0.005) 0 0 0 t 167.68 405.99 (..=0.0005) 0 0 0 t and here is what I've changed it to: /ps 12 def /Font1 findfont 12 s 0 setgray 167.64 317.78 (Lower Limit, = 0.05) 0 0 0 t 167.64 303.38 (Upper Limit, = 0.05) 0 0 0 t /Symbol 12 select...

...hen I last replaced ink, I only replaced the black cartridge. It didn't work, even when printing grayscale-only images, even when telling print-set-up grayscale-only. Is there a way to tell my printer to use only the black ink cartridge. My test image is a handmade postscript file that only use setgray to set the color. -- Michael hennebry at web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

hi! I would like to produce simple black and white postscript figures for publishing. A black/white or grayscale or CMYK colormodel can be used, but not RGB colours. Can I produce postscript graphs in R that satisfy this? Following an earlier advice on the help-list I have tried using Photoshop to convert - but this seems to convert the vector format into raster format - giving larger,

...t1<-c(1,2,3,4) t2<-c(4,2,4,2) plot(t1~t2, xlab="exp1", ylab="exp2") dev.copy2eps(file="test.eps") that all seems fine... until you look at the eps file created, where for some weird reason, if you scroll down to the end, the code reads: /Font1 findfont 12 s 0 setgray 214.02 18.72 (e) 0 ta -0.360 (xp1) tb gr 12.96 206.44 (e) 90 ta -0.360 (xp2) tb gr Which means, that the labels "exp1" and "exp2" get split up!?!? Now visually that doesn't matter, but I use the labels to refer to them in LaTeX using psfrag, so I have to know exactly what...

...f the file: ******************************************** 309.70 36.72 (aReallyLongStr) 0 ta 0.180 (ingT) tb -1.440 (oSeeHo) tb -0.180 (wItBreaks) tb gr 30.96 212.50 (aReallyLongStr) 90 ta 0.180 (ingT) tb -1.440 (oSeeHo) tb -0.180 (wItBreaks) tb gr 77.04 91.44 743.76 534.96 cl /Font1 findfont 12 s 0 setgray 1.03 104.76 (aReallyLongStr) 0 ta 0.180 (ingT) tb -1.440 (oSeeHo) tb -0.180 (wItBreaks) tb gr 309.70 310.10 (aReallyLongStr) 0 ta 0.180 (ingT) tb -1.440 (oSeeHo) tb -0.180 (wItBreaks) tb gr 618.36 515.43 (aReallyLongStr) 0 ta 0.180 (ingT) tb -1.440 (oSeeHo) tb -0.180 (wItBreaks) tb gr *************...

...e fails rather curiously. petal.ps <- "%!PS newpath % start a new shape 0 0 moveto % move to a start location -5 10 lineto % line to a new location -10 20 10 20 5 10 curveto % curve to a third location 5 10 lineto % line to a fourth location closepath % connect back to the start location 0 setgray % set the drawing colour to black fill % fill the current shape" cat(petal.ps, file="petal.ps") library(grImport) PostScriptTrace("petal.ps") petal <- readPicture("petal.ps.xml") grid.symbols(petal, 1:10/10, 1:10/10, size=0.1) # OK grid.symbols(petal, 1:10/1...

...lot.ps" to the same file generated with an older R in my Mac, I found one difference: $ diff -U2 oldtukeyplot.ps /Volumes/TIKKU/tukeyplot.ps --- oldtukeyplot.ps 2010-12-14 12:06:07.000000000 +0200 +++ /Volumes/TIKKU/tukeyplot.ps 2010-12-14 12:13:32.000000000 +0200 @@ -172,5 +172,5 @@ 0 setgray 0.00 setlinewidth -[ 3.00 5.00] 0 setdash +[ 0.00 0.00] 0 setdash np 660.06 91.44 m Editing the changed line to its old value "[ 3.00 5.00] 0 setdash" also fixed the problem both in Linux and in Mac. Evidently something has changed, and probably somewhere else than in plot.TukeyHSD (w...

...ppd is this: ---> snip %%Page: 1 1 %%PageBoundingBox: 0 0 612 792 %%BeginPageSetup % [{ %%BeginFeature: *PageSize Letter <</PageSize[612 792]/ImagingBBox null>>setpagedevice %%EndFeature } stopped cleartomark %%EndPageSetup gsave [0.24 0 0 -0.24 0 792] concat gsave 237 278 moveto 0 setgray (Courier-iso1252) cvn findfont 50 -50 matrix scale makefont setfont <585858582D746F2D6661782D6E756D626572> [30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 0] xshow grestore grestore showpage %%PageTrailer %%Trailer %%BoundingBox: 0 0 612 792 %%Pages: 1 <--- What this tells me is that...

.... Using HPLIP, I got a rather long-named queue that would print. The other queue, the one with the name I wanted, will accept jobs, but never finish them. > Is there a way to tell my printer to use only the black ink cartridge. > My test image is a handmade postscript file > that only use setgray to set the color. -- Michael hennebry at web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

...I only replaced the black cartridge. > It didn't work, even when printing grayscale-only images, > even when telling print-set-up grayscale-only. > Is there a way to tell my printer to use only the black ink cartridge. > My test image is a handmade postscript file > that only use setgray to set the color. Via the printer's settings options (GUI) and there should be a drop down for color options (in the past I've set color, grayscale, black). Or you could use lpoptions https://bbs.archlinux.org/viewtopic.php?pid=955786#p955786 -- ---~~.~~--- Mike // SilverTip257 //

...ing wrong? Everything works fine when using NT 4.0 SP3 clients, but we can't upgrade the NT 3.51 machines yet. Robbert. -- %!PS Robbert Heederik, heederik@wins.uva.nl, University of Amsterdam /Helvetica findfont 36 scalefont setfont 40 360 translate 1 -.05 -.05 {dup .05 le { pop 1 } if setgray 0 0 moveto (gsso9..vvv-vhmr-tu`-mk.}gddcdqhj.) { 1 add ( ) dup 0 4 3 roll put show} forall -1 .5 translate } for showpage

...t() for inputs which are atomic vectors without classes (called by pmax/pmin where applicable). pmin/pmax are now more likely to work with classed objects: they work with POSIXlt datetimes, for example. o postscript() now by default writes grey colors (including black and white) via 'setgray', which gives more widely acceptable output. There are options to write pure RGB, CMYK or gray via the new argument 'colormodel'. o rbind.data.frame() now ignores all zero-row inputs, as well as zero-column inputs (which it used to do, undocumented). This is because read.tabl...

...t() for inputs which are atomic vectors without classes (called by pmax/pmin where applicable). pmin/pmax are now more likely to work with classed objects: they work with POSIXlt datetimes, for example. o postscript() now by default writes grey colors (including black and white) via 'setgray', which gives more widely acceptable output. There are options to write pure RGB, CMYK or gray via the new argument 'colormodel'. o rbind.data.frame() now ignores all zero-row inputs, as well as zero-column inputs (which it used to do, undocumented). This is because read.tabl...