Re: [libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-12 Thread Kracked_P_P---webmaster
On 04/10/2014 11:53 AM, CVAlkan wrote: Re: "Also I use CUPS-PDF for my default printer, so I can print pages from a browser and skip those pages I do not want/need to print." I hadn't thought of that, but coincidentally I just opened a new ink cartridge from HP and found a promotion for somethin

Re: [libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-12 Thread Kracked_P_P---webmaster
The reason I stated that was due to the fact that with the conversion process from the old legacy coding languages to Python [and such] many of the bugs are tracked down and removed. Also, that helps remove coding conflicts that might arise as the new fixes and features are added to the code

[libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread CVAlkan
Terribly sorry if my ramblings got misinterpreted ... I am pretty much in full agreement with all your points. -- View this message in context: http://nabble.documentfoundation.org/Possible-LibreOffice-Duplex-Printing-Bug-tp4104713p4104815.html Sent from the Users mailing list archive at Nabbl

[libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread CVAlkan
Re: "Also I use CUPS-PDF for my default printer, so I can print pages from a browser and skip those pages I do not want/need to print." I hadn't thought of that, but coincidentally I just opened a new ink cartridge from HP and found a promotion for something they call "Smart Print," a (seems to be

[libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread CVAlkan
So sorry if my comments were misinterpreted - Tom's is one of the few names that I recognize so I know he's on board. I am concerned, however, with your suggestion that "modern languages" reduce bugs. They might make it easier to avoid bugs, or make it easier to spot bugs, but the only thing that

[libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread Alex Thurgood
Le 09/04/2014 23:31, CVAlkan a écrit : Hi, > d) Even so, once the single page is printed, the paper is "sucked back in" > and fed through a second time. Nothing prints of course, but this is > actually a potentially serious problem under some conditions which I'll > explain momentarily. I see th

Re: [libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread Tom Davies
Hi :) The point about having plenty of Ram is that if you do then you can go into Tools - Options - Memory and bump the settings up really high. The defaults are set for very low Ram machines. Actually i do have a lot of confidence in LibreOffice and OpenOffice. I've almost never had any proble

Re: [libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread Kracked_P_P---webmaster
On 04/10/2014 08:09 AM, CVAlkan wrote: Good points all, but I suspect not my problem. I almost mentioned during my post that folks should ignore the fact that my HP-LIP (3.14.4) had been released just the day before my post. It is, in fact, the "latest and greatest" as they say. But the problem

Re: [libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread Kracked_P_P---webmaster
On 04/10/2014 07:48 AM, CVAlkan wrote: Thanks for the responses ... I have reported the issue as a bug (for whatever that's worth); the number is 77265. I acquired my build from the nightly builds (albeit a while back); I did not compile it myself. As for Tom's suggestions: I have 4G or memor

[libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread CVAlkan
Good points all, but I suspect not my problem. I almost mentioned during my post that folks should ignore the fact that my HP-LIP (3.14.4) had been released just the day before my post. It is, in fact, the "latest and greatest" as they say. But the problem I'm experiencing has existed for quite a

[libreoffice-users] Re: Possible LibreOffice Duplex Printing Bug

2014-04-10 Thread CVAlkan
Thanks for the responses ... I have reported the issue as a bug (for whatever that's worth); the number is 77265. I acquired my build from the nightly builds (albeit a while back); I did not compile it myself. As for Tom's suggestions: I have 4G or memory and I quite regularly use LO for very l