Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc 3.4.1 OS: Linux Kparts plugin shows PDF files not Anti Aliased inside Konqueror while it does show Anti Aliased when KPDF is loaded standalone. Would be nice to have this one fixed. AA support is enabled on my system.
Which version? Is this using KDE from HEAD branch of CVS?
Oh ? I was refering to KDE CVS HEAD (as selected when have entered this bug with bugs.kde.org). Sorry if it was unclear.
Ali: Can you add screenshots? If publicly available post a link to the pdf docuemnt too.
Sure, Well I can't make the PDF document public since it's a private job application that I wrote but every other document from the NET show the same behaviour so I searched for this one. http://www.researchineurope.org/policy/patentdirltr.pdf
Created attachment 7871 [details] Demonstration PDF, one time in KParts one time standalone.
Oh wait, I just realized that within KParts it shows KGhostview... Why this ? It should show KPDF instead. Is it possible to change the Mimetype for this and commit a change to KDE CVS ? I didn't touch anything here so I wonder why KGhostview comes up.
To change the associated kpart go to kcontrol -> Components -> file Associations -> pdf -> Embedded tab and there change KGhostview part to KPDF part. Note: All that names are translations Catalan -> English so the actual names may be a bit different. To change that in whole kde we must discuss with other kde people if we really prefer kpdf or kghostview to view pdf.
Yes, I am aware of that and changed the association via file associations already. I think it would be a very good and promising idea to bring this up for conversation on the mailinglist. I assume that KPDF was changed to KGhostview because no one was maintaining KPDF for quite some time (which I have read somewhere). Would be a huge benefit to have the default be KPDF again. And thanks for the work on it.
We will bring up the discussion of which pdf viewer we want when KDE 3.4 is nearer than now, for now let's concetrate on code :-D For the bug can i close it as it seems it is not a kpdf error?
Yes, let's close it.