2010-07-31 06:52:47 +04:00
|
|
|
#
|
|
|
|
|
# The Python Imaging Library.
|
|
|
|
|
# $Id$
|
|
|
|
|
#
|
|
|
|
|
# PCD file handling
|
|
|
|
|
#
|
|
|
|
|
# History:
|
|
|
|
|
# 96-05-10 fl Created
|
|
|
|
|
# 96-05-27 fl Added draft mode (128x192, 256x384)
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) Secret Labs AB 1997.
|
|
|
|
|
# Copyright (c) Fredrik Lundh 1996.
|
|
|
|
|
#
|
|
|
|
|
# See the README file for information on usage and redistribution.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
|
2013-03-07 20:20:28 +04:00
|
|
|
from PIL import Image, ImageFile, _binary
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
|
2015-08-25 15:27:18 +03:00
|
|
|
__version__ = "0.1"
|
|
|
|
|
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
i8 = _binary.i8
|
2010-07-31 06:52:47 +04:00
|
|
|
|
2014-08-26 17:47:10 +04:00
|
|
|
|
2010-07-31 06:52:47 +04:00
|
|
|
##
|
|
|
|
|
# Image plugin for PhotoCD images. This plugin only reads the 768x512
|
|
|
|
|
# image from the file; higher resolutions are encoded in a proprietary
|
|
|
|
|
# encoding.
|
|
|
|
|
|
|
|
|
|
class PcdImageFile(ImageFile.ImageFile):
|
|
|
|
|
|
|
|
|
|
format = "PCD"
|
|
|
|
|
format_description = "Kodak PhotoCD"
|
|
|
|
|
|
|
|
|
|
def _open(self):
|
|
|
|
|
|
|
|
|
|
# rough
|
|
|
|
|
self.fp.seek(2048)
|
|
|
|
|
s = self.fp.read(2048)
|
|
|
|
|
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
if s[:4] != b"PCD_":
|
2012-10-11 07:52:53 +04:00
|
|
|
raise SyntaxError("not a PCD file")
|
2010-07-31 06:52:47 +04:00
|
|
|
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
orientation = i8(s[1538]) & 3
|
2017-01-01 15:04:59 +03:00
|
|
|
self.tile_post_rotate = None
|
2010-07-31 06:52:47 +04:00
|
|
|
if orientation == 1:
|
2017-01-01 15:59:48 +03:00
|
|
|
self.tile_post_rotate = 90
|
2010-07-31 06:52:47 +04:00
|
|
|
elif orientation == 3:
|
|
|
|
|
self.tile_post_rotate = -90
|
|
|
|
|
|
|
|
|
|
self.mode = "RGB"
|
2014-08-26 17:47:10 +04:00
|
|
|
self.size = 768, 512 # FIXME: not correct for rotated images!
|
|
|
|
|
self.tile = [("pcd", (0, 0)+self.size, 96*2048, None)]
|
2010-07-31 06:52:47 +04:00
|
|
|
|
2017-01-01 15:04:59 +03:00
|
|
|
def load_end(self):
|
|
|
|
|
if self.tile_post_rotate:
|
|
|
|
|
# Handle rotated PCDs
|
|
|
|
|
self.im = self.im.rotate(self.tile_post_rotate)
|
|
|
|
|
self.size = self.im.size
|
|
|
|
|
|
|
|
|
|
|
2010-07-31 06:52:47 +04:00
|
|
|
#
|
|
|
|
|
# registry
|
|
|
|
|
|
2015-07-04 16:29:58 +03:00
|
|
|
Image.register_open(PcdImageFile.format, PcdImageFile)
|
2010-07-31 06:52:47 +04:00
|
|
|
|
2015-07-04 16:29:58 +03:00
|
|
|
Image.register_extension(PcdImageFile.format, ".pcd")
|
