I have scanned pages into png (jpg print ok :D) they are white with black text. they are into 2 colors (black and white) and in small resolution. Generally they are scanned the way we scanne text. when I use kipi plugins to print images, all of them came out from printer black with white text! I event print them into pdf and the same result. Now I am using gThumb which print them correctly. Reproducible: Always Steps to Reproduce: 1. scan printed page into png in 2 colours and small resoulution 2. print pages using kipi plugins 3. Actual Results: I am getting black background with white letters. I have to use non kde apps to handle that (gnome app :/ ) Expected Results: the pages should be printed the way are displayed on computer screen
Created attachment 75579 [details] the page that are printed with black background and white letters
Created attachment 75580 [details] the way that earlier atachment was printed using kipi plugins (black bacground and white letters)
please help. is is such a waste of tonner.
I can reproduce this with your PNG (in gwenview and digikam). As a workaround you could use okular to print this PNG.
If you print to pdf, does it work instead?
(In reply to comment #5) > If you print to pdf, does it work instead? No, same result, and also when printing to ps.
I confirm this. Printing to pdf, and ps results in color inversion. However printing to jpg doesn't. @masterdany88 As a workaround, kindly print it in jpg format and then print it on your printer, or do it using okular as suggested above. We will look into this. Smit
This file still valid using last kipi-plugins 4.2.0 ? Gilles Caulier
Still reproducible using last kipiplugins 4.9.0 ? Gilles Caulier
masterdany, This file still valid using last kipi-plugins 4.10.0 ? Gilles Caulier
New Kipi-plugins 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier
digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance.
This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier