Issue 40308 - Antialiasing When Printing
Summary: Antialiasing When Printing
Status: CLOSED DUPLICATE of issue 4748
Alias: None
Product: Draw
Classification: Application
Component: printing (show other issues)
Version: OOo 1.1.4
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: requirements
QA Contact: issues@graphics
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2005-01-10 18:56 UTC by tlknv
Modified: 2005-01-15 20:47 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description tlknv 2005-01-10 18:56:53 UTC
Hi!
    I think that antialiasing of inserted bitmaps when printing in OODraw would
be a very helpfull improvment.   Let me explain my arguments against
"http://sw.openoffice.org/servlets/ReadMsg?listName=issues&msgNo=71237".
    Althougt Gimp and others don't have antialiasing when printing, it is easy
to simulate antialiasing by resizing a picture.  At present, in order to get
antialising, the best way to go seems:
1) Run the Gimp and copy the picture from the OODraw to the Gimp through the
clipboard.
2) Resize the picture with the Gimp.
3a) Either copy the pictute from the Gimp to the OODraw throuh the clipboard,
which hangs my PC for about 5 minutes and results in a huge object in OODraw
OR
3b) copy the picture throught a temporary jpg file.

My "ABC" project which is 10MB would grow at least to 40MB. Even saving a 10MB
project takes several seconds on my PC ( HDD 10GB, UDMA33, NTFS ). Moreover,
resizing 360 pictures in my "ABC" in that way would take many hours.

Thus, I think that it would be beneficial to have antialiasing when printing to
minimize the project size and maximize effeciency, and it could be either a
project option, a picture option, or both.
           
Thank you in advance,
Boris Toloknov
Comment 1 wolframgarten 2005-01-11 07:33:17 UTC
Reassigned.
Comment 2 lohmaier 2005-01-15 20:45:26 UTC
It does not make sense to spread the arguments across various issues.
I copy your comment to issue 4748 and mark this one duplicate.

see also issue 28526

*** This issue has been marked as a duplicate of 4748 ***
Comment 3 lohmaier 2005-01-15 20:47:52 UTC
closing duplicate.