Slashdot Mirror


Making Linux Printing as Easy as in Windows

Jonny5 writes: "In preparation for the transition from windows to a Linux based workstation, the main focus is that of peripheral compatibility. Sure Linux is rock solid stable, and has an almost totally customizable GUI, but dammit, if my hardware won't work, what's the point? ...After hearing about TurboPrint, and their claim to provide 'Printer set-up and configuration is as simple as on Windows or MacOS,' I had to rise to the challenge. LinuxLookup.com has done a full review of TurboPrint For Linux."

7 of 278 comments (clear)

  1. What I would like to see.. by brunes69 · · Score: 5, Interesting

    .. is some kind of wine-driven printer emulation layer, that would let you use windows printer driver sin Linux. Why? Because I have a printer that I have had for 4 years now, and is still nowhere near a Linux solution. Is this idea even possible? I think it would be great if it were, since I could finally use my printer!

  2. doesn't seem comparable to Mac or Windows by tim_maroney · · Score: 5, Insightful

    What's wrong with this picture?

    Printer set-up and configuration is as simple as on Windows or MacOS

    TurboPrint for Linux comes as a tarball containing 'install' and 'uninstall' shell scripts, installation instructions, and all the binary software.

    Yes, it's a command-line installer!

    The default printing would be in black and white, and when I want to print in colour, I can just change the print command used by the program from 'lpr' to something like 'lpt -Ptp0'.

    Yes, you have to give command line options to set printing modes every time you print with a different mode!

    And yet this gets an 18 out of 20 in the review. It's amazing to me that this late in the game, there are still so many Linux-heads who just don't get it. This is not just inferior to Mac and Windows -- it's a giant quantum leap backward from where Mac has been for seventeen years and Windows for six. Real end users don't memorize command languages.

    Tim

  3. Printing, and then maybe fonts by Beautyon · · Score: 5, Insightful

    The next problem after printing is ironed out is the lack of a single, easy to use tool to add, temporarily disable, manage and remove fonts in any Linux setup, that makes one set of fonts (both ttf and Type 1) in a single directory available to all applications system wide, in the way that Adobe Type Manager does.

    We then need CMYK capability in The Gimp. After these are in place, it will be possible to assemble a desktop publishing suite that will have mass appeal, because anyone will be able to design and publish to QuarkXpress/Photoshop/Illustrator quality, and print the results, all in a rock solid, free alternative to Windoze and OSX, without any pain.

    --
    ATH0 Bitcoin: 1DnwFLXczVZV8kLJbMYoheUrpqHesjxrSi
  4. The Windows GDI by rcw-home · · Score: 5, Informative
    Windows print drivers work by accepting Windows GDI (Graphics Device Interface) commands and using them to plot a page.

    UNIX apps don't send GDI commands - they usually send postscript commands.

    So unless someone wants to write a postscript to GDI filter, that approach won't work.

    Oh, and things that need to communicate directly with your hardware (like this printer driver) may not be able to run in wine anyway.

  5. Why not Lexmark? by Bowie+J.+Poag · · Score: 5, Informative



    In my experience, Lexmark has wonderful Linux support for its products. $79 at Best Buy got me a very high quality 1200dpi inkjet printer (the Lexmark Z23) with both Windows and Linux support. The Linux side actually works better than its Windows counterpart, oddly enough. It runs as a daemon process, does PostScript exactly the way it should, and the fact that its a USB printer doesn't complicate the situation either. It all just plain works, out of the box. Even has a nice graphical config utility

    Kudos to Lexmark for doing it right!

    --
    Bowie J. Poag

  6. what "side"? by Anonymous Coward · · Score: 5, Interesting
    What is this "our side" you're talking about? I mean this seriously.

    "My side" wrt Linux is a place where things really ARE modular and logical. Where, if you have an extraordinary knowledge of systems and computer science as a whole, you can enjoy your time in it. Where, if something isn't working, you can change and recompile it within hours.

    Your "our side" seems to be that awful "I want Linux to be a better Windows than Windows!" garbage. Here's some advice: Linux is not Windows, and Linux will never be Windows. It will never be worse than Windows; it will never be better than Windows -- IT WILL NEVER BE COMPARABLE TO WINDOWS. If you want something like Windows, use Windows. If you want something kind of like Windows but different, use Windows. If you want something better than Windows -- sorry to say it -- you're going to have to live with Windows. LINUX IS NOT WINDOWS.

    And why on Earth would you be trying to "win over" someone to "your side"?! Can you even THINK of anything more dishonest? Linux is not Britney Spears; it is not a Happy Meal. If people use it, it's because they want a free Unix-like operating systems, they've done their research, and they WANT to use it. It's not because they've been tricked into something (sorry -- "won over"), so that when they finally do try out Linux, they're horribly disappointed at how un-Windows-like it is, and hold some kind of great resentment towards it.

    Look around the web. How many "Linux sucks" posts and websites do you find? A LOT. Is it because Linux actually sucks? Not likely. It's because some "helpful" friend tried to "win them over". They probably said something like "if you're tired of Windows crashing all the time, try this other operating system called Linux". They try Linux, expecting it to be better than Windows, and SURPRISE SURPRISE find out that it "sucks". If you use Linux expecting it to be Windows, guess it, it sucks donkey balls. Not just any donkey balls either -- big ones. LINUX IS NOT WINDOWS. DON'T PRETEND IT IS. AND FOR THE LOVE OF GOD, FOR THE GOOD OF HUMANITY AND COMPUTER USERS EVERYWHERE, DO NOT "WIN OVER" SOMEONE EVER AGAIN.

  7. To all you CUPS advocates out there... by SCHecklerX · · Score: 5, Informative
    ...Just make sure you set
    PreserveJobHistory No
    PreserveJobFiles No
    in your /etc/cupsd.conf, or your cupsd process will get HUGE over time!! Mine grew to over 17 Meg on my own box. Sheesh!

    Also, make sure there are no spaces after the 'No's. The first time I tried configuring this, I had a space after the word and the braindead parser couldn't recognize the option because of it(not sure if they've fixed it in the newer versions or not)...so I swore for a couple hours before actually checking my syslog as to why the damned thing kept ignoring the option :)

    The GUI should let you purge completed jobs, IMNSHO. For a basically single-user system, it's best to just disable those two options, unless you are into checking your /var/spool/cups directory on a regular basis (I have better things to do with my time)