Date: Sun, 11 Sep 2011 07:21:40 -0400 From: Jerry <jerry@seibercom.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Printing from Firefox broken after update. Message-ID: <20110911072140.17d8ec2d@scorpio> In-Reply-To: <20110911085342.3c820f79.freebsd@edvax.de> References: <4E6A3504.6020002@eskk.nu> <20110909191726.4af3e660@debiand1.localdom.ain> <4E6A6152.5070703@eskk.nu> <20110909222951.45a29861.freebsd@edvax.de> <4E6B324F.8030700@eskk.nu> <20110910082446.0e8280eb@scorpio> <4E6C56D5.4030600@eskk.nu> <20110911085342.3c820f79.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 11 Sep 2011 08:53:42 +0200 Polytropon articulated: > Do you get better results when printing to a file (PS) and > then sending it directly to the printer (via lpr)? Maybe > this problem is comparable to my Opera printing problem > (where I could identify Opera being the source of invalid > PS data). Wow, what a waste of time that is. I just use MS Windows when I have to print and avoid all that rigmarole. Firefox use to work correctly; however, it no longer does. At first I thought it was a localized phenomena; however, after checking on several different forums I have concluded that it is far more wide spread than I had originally thought. There have been reports filed against this behavior. If and when they are acted upon is anyone's guess. In the mean time, I just use what is convenient and works reliably without adding an undo burden upon myself. Continual use of broken software effectively makes the end user and enabler; something I have no desire to invest my time in. -- Jerry ✌ jerry+fbsd@seibercom.net Disclaimer: off-list followups get on-list replies or ignored. Do not CC this poster. Please do not ignore the "Reply-To" header. http://www.catb.org/~esr/faqs/smart-questions.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110911072140.17d8ec2d>