Bug 32817 - pcx image format not supported
Summary: pcx image format not supported
Status: RESOLVED FIXED
Alias: None
Product: kview
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Matthias Kretz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-23 00:33 UTC by al867
Modified: 2013-08-21 06:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description al867 2001-09-23 00:29:08 UTC 
(*** This bug was imported into bugs.kde.org ***)

Package:           kview
Version:           KDE 2.2.1 
Severity:          wishlist
Installed from:    RedHat RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

PCX image format seems to be not supported by kview (and kview-part). When opening a pcx image in kview no image is displayed and no warning/error message is generated.

(Submitted via bugs.kde.org)
Comment 1 Gaute Hvoslef Kvalnes 2003-01-30 20:05:18 UTC 
I believe PCX support is important because Lotus Notes seems to use PCX when sending image attachments in emails.
Comment 2 Maksim Orlovich 2003-01-31 01:55:21 UTC 
Nadeem, you have this at least partly implemented, right?
Comment 3 Nadeem Hasan 2003-01-31 17:33:52 UTC 
Subject: Re:  pcx image format not supported         

Quoting Maksim Orlovich <mo002j@mail.rochester.edu>:
> Nadeem, you have this at least partly implemented, right?

Hey SadEagle,

The PCX plugin fully supports reading and writing (1, 4, 8, 24bpp) PCX images.
So I would say its fully implemented.

--
Nadeem Hasan
nhasan@nadmm.com
http://www.nadmm.com/

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
Comment 4 Nadeem Hasan 2003-01-31 17:35:43 UTC 
*** Bug has been marked as fixed ***.
Comment 5 Felix Michel 2013-08-21 06:19:05 UTC 
*** Bug 323818 has been marked as a duplicate of this bug. ***