Re: PS file not portable

From: Vinod Gupta (vrak58_at_yahoo.com)
Date: 02/29/04 

Date: 29 Feb 2004 12:06:02 -0800

Robert Heller <heller@deepsoft.com> wrote in message news:<80931$4041480d$cb248f0$20082@nf2.news-service.com>...
> vrak58@yahoo.com (Vinod Gupta),
> In a message on 28 Feb 2004 16:25:48 -0800, wrote :
>
> VG> I have created a PS file from TeX document on my Linux RH9 which print
> VG> fine on a networked PS printer. If I send the same PS file to Windows
> VG> users, while they can view the file using ghostview, but printing to
> VG> the same PS printer is painfully slow. It seems gv sends a bit map to
> VG> the printer as the job is shown as 100 times larger than the size of
> VG> the PS file. The document has no images. Any suggestion?
>
> If the printer IS a PostScript printer, the MS-Windows users *probably
> should not* be using ghostview to print it -- they really should be
> sending the file *directly* to the printer. There are some shareware /
> freeware utilities for doing thie.
>
> I suspect that what is happening is that ghostview is using ghostscript to
> 'convert' the PostScript to the MS-Windows print driver API (GDI?),
> which is being turned *back* into PostScript by the MS-Windows
> PostScript 'driver'. To print a *PostScript* file on a *PostScript*
> printer, the file just needs to be sent directly out the 'port',
> bypassing all 'driver' software. The 'driver' software is making a mess
> of things.

Thanks a lot for this explaination and I believe you are right. I also
appreciate your tip on howto get around. However, I will be interested
in identifying and possibly fixing the source of the problem.

PostScript is supposed to be a universal language, thousands of PS
printers work on this assumption. If latex/dvips on linux is not
producing the "standard" ps, or more likely gs/driver on Windows is
making mess of it then that need to be fixed. Not using gv/gs is not
an option for us because some times we get huge ps files and we often
need to preview and print only selected pages. pdflatex is good
alternative but only for our own tex docs. Many times, ps files are
coming from different sources on which we have no control. It is not
that all ps files fail to print from gv/ps on Windows. So, I am not
sure if problem is badly created ps by latex/dvips on linux or
gv/gs/print_driver on Windows. Howto identify the source of the
problem?

Vinod

Relevant Pages

  • Re: Future of IT in Lebanon
    ... working knowledge of Indian programmers DNA, nor of their intuitive Java ... > So Longhorn is not an experiment and Linux is an experiment? ... another chapter in the Windows story, and the Microsoft marketing machine is ... > application opens, Check the about, it says Microsoft Visual Basic 6.3. ...
    (soc.culture.lebanon)
  • FTP DOWNLOAD! More than 6500 CRACKED SOFTWARE(CAD,CAE,CAM,ED
    ... Autodesk Architectural Desktop 2005 ... DASSAULT SYSTEMES CAA ENOVIA LCA V5R13 ... ALTAIR.OPTISTRUCT V5.1 for LINUX ... ANSYS V8.0 FOR WINDOWS ...
    (microsoft.public.dotnet.framework.adonet)
  • Linux for Senior Citizens
    ... Linux for Senior Citizens ... For such people, I believe, Windows really is a better option: ... The kernel manages all the hardware and also looks after all running ...
    (uk.people.silversurfers)
  • Re: Future of IT in Lebanon
    ... It's the same Linux code base. ... Microsoft Office on a Windows server, it will install and run fine, the main ...
    (soc.culture.lebanon)
  • Re: [SLE] Developing a Real Time Data System
    ... The KBasic License is valid for both operating systems: Windows and Linux. ... Modern BASIC language ... chapters learning about the programming language. ...
    (SuSE)