Issue 96097

Summary: Export as bmp ignores user definded resolution
Product: Draw Reporter: wolle2000 <wuhlig>
Component: programmingAssignee: sven.jacobi
Status: CLOSED DUPLICATE QA Contact: issues@graphics <issues>
Severity: Trivial    
Priority: P3 CC: issues, rb.henschel
Version: OOO300m9   
Target Milestone: OOo 3.1   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
file exported with 2.4
none
File exported with 3.0 none

Description wolle2000 2008-11-11 14:42:06 UTC
If you export a drawing to bmp-format, user defined resolution (150, 300 or 
600) are ignored. The exported bitmap will always have 96 dpi.

This was different in previous versions and thus is a regression.
Comment 1 wolframgarten 2008-11-11 14:52:23 UTC
Reproducible. Reassigned.
Comment 2 wolframgarten 2008-11-11 14:53:55 UTC
Created attachment 57878 [details]
file exported with 2.4
Comment 3 wolframgarten 2008-11-11 14:54:30 UTC
Created attachment 57879 [details]
File exported with 3.0
Comment 4 wolframgarten 2008-11-11 14:55:11 UTC
IrfanView does not show dpi for the 2nd file exported with 3.0.
Comment 5 Regina Henschel 2008-11-11 18:02:37 UTC
@wolle2000: In which version was it correct? As far as I know, it has been wrong
since ever. See discussion and solutions in issue 4499.
Comment 6 wolle2000 2008-11-11 19:21:32 UTC
@Regina
I tried it with the English version of 2.0 (shame, so old!) and in the Dutch 
version 2.3. I have both as portable versions just in case I have to look 
something up in the UI.
Comment 7 Regina Henschel 2008-11-11 20:48:02 UTC
OOo3.0 doesn't set a dpi-info, that I see too. But it is not worth to correct
it, because the logic itself is wrong. Draw a rectangle in 2" x 0.5" and export
is with 300dpi. This should result in 600 x 150 pixels, but has never been. And
that has to be corrected.
Comment 8 wolle2000 2008-11-12 09:51:15 UTC
Hi Regina,
you're right. I hadn't even payed attention to this before ;)
Comment 9 sven.jacobi 2009-01-07 13:47:47 UTC
As regina said, this issue is something that should be handled in issue 4499, so
I set this issue double to 4499

*** This issue has been marked as a duplicate of 4499 ***
Comment 10 Mechtilde 2009-07-12 18:00:04 UTC
duplicate -> closed