On Wed, 2005-07-06 at 20:59 +0300, Martin-Eric Racine wrote: > > > > I'd just like to say I think the old default of $HOME/cups-pdf/ is > > better than $HOME/ because it means the output goes somewhere expected > > and _isolated_ from your other files. This is especially helpful when > > Windows is sending printjobs through with all kinds of unexpected > > filenames, and it's therefore much more unlikely to accidentally > > overwrite an unrelated file. > >
> The advantage is that documents get sent straight to a familiar folder, > instead of a fuzzy-named cups-pdf; users won't necessarily associate the > name of the back-end with the ability to print documents out or to the > similarily-named subdirectory sitting in their home-directory. > > In fairness, I think that CUPS-PDF and Xprint (or any PDF backend) should > output to a common directory, which could be e.g. ~/Printouts or something > similar. Then again, this would require teaching users where to find the > PDF documentss which, by definition, is a bad idea; anything that is not > self-evident from a layman user's point of view is simply not acceptable. > Xprint currently prints to ~/Xprintjobs (if you use the built-in PDF-file or PS-file printer). I'm happy enough to rename it. ~/cups-pdf wouldn't make sense - Xprint is not CUPS (and does ps as well as pdf). I might suggest ~/Printing rather than ~/Printouts, it sounds better to my ears at least. Drew _______________________________________________ Xprint mailing list [email protected] http://mozdev.org/mailman/listinfo/xprint
