[NTLUG:Discuss] printing from Linux

./aal al_h at technologist.com
Sat Dec 10 18:01:37 CST 2005


Leroy Tennison wrote:
> Charles Cashion wrote:
> 
>> I would like to understand the flow of information from a
>> program to a printer.
>>
>> True for False?
>> The output from Linux programs is occasionally, frequently,
>> most frequently, almost always PostScript?
> 
yes
> 
> Haven't got a clue, hopefully someone else has.
> 
>>
>> True for False?
>> If you feed PostScript (PS) to a printer that understands PS or
>> that pretends to understand PS (emulation), then you will get
>> your printout.
> 
> 
> If it's valid Postscript and the printer is either set to expect 
> Postscript or is capable of automatically detecting it (on this latter 
> point remember other intelligent technologies such as plug-and-pRay and 
> advanced power MISmanagement not to mention NIC auto-speed deFection) 
> then you should get it's interpretation of the printout (genuine Adobe 
> Postscript is the standard, emulators? Well, place your bets).  If it's 
> not valid Postscript you may well see the printer warm up only to do 
> nothing.  If it's a "nice" printer (I haven't seen one yet) you might 
> get a message stating that the Postscript has an error.  Just because 
> it's Postscript doesn't produce magic.  I get fine results on my HP 
> laserjet 1200 series printer with the Linux generic Postscript driver. 
> Think that HP's own Postscript driver for Linux works?  My experience at 
> least is that the answer is "No".
> 
>>
>> True?
>> A NON-PS printer that understands raster scan (RS) can be used
>> if the computer translates PS to RS.
> 
> 
> Depends on the printer.  HP has it's own language (PCL) that consists of 
> Escape codes plus text which gets interpreted into some kind of image 
> before being printed by the printer.  I don't know how many printers 
> accept raster scan directly.  This is definitely not preferable because 
> of the sheer size of the file being sent unless some kind of compression 
> is done in which case both ends have to agree somehow on which 
> compression technique is used.  The printers I've seen all have their 
> (usually proprietary) Escape sequence languages.  Ihaven't done the 
> research but I would think that Linux printer drivers for the popular 
> printers would use the printer's Escape sequence language rather than 
> output raster scan.
> 
>>
>> True?
>> Almost any new printer (ink jet or laser) does raster scan.
>>
only if it does not say postscript

cavet: alot of new ones are "winprinters"(see winmodem)
windows emulates the parralell hdwr the printer lack
these often dont work in linux, if they do they are slow

>> Options?
>> If your printer does not understand PS, then you have several
>> options:
>>         1. You translate PS to raster scan and send it to
>>                 the printer?
>>         2. You send your printing to ghostscript and that
>>                 converts it to RS
>>         3. You send your printing thru pimp and it does the
>>                 conversion
>>
>> Print Specific file:
>> So if you are going to convert PS to RS,

or what ever proprietary lang the printer speaks(maybe not RS)

  you are really
>> translating PS to whatever language the printer speaks?

yes

>>
>> WHAT I REALLY NEED: If you understand how printing works, and
>> you learned it from something you read, I want to know what
>> you read. I want to read it.
>>

tldp.org
google.com

>> WHAT HELPS: Most of the time, I have to read something from
>> more than one source before I finally understand it. If more
>> than one person would suggest something to read, it would
>> help. Please let me know what you read that finally caused
>> you to understand Linux printing.
>>

/etc/printcap
and other print config files
the settings will point you to things to investigate

man <app> is also quite useful



>> Tnx,
>> Charles
>>
>>
>>
>> _______________________________________________
>> https://ntlug.org/mailman/listinfo/discuss
>>
> 
> 
> 
> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss
> 





More information about the Discuss mailing list