Mention on the export screen that black and white pages are smaller as PDF - #242
Conversation
|
CI will be red until #241 is merged, the tests on the branch don't compile without it. |
|
Did you do your tests before or after f0e71e7? |
|
And who, apart from people with a technical background, would look for a JPEG export? |
Before (and after), but my version already had the same downscaling since September 12, and that's what they tested with. The difference is still there: 48 kB as PDF, 240 kB as JPEG, plus the artifacts. |
Both formats have their use cases. I scan to PDF for archiving, but sometimes I want to send a document in a messenger, so I use JPG so it shows up inline, like a photo, just straightened and cropped. Sending each other JPG images is normal and people who set JPG as their default for that reason would save black and white as JPG too, without knowing that in this case it makes a big difference. Either way, only people who set JPG will ever see the line. If that's nobody, it doesn't get in anyone's way. |
I see. On my side, I was comparing JPEG grayscale vs JPEG black and white, which is what f0e71e7 addressed. |
|
OK, thanks. I may change the message before the release. |
Since your comment I've thought about this for a few days, talked to a few people (archiving documents was already a topic here before I found FairScan) and tried the app with and without the line. I'm convinced now that it's needed. Nobody without a technical background expected the file format to make such a difference for black and white. When I asked them to compare the two exports, one asked whether the size difference was a bug. But they all agreed that if they knew black and white is smaller and sharper with PDF, they'd do it.
I shortened the text after your feedback and made it the normal text color instead of red. It only shows when the document has a black and white page and the output format is JPG, so nobody else has to see it.
One string in all locales, machine translated.