Web site design philosophy: .html and . pdf - Page 2

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

Re: Web site design philosophy: .html and . pdf

Quoted text here. Click to load it

Does that disabling also work in xpdf or gv, I wonder? You don't
happen to have a sample file that's been treated this way, do you?

Of course, even if it does do that in xpdf too, there's still always
the Print Screen key, followed by a run through an OCR program if
necessary - I'm just curious.


Re: Web site design philosophy: .html and . pdf

On Wed, 25 May 2005, Chris Morris wrote:

Quoted text here. Click to load it


Quoted text here. Click to load it

I think that depends on the underlying ghostview which gv uses.

Its changelog refers to "crypting support" but doesn't seem to say
explicitly whether it honours these requests from the author.  Sorry,
I don't have a sample of such a PDF to hand to try it out.

Quoted text here. Click to load it

Oh sure.

Re: Web site design philosophy: .html and . pdf

I am really grateful to those who have taken the time to make some
thoughtful and helpful contributions on this topic.

It has certainly helped clarify my views and I will return to the
discussions much better armed than before.

One remaining thought is what might be the result of putting a similar
question on a pdf forum.............

Bets wishes to all,  John Morgan

Re: Web site design philosophy: .html and . pdf

Quoted text here. Click to load it

My thoughts on this is that pdf is not designed for the www.  It is a
great format to allow people to download and print a document; it is
not a good format for reading on screen.  I also believe that it may
not (haven't really looked into it) be accessible.

I have a high speed connection as you may have as well.  That does not
mean that it is the most common.  I have many friends that still use
dialup and I'm sure there are many still with those slow connections.
I try to create pages that load quickly for those that don't have high
speed access.

Although, I do have pdf files on some of the sites I manage, it is not
by my choice but other's choices or in some instances, the only format
that I could get.  And I'm not going to go out and pay a bunch of
money for an editor that I don't want to use just to get the text out
of these documents to mark it up correctly.

Most of my arguments against pdf files are "personal taste" so I will
be watching this thread for good, valid arguments that I can use to
stop some of the pdf files from being linked in as if they were just
another page on the site.  I have no objection to a pdf being linked
in with information stating that this is a pdf for download and
printing purposes.

I have the same problem with Word and Excel files being placed on the
University site.  I keep trying to tell people that it doesn't work
everywhere; not everyone has Word and/or Excel.  Again, I have no
objection to them being linked in telling the user that it is a Word
or Excel file that can be downloaded and edited if you have that

Stan McCann "Uncle Pirate" http://stanmccann.us/pirate.html
Webmaster/Computer Center Manager, NMSU at Alamogordo
There are 10 kinds of people.
Those that understand binary and those that don't.

Re: Web site design philosophy: .html and . pdf

Quoted text here. Click to load it

There's been a recent thread on a similar subject in comp.text.pdf and
comp.sys.mac.apps under the title of

   Adding "Next Page" links to PDF document?

and elsewhere before that.  

Without repeating all the arguments there, I believe PDF is the best
general multi-purpose document storage and transmission format for
"ordinary computer users" that  is currently available or likely to be
available in the foreseeable future, for reasons I can articulate but
won't at this point -- including for making documents available from
authors to readers on the web "to download and print", as you say.

The technical capability that is still lacking, however, is making it
possible (or at least easy) for readers to look at and step through a
long multi-page PDF document on the web page by page, rather than having
to download the entire document and, in most cases, having to wait for
either a browser PDF plugin or a separate PDF reader to start up.

One good way to solve this would be software to batch-convert the
individual pages in a multipage PDF document into multiple, linked
individual HTML web pages with "Next" and "Previous" buttons overlaid on
the web pages, which the author could post on the web site along with
the PDF version.  

This is an essentially trivial problem and can be done quite easily,
now, in fact.  All of the tools to do this that I know about or have
available, however, require it be done "by hand", page by page.  

So my current situation is I'm looking for an inexpensive Mac tool to do
this efficiently and easily, or hoping that Acrobat will add this
capability sooner or later.

Re: Web site design philosophy: .html and . pdf

Quoted text here. Click to load it

Eh? That capability has been available in Adobe's implementation since
Acrobat 3, but it requires that
1) The PDF is produced using Adobe's tools. (IIRC, they
   are not licensing the related patent to third parties
   on an RF basis.)
2) The viewer is Adobe's browser plug-in.
3) The server supports HTTP 1.1 byte ranges (eg. Apache).

Usually either 1 or 2 is not true.

Henri Sivonen
http://hsivonen.iki.fi /
Mozilla Web Author FAQ: http://mozilla.org/docs/web-developer/faq.html

Site Timeline