I think your observations are good ones, Adam, but you may not find
the data you're seeking. I've looked for it, too. I know your
frustration.
In the absence of information about your specific use case, some food
for thought:
* For the inexperienced user, well-formed HTML/XHTML is designed to
do
Thanks for the input everyone.
Jeff:
I completely realize that Adobe has made a lot of effort to include
things like accessibility, and I commend them for it.
The issues I've observed though, is that for a general audience,
expectancy changes when users are presented with a PDF on the web,
they
Keep in mind that you might be able to get both.
If the source is written in DITA XML, you can output topics in
whatever combination you find necessary, and in multiple formats,
including HTML and PDF.
The barrier to general use is significant, since you have to put in
place special software
Adam:I myself believe very strongly that PDFs have a certain place
on the web and that mimicking web functionality is not it, but the
more ammo I go in with the better.
I accept that pov but until you've exported a
sketch/wireframe/interactive wireframe to pdf and sent it to a client
or used it
I am working to make the case to some of my company's IT professionals
that the decision to go with PDF delivery for certain reports rather
than HTML is a bad one.
I've read all of Nielson's articles on PDFs as well as rebuttals by
various individuals (where they only seem to point out that PDFs
Great question!
The decision _may not_ be a bad one, actually, depending on the
specifics. A lot of it depends on how you've set up the PDF, which
may be somewhat inaccessible by default. Adobe has made some
significant effort to help with these concerns, but it's something
many people don't
