printer Panasonic DP-c262 with pxlmono driver; I'm in Italy. I installed this new printer, and set default page to A4. However, when I print a new or old document, US letter size is shown and used; even if I set A4, US letter is used in printing. In order to get A4 accepted I must set it and print the doc to file: after that A4 is saved. I think this bug arose with 4.3 release
Actually you can change the paper setting when you are going to print, and apparently the setting changes, but the printer receives the document with US letter size
Please attach a document with which you have this problem. Set status to NEEDINFO, please set it back to UNCONFIRMED once you have provided requested informations. Best regards. JBF
The problem is with documents saved with some previous versione of LO. If you tell me where I can find the LO version used in the odt archive I think I can get this info. The problem isn't with all the printers: in my case I have it with Panasonic DP-C262 while I don't have it with Epson Stylus Office BX535WD
(In reply to Paolo Benvenuto from comment #3) > If you tell me where I can find the LO version used in the odt archive I > think I can get this info. It is in the meta.xml, inside the <meta:generator> tag
Created attachment 119562 [details] A5 document with depliant printing mode set
Apparently the
With LO 4.4.2.2 the bug changed: with old or new documents opening the printer dialog always show A4 portrait, I mean because it's the printer default size and orientation. With the document I just uploaded, which is an A5 with printing layout set to depliant (booklet), I expect the print dialog says A4 landscape
(In reply to Paolo Benvenuto from comment #0) > In order to get A4 accepted I must set it and print the doc to file: after > that A4 is saved. Click "Use only paper size from printer preferences" checkbox on the File > Print .. Options tab. See https://bugs.documentfoundation.org/show_bug.cgi?id=61186 and https://wiki.documentfoundation.org/ReleaseNotes/4.1#Other Closing as duplicate of 67576 *** This bug has been marked as a duplicate of bug 67576 ***