|
![](/i/fill.gif) |
Leroy Whetstone schrieb:
> clipka wrote:
>> Why is that?
>
> Let's see a long long time ago I was in the middle of a then complex
> program and I needed some critical information fast. So I found a PDF
> with what I wanted on the net. It took for ever to download. I don't
> remember what program I used to read it. But I do remember two things
> the size of that PDF was out of proportion to the information on it and
> it wasn't what I wanted. I hate it. I could have got to 10 web sites
> in the time it took me to read that one PDF.
Wait - let me get that straight: You advocate against PDF for inbuilt
help because you have bad experience with it as on-the-net help?
Okay...
>> They give a nice, clean, consistent layout on every output device
>> (including printers). HTML files, on the other hand, always have this
>> subtle "half-finished" feel to them, no matter how much effort you put
>> into their design.
>
> I rearly print anything. If I find something interesting on the net I
> download it or bookmark it.
I'm not just talking about printing - I'm talking about on-screen
appearance, too.
>> And you can easily do a full-text search on a PDF, which is always a
>> semi-hassle with HTML help files (as they typically don't come in a
>> single file).
>
> That's why I liked a will written *.hlp file's index.
That's not native part of HTML. And besides, you can do full text search
in a PDF anytime even if the author did not bother to create a good index.
Post a reply to this message
|
![](/i/fill.gif) |