similar to: PostScript printing to a file?

I had located and installed wine via rpm only to discover that I needed to compile from source to get --with-opengl. Fine. The documentation with the source is written in sgml. Turns out sgml, specifically Mozaic, died on the vine thirty years ago, replaced by xml, sort of. Mozilla doesn't open sgml. A search suggested Netscape might. Curious. So I installed 7.2. It doesn't

Alvaro, The Postscript output from R will produce output as good as your printer. It is best to have a printer with a Postscript interpreter built in, as the software conversions often found in Windows printer drivers can be pretty wobbly. One advantage of R Postscript is that it doesn't tack a Postscript reset (^D) on the end of every file. As for word processors which handle Postscript

I'm having trouble printing to a HP LaserJet 6MP Postscript printer. I'm using CUPS and normal UNIX printing works fine. I've tried to configure SAMBA for point and click printing. That all seemed to go okay except that what is printed is: ===================================================== -12345X@PJL JOB @PJL SET RESOLUTION = 600 @PJL SET ECONOMODE = OFF @PJL ENTER LANGUAGE =

Hello: I have a machine running Fedora Core 2 with an HP Color LaserJet 2550L printer connected via a USB cable. Local printing from the fedora machine is just fine. It uses CUPS. I am trying to set this printer up using Samba, but I keep getting postscript code when I try to print from Windows. Here is my smb.conf file: [global] log file = /var/log/samba/%m.log load printers =

I've searched both the archives and dejanews, to no avail. I'm trying to get a hp 4mp (PostScript) print out sane output. I've got a old machine running Red Hat Linux, hooked up to the 4MP. The printcap prints up postscript just fine. I make the printer a share, tell it that the printer is postscript, then go to the win98 box, choose the HP 4MP driver and try printing and get

Hi there, For postscript printing, if the print server is on a Linux (Unix) box, I've very good experiences with 'MagicFilter'. This turns your spooler into a universal and flexible printer. Of course for postscript you need to have Ghostscript installed... Kees

I've run into another postscript/rpart problem unrelated to the issues I've mentioned in a previous query. I'm using 1.3.1 on a Win2K box. >plotcp(some.rpart.object) draws a very nice plot on the windows graphic device. If I save this as a postscript file, either by opening a postscript device before calling plotcp, or by saving the graphics window as a postscript file, the

Dear R users, I have created a series of postscript files and I?d like to print them with the file name added to the printout. Is there a way of reading these files into R (e.g. using rimage after conversion to jpeg), adding the file name, and then sending the files to a windows printer? I have already tried the rimage package, and several image batch conversion program, but none was so far

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 --

Hello to the list, I noticed something that it seems weird to me with postscript device in dev.print function. Suppose this little code: x<-1:10 par(family="sans") plot(x, main="main") Using dev.print with pdf device brings no problem dev.print(device=pdf, file="test.pdf") But using postscript device dev.print(device=postscript, file="test.ps") I get

Hi, I have printing with wineps successfull used in the older wine versions. After I have upgraded to 20010418, the printing does?nt work longer with the same configuration as before. What have must I change, to get back a working printing wine ? - The error text is: ---------------- snip ----------------------------- err:psdrv:PSDRV_FindPrinterInfo Error 2 getting PPD file name for printer

Hi all, I have a problem with plotting: (R-1.2.2 on SunOS fluke 5.5.1 Generic_103640-27 sun4u sparc SUNW,Ultra-Enterprise solaris 2.) I define a function to switch between plotting on graphics device and generating a postscript file (which can also be automatically be printed) plt <- function(view,f,file="") { if (view>0) f else {

I am running wine version 20010824 and have been trying to get printing to work. I am running wine on a Slackware 8.0 box with the 2.4.7 kernel. Command: wine -debugmsg +psdrv excel.exe Result: ---snip trace:psdrv:PSDRV_Init (0x41422000, 0x00000002, (nil)) trace:psdrv:PSDRV_Init (0x41422000, 0x00000003, (nil)) FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock ---snip

--lHuqAdgBYNjQz/wy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! Since netfilter/iptables is a volunteer based effort, the project lives by more participation and involvement of it's user community. While we receive lots of code contributions (new matches/targets, patches, bugfixes, ...), there is lots of work in

Hi folks, I'm having a problem getting my printer to work with wine... I got through the how-to dozens of times, but it just doesn't work. In the print-setup dialog of the application (Kipplinger TaxCut 2000) Wineps is shown in the combobox but without port and so. Wine shows the following errors: fixme:commdlg:PRINTDLG_OpenDefaultPrinter Could not open printer Wine PostScript Driver?!

Hi folks. I've got a system where my WinXP (they still work well) workstations have a virtual printer installed on them. This virtual printer uses Apple Colour Laserwriter Postscript drivers to generate PS files which are then printed to a linux server where Samba passes the file to one of my scripts which then parses the file, extracts data, coverts the PS to PDF and then inserts the

I've noticed that the postscript files produced by R-0.49 come up inverted in my postscript previewer. Also, they do not behave like encapsulated postscript files so they can't be imported into LaTeX documents. If I remove lines with page-oriented commands like "%%Page", "%%Orientation", "\bp" and "\ep", the resulting files seem to behave like

hi, I've noticed a small problem trying to include postscript plots generated by R into a latex document. Specifically, the latex package graphicsx allow you to specify the bounding box of the postscript file, so that you can just show _part_ of the postscript file if you tell it to also clip the area outside of the bounding box. I've previously used this LaTeX feature without problems

Full_Name: Peter Perkins Version: 1.2.1 OS: LinuxPPC Submission from: (NULL) (24.4.89.36) Unlike (at least some) other args/components of ps.options(), the onefile= arg to postscript() does not default to ps.options()$onefile. For the family= and landscape= args, for example, it does. Looking at postscript()'s code, this appears to be intentional. If it _is_ intentional, the following

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: