public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: extract an image from a .doc file?
Date: Mon, 14 Dec 2009 19:21:36 +0000	[thread overview]
Message-ID: <2D94F7B3-3561-44F8-AE9F-45C960F9C02E@stellar.eclipse.co.uk> (raw)
In-Reply-To: <20091214144344.GA21815@princeton.edu>


On 14 Dec 2009, at 14:43, Willie Wong wrote:
> ...
> (b) If the Big Wig is already happily letting the computer sign those
> documents for him, is it prohibitive to try the non-technological
> measure? E.g., ask the Big Wig to provide another image of his
> signature?

Oh, for sure.

I just didn't expect it to be this complicated. I expected to be able  
to open the document and pretty much to be able to click on the file  
to ascertain it's file size. I expected to be able to turn around  
quickly to the boss and say "you'd have saved all this file space if  
you used a 20kb version instead".

When I posted here I was kinda expecting someone to be able to suggest  
a 2- to 5-minute fix. I had no idea it would be this complicated, and  
now I'm mostly only interested because it has become an interesting  
problem.

> (c) If the image file is that big, it is probably because the
> original that got included in the doc file has a ridiculously high
> resolution (maybe they just scanned the signature in, cleaned it up a
> bit? My signature usually fits in a 1/2 inch by 2 inch block, if
> scanned at 24-bit color and 600 dpi, this makes almost a 1M raw
> image). I hope if the processing/storage/bandwidth tax is high
> enough, an "upstream" fix would not be ruled out directly.

Yeah, I think I have a copy of my signature here which was scanned at  
about that kinda resolution, stored as a bitmap & has a large  
filesize. When I discovered how badly it slowed down Word when  
actually trying to place it in a document it got replaced with a much  
smaller gif version. The improvement in performance that this  
eventuated was, to me, slightly unexpected - surely whatever the  
original format, both images must be stored in RAM in about the same  
way.

Stroller.




  reply	other threads:[~2009-12-14 20:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13  8:46 [gentoo-user] OT: extract an image from a .doc file? Stroller
2009-12-13 10:50 ` Mick
2009-12-13 12:12   ` Stroller
2009-12-13 12:50     ` Mick
2009-12-13 14:57 ` felix
2009-12-13 15:01 ` Sebastian Beßler
2009-12-14  9:48   ` Stroller
2009-12-14 13:01     ` Renat Golubchyk
2009-12-14 14:43       ` Willie Wong
2009-12-14 19:21         ` Stroller [this message]
2009-12-15 15:50           ` Marcus Wanner
2009-12-14 15:43       ` Stroller
2009-12-14 16:44         ` Renat Golubchyk
2009-12-15 14:22           ` Sebastian Beßler
2009-12-14 15:06     ` Arttu V.
2009-12-14 15:18       ` Willie Wong
2009-12-14 16:25         ` Dale
2009-12-14 17:27           ` Willie Wong
2009-12-14 19:45           ` Stroller
2009-12-14 16:46     ` Sebastian Beßler
2009-12-14 19:23 ` Daniel da Veiga
2009-12-15 13:01   ` Stroller
2009-12-15 14:00     ` Mick
2009-12-15 16:29       ` Stroller
2009-12-15 21:45         ` Mick

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2D94F7B3-3561-44F8-AE9F-45C960F9C02E@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox