From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: "Jan Böcker" <jan.boecker@jboecker.de>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [OT] Scanning for archiving
Date: Sat, 5 Nov 2011 15:06:52 -0600 [thread overview]
Message-ID: <CACHMzOGATdHMD4UFhp_xNKgDx5RmTsehOB=kyM4VQM+ExRFxXQ@mail.gmail.com> (raw)
In-Reply-To: <4EB5A43E.5070605@jboecker.de>
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
Hi Jan,
I was in fact just looking at that article again a few minutes ago. I
recalled that we had discussed that before briefly and that I saw it
somewhere, and then I remembered about the discussion about your archiving
system.
Thanks again!
Marcelo.
On Sat, Nov 5, 2011 at 3:01 PM, Jan Böcker <jan.boecker@jboecker.de> wrote:
> On 11/05/2011 09:03 PM, Marcelo de Moraes Serpa wrote:
> > Hi list,
> >
> > I just bought a scanner and started to scan important documents as a
> > backup, and archiving them with meaningful metadata in orgmode files.
> > Then a question came to mind - what dpi to use? I'm not really savvy
> > when it comes to scanning or printing, and I want like a dpi that allows
> > me to reprint the document at an acceptable quality later if necessary,
> > but that also doesn't take that much space (600dpi pdfs take around 5MB).
>
> Hi Marcelo,
>
> I am using 300 dpi. Even the fine print on my cell phone contract is
> still comfortably readable at this resolution.
> I guess that about 150 dpi is sufficient for most documents, but I don't
> bother thinking about that on a case-by-case basis and just scan
> everything at 300 dpi.
>
> I do scan most documents in grayscale and only enable color when required.
>
> Said cell phone contract weighs in at 4.6 MiB for a 6-page grayscale PDF
> (about 770 KiB per page).
>
> Btw, my problem with big file sizes it not exactly disk space (which
> rapidly becomes cheaper with time) but the time it takes evince to
> display the document on my laptop :)
>
> If you are interested in the shell script I use to scan to PDF files,
> see
>
> http://www.jboecker.de/2010/04/14/general-reference-filing-with-org-mode.html#sec-5
>
> Hope this helps,
> Jan
>
[-- Attachment #2: Type: text/html, Size: 2339 bytes --]
next prev parent reply other threads:[~2011-11-05 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 20:03 [OT] Scanning for archiving Marcelo de Moraes Serpa
2011-11-05 20:34 ` Achim Gratz
2011-11-05 20:52 ` Marcelo de Moraes Serpa
2011-11-05 21:01 ` Jan Böcker
2011-11-05 21:06 ` Marcelo de Moraes Serpa [this message]
2011-11-05 22:36 ` Pieter Praet
2011-11-05 23:35 ` Samuel Wales
2011-11-06 21:59 ` Pieter Praet
2011-11-07 6:14 ` TP
2011-11-09 8:51 ` Pieter Praet
2011-11-20 13:57 ` Matt Lundin
2011-11-07 17:44 ` Karl Voit
2011-11-09 7:40 ` Pieter Praet
2011-11-09 9:06 ` Johnny
2011-11-09 11:05 ` Karl Voit
2011-11-09 14:53 ` Karl Voit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACHMzOGATdHMD4UFhp_xNKgDx5RmTsehOB=kyM4VQM+ExRFxXQ@mail.gmail.com' \
--to=celoserpa@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jan.boecker@jboecker.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).