Ger writes
Or:
- convert all your documents in PDF
- [...]
In a certain pragmatic sense, I agree with this. PDF is a
reasonable "lowest-common-denominator", and it may well be the
best choice. But I still can't let the suggestion go without
qualifying it.
Firstly, PDF's tend to be big. Bigger than common WP formats,
and much bigger than HTML (and cousins). Not a problem if you
have the luxury of broadband Internet, but a real hassle
otherwise.
Secondly, PDF's are ugly ... on screen. They are nice on
paper (although even then usually only if you have a nice high
resolution, color, printer). Because, in general, text cannot
reflow in PDF, display of PDF doesn't normally adapt to the
available display area - the positioning is fixed on the basis of
what will look good on paper, and is very unpleasant to try to
read on screen, with forced horizontal scrolling etc. (IMHO this
is one of the reasons many people say they prefer
reading hardcopy than on-screen; and they are absolutely right. PDF
is much easier to read in hardcopy - that's what it is
designed for...) So: if you have any users with lower res
screens (anything from an old 640x480 PC monitor, through WebTV,
games console, PDA down to mobile phone) then PDF is going to be
very unfriendly for them. There are ways around this, but they
are even uglier!
Thirdly, PDF does not integrate well with the rest of the web.
While PDF can contain hyperlinks, and can be pointed at by
hyperlinks, accessing it normally bounces a user into at best a
browser plug-in, at worst a completely separate application.
"Fluid" hyperlinkage is the very stuff of the web: PDF disrupts
this. (And, combining this with the previous point, if we
print PDF then hyperlinks are not hyperlinks anymore at
all at all...)
Fourthly, PDF is unfriendly to client side assistive technology
for users with disabilities. This is sort of a special case of
the second point, only with a few extra wrinkles. But
basically, optimal access for these users requires that text be
carefully marked up for logical structure, and that that logical
structure be separately translated for rendering or presentation
on a particular device. Non-text things also need to have text
equivalents associated with them. This can be done in
PDF; but it is really quite difficult. It is cutting against the
grain of how PDF was designed. It is a "page
description" language - i.e. a language for describing page
layout. It doesn't like separating layout from logical
structure. By contrast, HTML and CSS are designed precisely to
work cleanly with this kind of separation. Of course, if none of
your users have disabilities, and you are not
constrained by equality legislation, this may not be an
issue...
Ger is still "right": PDF is a very quick, clean, and easy way
of bringing consistent order to a chaos of multiple incompatible
legacy formats. But this is a very Faustian bargain (IMHO)...