[Digikam-devel] [Bug 120994] New: Print preview generates HUGE postscript files

[Dik Takken]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=120994         
           Summary: Print preview generates HUGE postscript files
           Product: showfoto
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: d.h.j.takken phys uu nl


Version:           0.3.0 (using KDE KDE 3.5.0)
Installed from:    Gentoo Packages
OS:                Linux

When I open a 2 Megapixel photograph in showFoto and create a print preview, Showfoto generates 54 MB of postscript data, which takes 15 minutes to display on the screen. Not exactly practical.

When I print the same image to a Postscript file from the print dialog, showFoto generates 2 MB of postscript data which takes 30 seconds to display on the screen.

This 2 MB postscript file is 30% *smaller* than the original PNG image, and has lost a lot of details.

What is going on here?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Dik Takken]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=120994         




------- Additional Comments From d.h.j.takken phys uu nl  2006-01-29 20:36 -------
I would like to add that DigiKam (0.8.0-beta2) has the same problem.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Anders Lund]

On Sunday 29 January 2006 19:25, Dik Takken wrote:
> This 2 MB postscript file is 30% *smaller* than the original PNG image, and
> has lost a lot of details.

Maybe it uses screen resolution, which is usually < 100 dpi.

--
www: http://alweb.dk
jabber: [hidden email]
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Anders Lund]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=120994         




------- Additional Comments From anders alweb dk  2006-01-29 20:57 -------
On Sunday 29 January 2006 19:25, Dik Takken wrote:
> This 2 MB postscript file is 30% *smaller* than the original PNG image, and
> has lost a lot of details.


Maybe it uses screen resolution, which is usually < 100 dpi.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Dik Takken]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=120994         




------- Additional Comments From d.h.j.takken phys uu nl  2006-01-30 10:16 -------
Yes maybe, but why? I expect to get exactly the same result when printing to a printer or to a file.

I tried other applications, and all of them generate similar postscript files, both when sending it to the printer and when writing it to a file. One weird thing is that the applications I tried generated a wide variety of postscript file sizes.

It seems that printing an image to a postscript file involves more than simply wrapping the original bitmap into a postscript file...
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel