I know that printing on Linux is somewhat of an art form, but I have
a fairly simple problem. I used the following command to configure a
networked printer (HP LaserJet 8150):
lpadmin -p name -E -v socket://name -m laserjet.ppd -u allow:all -
u deny:none
This added and enabled the printer, and I can print to it using the
print command from within a GUI application and PostScript utilities
like enscript. However, printing simple text files from the command
line using lpr or lp produces undesirable output that looks like this:
Line 1
Line 2
Line 3
It seems rather obvious that the printer is expecting carriage
returns and not getting any. What is the "right" way to fix this
using CUPS, which "owns" the /etc/printcap file. I can't be the
first one to run into this issue...
Thanks,
Alfred
On Aug 8, 2006, at 3:21 PM, Alfred von Campe wrote:> I know that printing on Linux is somewhat of an art form, but I > have a fairly simple problem. I used the following command to > configure a networked printer (HP LaserJet 8150): > > lpadmin -p name -E -v socket://name -m laserjet.ppd -u allow:all - > u deny:none > > This added and enabled the printer, and I can print to it using the > print command from within a GUI application and PostScript > utilities like enscript. However, printing simple text files from > the command line using lpr or lp produces undesirable output that > looks like this: > > Line 1 > Line 2 > Line 3 > > It seems rather obvious that the printer is expecting carriage > returns and not getting any. What is the "right" way to fix this > using CUPS, which "owns" the /etc/printcap file. I can't be the > first one to run into this issue... > > Thanks, > AlfredI would use printconf instead of lpadmin. It sets up all the necessary filters. Tony
On Tue, 2006-08-08 at 15:21 -0400, Alfred von Campe wrote:> It seems rather obvious that the printer is expecting carriage > returns and not getting any. What is the "right" way to fix this > using CUPS, which "owns" the /etc/printcap file. I can't be the > first one to run into this issue...I would avoid printconf - it sucks (my opinion of course, but printconf really does suck). It destroys cups.conf. Instead, use foomatic-configure to set up/configure your print queue(s) for CUPS. It's simple to use. For example: foomatic-configure -s cups -n epson -N "Epson Stylus Color 600" -L "Office" -c file:/dev/lp0 -d gimp-print-ijs -p Epson-Stylus_Color_600 Most of that is self-explanatory. The "tricky" part is finding out which driver to use ("-d"), and what the Foomatic ID is for your printer ("-p"). The driver bit you can determine by going to the www.linuxprinting.org. The ID can be determined by greping the foomatic database. For example: foomatic-configure -O | grep Epson- | sort | less BTW, if you end up at www.linuxprinting.org, you can download the driver for your printer from there too, in which case you don't have to use foomatic-configure. For more detailed steps, refer to this: http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/II.Foomatic-User/II.tutorial-handout-foomatic-user.html HTH, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2142_FC4 i686 GNU/Linux 12:50:40 up 6:20, 3 users, load average: 1.40, 1.02, 0.71