Bug 162089 - kfile_pdf handler assumes KPDF_FORCE_DRM is set
Summary: kfile_pdf handler assumes KPDF_FORCE_DRM is set
Status: RESOLVED INTENTIONAL
Alias: None
Product: kfile-plugins
Classification: Applications
Component: pdf (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-14 14:36 UTC by Robert Millan
Modified: 2008-06-10 15:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
patch (782 bytes, patch)
2008-05-14 14:37 UTC, Robert Millan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Millan 2008-05-14 14:36:44 UTC
Version:            (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages

Informational message in kfile_pdf handler seems to assume Digital Restriction Management is in effect, but most likely it isn't.
Comment 1 Robert Millan 2008-05-14 14:37:12 UTC
Created attachment 24761 [details]
patch
Comment 2 Pino Toscano 2008-05-14 18:54:29 UTC
I don't see the relation between KPDF and the kfile_pdf plugin.
Futhermore, this changes how the details of the document are shown to the user, why would you want that?
Comment 3 Robert Millan 2008-05-14 19:10:44 UTC
This isn't obvious from the function names exported by libpoppler, but okToPrint(), okToCopy() etc are only meaningful in the context of Digital Restriction Management.

In the non-DRM world, it isn't conceiveable that you can print a document but you can't copy from it, etc.  So they're basically reporting information to the user about properties of a document that don't really exist (at the least, not in the way they're presented).
Comment 4 Albert Astals Cid 2008-05-14 20:25:32 UTC
KPDF and kfile_pdf plugin have nothing to do with eachother, other than dealing with pdf and being on kdegraphics. 

The information is correct, technically you are not allowed to print it, that some readers like kghostview or kpdf set to ignore DRM let you do it does not mean you can always do it.

In my opinion, not a bug.
Comment 5 Robert Millan 2008-05-14 20:34:58 UTC
> KPDF and kfile_pdf plugin have nothing to do with eachother, other than dealing with pdf and being on kdegraphics. 

And the fact that they share the same KPDF_FORCE_DRM macro definition.  Which indicates the setup kpdf received in the same environment, thus with the same policy.
Comment 6 Albert Astals Cid 2008-05-14 20:43:28 UTC
They only share it with your patch ;-) Not in current code.

I understand that you think "if i'm compiling kpdf with the 'do not use drm' option, why should i get drm entries on kfile_pdf plugin?"

The fact is that even if it may seem strange, there is people using other pdf readers than kpdf and the kfile_pdf plugins is there to give information about the file, not information about the file when opened with kpdf.
Comment 7 Robert Millan 2008-05-14 20:54:51 UTC
What?  All pdf readers I know are DRM-free.  Oh wait :-)

Ok, but please reconsider this when Adobe's reader is completely abandoned.  Thanks ;-)
Comment 8 Pino Toscano 2008-06-09 15:05:23 UTC
The information provided by the kfile_pdf plugin are just that, information, nothing else from the point of view of the plugin. They are not used in any other way, but just shown to the user.
Just like you feel wrong in hiding information (just like what DRM does), I feel wrong in hiding information about the document to the user.
The fact that you like or not this information, is a totally different matter, but purely irrelevant for the plugin.
Comment 9 Robert Millan 2008-06-10 15:44:50 UTC
Pino, I agree with what you said.  But the information it is displaying leads the user to believe this document cannot be printed, which isn't true most of the time.  It is misleading.

An accurate description of the information would be, that the author of this document pretended to restrict you from printing it, but this will only have an effect if you're not using the free PDF viewer that came with KDE.

I don't know how to summarize this, but certainly "cannot be printed" doesn't describe reality.