From: Antoine <melser.anton@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [ot] PDF or PS format for daily use?
Date: Wed, 26 Oct 2005 21:04:13 +0200 [thread overview]
Message-ID: <435FD32D.6010101@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0510231551570.501@Quasimodo.realss>
Zhang Weiwu wrote:
> Hello. I have got a lot (much more) ps files and PDF files since I start to
> use Linux. In the past there were mostly doc files but now I always prefer
> to have a PS or PDF copy to ease the compatibility pain. And looks linux
> people always prefer to send me a PS or PDF document.
>
> Because I always save two copies of every of my document, one in original
> format (eg. odt) and another in printable format for my colleagues in case
> they don't have the Linux fonts and software. Here comes the question should
> I keep a PS copy or PDF copy.
>
> I think PDF copy is absolutely the prefered format because:
> * easier to find acrobat reader;
> * can be 'Tagged', especially used with OOo;
> * possibility to 'copy and paste', though format will be lost;
> * not to take other people by surprise with unfamiliar PS extension;
> * different quanlity: I can save PDF in very high quanlity that I was told
> "can be taken to press house"
> * easy to convert to PS format when needed.
>
> Here comes the question: if the above all stands true, why do I ever need PS
> format at all? There might be some reasons to keep this format still
> existing. Perhaps in other areas, other then office work.
>
> So the conclusion: for typical office workers, we can forget PS format.
>
> Now welcome for suggestions.
I think the key to this whole story is the second to last line above.
"for typical office workers" says it all. I think you are quite right to
say you can forget PS format. You could probably stick with pdf if you
only need the documents for 2-5 years. PDF is very much industry
standard for archiving, and isn't going away soon.
I would *definitely* think about keeping documents (if you are going to
go to the trouble of archiving and all that) in text format, probably
xml like odt or even m$ xml, because if the data are valuable then
finding something to read it in 50 years will probably be difficult. The
EU is looking like it will go that way just like Massachusetts - no
reason why you shouldn't either. You will ALWAYS be able to find or
create a tool to get decently printed and onscreen presentation from
well marked up plaintext.
Cheers
Antoine
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-26 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 8:08 [gentoo-user] [ot] PDF or PS format for daily use? Zhang Weiwu
2005-10-24 13:33 ` Daniel da Veiga
2005-10-24 13:51 ` John Jolet
2005-10-24 14:22 ` Daniel da Veiga
2005-10-24 14:46 ` John Jolet
2005-10-24 14:50 ` Digby Tarvin
2005-10-24 15:14 ` David Helstroom
2005-10-29 23:42 ` Matthias Bethke
2005-10-24 18:58 ` Chris Gottbrath
2005-10-25 0:10 ` Nick Rout
2005-10-25 10:57 ` Hans-Werner Hilse
2005-10-26 0:36 ` Nick Rout
2005-10-24 20:35 ` Hans-Werner Hilse
2005-10-26 19:04 ` Antoine [this message]
2005-10-26 19:52 ` Nick Rout
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=435FD32D.6010101@gmail.com \
--to=melser.anton@gmail.com \
--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