Pino Toscano <p...@kde.org> writes: > Because Okular by default respect the PDF format. > Why it is there? Exactly to give you the freedom to choose, to respect > both the ideas of people who just shiver at listening the "DRM" word, > and people who make a use of that PDF "feature".
Note, though, that “people who make use of that feature” are *not* the ones in control of the computer, but the ones who create the PDF. It is the user/administrator of the Debian operating system (and, in this case, the Okular program) whose needs should be foremost, *not* the needs of whoever flipped a bit in the incoming PDF file. > If tomorrow a corporate person complains that Okular does not respect > the PDF format in that sense and that they cannot make use of it > because of that, what should I tell them? They would be right. For this reason, I agree with Josselin earlier in the thread that the ability should remain. But certainly the default should be “don't impose any restrictions not in the interest of the computer's nominal controller”. Indeed, imposing such restrictions should be a hidden option since it's not in the interest of *any* user who isn't already under some external constraint to enable it. > Look, having the "power of developers" does not imply developers > should feel like crackers, disabling restrictions just because they > can or in the name of some "freedom". Expressly imposing restrictions just because some incoming data says so is pretty close to a deliberate misdesign. Fixing that misdesign is not “cracking”. -- \ “Whatever a man prays for, he prays for a miracle. Every prayer | `\ reduces itself to this: “Great God, grant that twice two be not | _o__) four.”” —Ivan Turgenev | Ben Finney
pgpf0XmQoiqdq.pgp
Description: PGP signature