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:45:01 +0000 [thread overview]
Message-ID: <FC0A905B-7768-47F0-B55A-916583B36D74@stellar.eclipse.co.uk> (raw)
In-Reply-To: <4B26670F.2020200@gmail.com>
On 14 Dec 2009, at 16:25, Dale wrote:
> ...
> I'm somewhat clueless about this software issue but wonder about
> this way of seeing things. Since it appears there is a signature,
> as in what is at the bottom of a letter or a bank check, wouldn't
> they want to make it so that is not able to be extracted at all? If
> I had a digital signature, I wouldn't want to put it somewhere that
> it could be used by someone that I wouldn't want it to be used by.
My customer, an agency which rents out apartments on behalf of
landlords, has a server on which they store all their files. These
letters are generated by their property management software, and are
written to their landlords, tenants &c. Obviously they have to keep a
big archive of copies of all the letters they've written in the past.
The letters are stored in .doc format, but when they're originated I
think they're actually just printed out and posted. Storing the
signature in the .doc is, I think, just a convenience to save the boss
(or other members of staff) having to physically scribble a signature
at the bottom of each letter.
I'm guessing the office might manage c 100 properties, and I imagine
that they may generate some thousands of letters per year. So a 1meg
image in a letter might well start to consume gigs of disk space.
"Gigs of disk space" is only a little bit of a problem because when
this server was manufactured, 4 years ago, decent RAID meant
horrendously expensive SCSI disks (it is still under support contract
for another year) and because I haven't got around to migrating them
away from an offsite-backup provider who is somewhat overpriced.
Hope this clarifies,
Stroller.
PS: a couple of great suggestions have been made this afternoon. I'm
going to watch some of the fruits my labours - my labours involving
get_iplayer earlier today - and will try these suggestions later. Many
thanks!
next prev parent reply other threads:[~2009-12-14 20:23 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
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 [this message]
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=FC0A905B-7768-47F0-B55A-916583B36D74@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