similar to: postscript printing

Hi there, If the printer is connected to a W95 box the following information may help. 1) read the shell script '/usr/local/samba/smbprint', it provides info on how to setup the configuration files 2) install ghostscript, portable bitmap utils etc 3) install 'Magicfilter', it may need all of '2)' 4) modify the (last) lines in 'smbprint' to something like: (

Paul Janzen wrote on Samba digest: > Message: 7 > To: Gerald Carter <jerry@samba.org> > Cc: samba@lists.samba.org > From: Paul Janzen <pcj@samba.sez.to> > Subject: cups raw mode, was Re: [Samba] unlink data file in cups_job_submit > Date: 21 Sep 2002 12:09:23 -0700 > > > Gerald Carter <jerry@samba.org> writes: > > > Looks right to

I have a non-PS printer setup to print under linux using ghostscript as a filter. This printer has two paper trays, one has letter paper, the other tabloid size paper. If I print from a program that uses a PPD file to configure the printer, like StarOffice or The Gimp, I can select the paper size from a nifty list. If I select letter size, the printer print with paper from the letter tray. If

--------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory Synopsis: Printing exposes system files to reading. Advisory ID: RHSA-2001:112-07 Issue date: 2001-09-24 Updated on: 2001-10-25 Product: Red Hat Linux Keywords: Ghostscript lpr LPRng printing Cross references: Obsoletes:

Well, I finally managed to setup samba printing... almost. smbprint seems well and good... if you have a postscript printer, which I don't. So, I just see stair-stepping, raw postscript on the win98 box printer I'm sending to. I've configured magicfilter to handle postscript with gs, but I'm having trouble integrating magicfilter with smbprint. I'm not much of an expert on

Well, I finally managed to setup samba printing... almost. smbprint seems well and good... if you have a postscript printer, which I don't. So, I just see stair-stepping, raw postscript on the win98 box printer I'm sending to. I've configured magicfilter to handle postscript with gs, but I'm having trouble integrating magicfilter with smbprint. I'm not much of an expert on

Full_Name: Mr. Daniel Murray Bolser Version: R 2.0.0 (2004-10-04) OS: Linux beagle 2.4.20-31.9 #1 Tue Apr 13 17:38:16 EDT 2004 i686 athlon i386 GNU/Linux Submission from: (NULL) (193.60.81.207) Trying to execute the following code produces a 'not a valid postscript' error from various postscript readers (gv, ggv, ghostscript). A very similar code works fine. <CODE> postscript()

Hello, using wine with CUPS, I have following print problem: The printer prints the plain postscript code! I don't have a Postscript printer, but on Linux Ghostscript renders the Postscript without problems. I think the Postscript file wine produes is wrong and doesn't get detected by the print filter as Postscript and so it is printed as ASCII. Can anybody help? Regards, Bernhard --

Ah, it appears that I have confused myself... I indeed have ALL of the queues defined as JetDirect with the model specific driver selected in printconf. With this combination I am telling linux to modify the job [via the filter] and then pass it as a RAW [jetdirect] where I SHOULD just have the queue define as JetDirect with a RAW as the driver and let the job go as transmitted by the client

To the plot experts: when creating a plot containing different lines, each with a special line type, it may happen that the result of 'postscript()' is not readable by ghostview (which may not be an R error, thus not bug report ;-). This is the case when mixing lty as 0:6 and character or even when using lty as character only. Example: postscript("test.ps") plot(1:10,

I discovered a little problem when using the Windows NT release of R 1.0.1, and it's still there in R 1.1.0. The boiled down version is this: I want to draw the following plot and put it into a Postscript file: x <- c(1,2,3,4); y1 <- c(1,2,3,4); y2 <- c(2,2,2,2) Fred <- c(1,2) postscript(file="d:/Bob/Papers/IFM/try2.ps") plot(x,y1, type="l")

Dear R developers and users, I have a suggestion for the postscript device driver. Now the paer= option only support "a4", "letter", "legal", "executive". I suggest we add a "user" option and letter user provide paper size, even like "595x421", width>height. For printing purpose, the provided paper size are nearly enought. But I

Dear R developers and users, I have a suggestion for the postscript device driver. Now the paer= option only support "a4", "letter", "legal", "executive". I suggest we add a "user" option and letter user provide paper size, even like "595x421", width>height. For printing purpose, the provided paper size are nearly enought. But I

Dear all, We are trying to get the Windows client to print thought postscript printers to SAMBA box, Windows apps (Words, Outlook, etc..) freeze for a long time to spool and print to SAMBA ghostscript. We have a windows 2000 PDC and using SAMBA 2.2.4. Normal SAMBA file sharing, browsing and transfers are fast. I sincerely thank you for your help. Regards Steven

hello all, when trying to produce a plot with the following code postscript("g6-5000-0705-b.ps") par(mfrow=c(4,1)) for (i in 1:4) { somc<-cumsum(betaC[,i])/c(1:N) plot(somc,ylim=c(min(somc),max(somc))); } dev.off() I get a postscript file g6-5000-0705-b.ps, but if I try to open it with ghostscript, or to convert it to pdf, I get the following error : Error: /invalidfont in

Hello, I wonder if anybody has encountered this problem? While MiKTeX/yap/Ghostscript seems to work fine on most TeX files that I have tested (including a great deal of postscript graphics), there is one file where the graphics works ok for all postscript files except one, the only one that is generated by R. I get an error "Some postscript specials could not be rendered", and the

With R 2.3.1 on Windows, I've noticed that it defaults to the "WinAsci.enc" encoding, which throws up an error when viewed with the default install of GhostScript/GSView (versions 8.51/4.7 respectively). I didn't have this problem prior to upgrading to 2.3.1 as I can view all my old PS graphs and they don't have the WinAsci encoding. I've got around this problem by

Hi Everyone, Just thought I'd pass this little snippette your way. It may help someone to get around the limitations of M$ Windoze printing. - John H Terpstra ---------- Forwarded message ---------- Date: Sat, 2 Oct 1999 17:19:08 -0700 (PDT) From: papowell@astart.com Reply-To: lprng@lprng.com To: lprng@lprng.com Subject: LPRng: RedMon - interesting program I just ran across the following

Hello, I'm currently using R-0.65.0 with --gnome option in configure on IRIX64 and Debian GNU/Linux. I found a problem in generated postscript file which has following sequence: x <- 1:30 postscript("output.ps") par(mfg=c(1,1,2,2)) plot(x,sin(x)) plot(x,sin(x)) plot(x,sin(x)) plot(x,sin(x)) dev.off() The generated postscript file "output.ps" can't

Viewing certain postscript files under R 2.13-0 is very slow, at least using GSview on my 64 bit Windows 7 system. To see this, compare how long it takes to display these two files (fast.ps was created by removing the /srgb stuff in .ps.prolog): www.milbo.org/postscript/slow.ps www.milbo.org/postscript/fast.ps The code to produce the above two files is here: