Bug 25844

Summary: pdftoppm writes wrong resolution in metadata
Product: poppler Reporter: Kristian Nordestgaard <kristian9k>
Component: generalAssignee: poppler-bugs <poppler-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: make pdftoppm embed correct resolution

Description Kristian Nordestgaard 2010-01-01 03:09:35 UTC
Example:
$pdftoppm -r 300 file.pdf output.ppm

Appears to give the correct resolution but the metadata says that the resolution is 72x72. 

Build:
pdftoppm version 0.12.3

OS:
Linux Mint Gloria (but seems to reproduce on other OS's)
Comment 1 Adrian Johnson 2010-01-01 03:27:08 UTC
Created attachment 32387 [details] [review]
make pdftoppm embed correct resolution

Patch to make pdftoppm embed correct resolution.
Comment 2 Albert Astals Cid 2010-01-01 16:33:51 UTC
How do you get the metadata of a ppm file?
Comment 3 Kristian Nordestgaard 2010-01-01 16:38:39 UTC
Albert: 
$ identify -verbose filename.ppm
Comment 4 Albert Astals Cid 2010-01-01 17:25:55 UTC
Nowhere i could find a PPM file description specification that mentions resolution as one of the fields of the metadata so i'm thinking it's the identify program here to blame for giving an information that really is not inside the file
Comment 5 Albert Astals Cid 2010-01-01 17:32:07 UTC
I've commited Adrian's patch to embed the data when writing to png and jpeg.

As said i didn't find that PPM can have that metadata so i'm going to close the bug as fixed, if you know that PPM has that metadata please reopen the bug and point to some url that explains how to set it.
Comment 6 Kristian Nordestgaard 2010-01-03 23:48:09 UTC
Perhaps you're right about the ppm metadata, I'm not savvy enough to figure it out. Anyway, thanks for being swift in addressing this.

Best, 
Kristian

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.