I assume many of you host a DMS such as Paperless and use it to organise the dead trees you still receive in the snail mail for some reason in the year of the lord 2023.

How do you encode your scans? JPEG is pretty meh for text even at better quantisation levels (“dirty” artefacts everywhere) and PNGs are quite large. More modern formats don’t go into a PDF, which means multiple pages aren’t possible (at least not in Paperless).

Discussion on GH: https://github.com/paperless-ngx/paperless-ngx/discussions/3756

You are viewing a single thread.
View all comments View context
1 point
*

Using an OK scanner makes a big difference.

WDYM? The lossless scans SANE produces themselves subjectively look very good. My only issue is the transcoding to lossy formats I want to do in order to save >3/4 of the space.

permalink
report
parent
reply
1 point

Oh, it’s common in my country to use a smartphone to ‘scan’ documents by actually just taking a lousy photo of them. It’s so prevalent that when you tell someone to do a scan they usually do this instead.

I bought a cheap canon scanner for 50$ and it’s pretty perfect for legal documents. A little slow maybe. I use SANE, then do lossy compression too.

In rare situations I’d then post process the PDF to even worse quality using ghostscript, for example when a foreign visa application form requires a scan of a really long document, but doesn’t accept sizes over 2MB.

permalink
report
parent
reply
1 point

I use SANE, then do lossy compression too.

Well, what kind of lossy compression? JPEG?

IME, JPEG looks quite terrible for text documents -even at q=95.

permalink
report
parent
reply
1 point

@Atemu
I just use grayscale PNGs, myself. optipng usually takes them down to a decent size.
@Saigonauticon

permalink
report
parent
reply
1 point

Yeah just jpeg. Always comes out perfectly legible.

permalink
report
parent
reply
1 point

@Saigonauticon @Atemu A scanner is a camera. Why complicate things?

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 3.8K

    Monthly active users

  • 3.7K

    Posts

  • 80K

    Comments