>>11
Oooh they won't be able to change it fap fap fap. (There are free utilities to sign your octet-streams if you'd so need. You rarely do.)
Oooh my professional marketing catalogue fap fap fap. (Breaking news: I hate that shit. The second I'm using my W3C standards-compliant browser to browse the W3C-regulated web, and I'm offered a PDF, I close the page and move on to something else.)
Oooh a PDF, it looks so serious, this company must be serious business! fap fap fap. (Breaking news: You look like a retarded luser and a lousy web designer (and "web designer" was already an insult) if you do PDFs.)
Readable as you typed it. That's the kind of faggotry I was expecting from a PDF user. Who in the fuck are you to say how should others' octet-streams be interpreted? Why do your users have to cope with your shitty Courier font or retarded 5 cm margin? I want to use User-agents that act by my side, because they run on my machine. As such, I want to enforce whatever rules I want on how to render my octet-streams, and I like to be able to do something useful with them.
And of course, I use KPDF when I have to browse a stupid PDF because some moron wants to choose my fonts and put stones in my path. If I had to use acroread I'd have suicided by now.