2010-07-31 06:52:47 +04:00
|
|
|
#
|
|
|
|
# The Python Imaging Library
|
|
|
|
# $Id$
|
|
|
|
#
|
|
|
|
# WMF stub codec
|
|
|
|
#
|
|
|
|
# history:
|
|
|
|
# 1996-12-14 fl Created
|
|
|
|
# 2004-02-22 fl Turned into a stub driver
|
|
|
|
# 2004-02-23 fl Added EMF support
|
|
|
|
#
|
|
|
|
# Copyright (c) Secret Labs AB 1997-2004. All rights reserved.
|
|
|
|
# Copyright (c) Fredrik Lundh 1996.
|
|
|
|
#
|
|
|
|
# See the README file for information on usage and redistribution.
|
|
|
|
#
|
2016-11-27 19:03:51 +03:00
|
|
|
# WMF/EMF reference documentation:
|
|
|
|
# https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-WMF/[MS-WMF].pdf
|
|
|
|
# http://wvware.sourceforge.net/caolan/index.html
|
|
|
|
# http://wvware.sourceforge.net/caolan/ora-wmf.html
|
2010-07-31 06:52:47 +04:00
|
|
|
|
2016-11-26 03:05:56 +03:00
|
|
|
from __future__ import print_function
|
|
|
|
|
2017-01-17 16:22:18 +03:00
|
|
|
from . import Image, ImageFile
|
|
|
|
from ._binary import i16le as word, si16le as short, i32le as dword, si32le as _long
|
|
|
|
|
|
|
|
|
2010-07-31 06:52:47 +04:00
|
|
|
|
2015-08-25 15:27:18 +03:00
|
|
|
__version__ = "0.2"
|
|
|
|
|
2010-07-31 06:52:47 +04:00
|
|
|
_handler = None
|
|
|
|
|
2012-10-17 07:54:38 +04:00
|
|
|
if str != bytes:
|
|
|
|
long = int
|
|
|
|
|
2014-08-26 17:47:10 +04:00
|
|
|
|
2010-07-31 06:52:47 +04:00
|
|
|
def register_handler(handler):
|
2016-09-24 12:10:46 +03:00
|
|
|
"""
|
|
|
|
Install application-specific WMF image handler.
|
|
|
|
|
|
|
|
:param handler: Handler object.
|
|
|
|
"""
|
2010-07-31 06:52:47 +04:00
|
|
|
global _handler
|
|
|
|
_handler = handler
|
|
|
|
|
|
|
|
if hasattr(Image.core, "drawwmf"):
|
|
|
|
# install default handler (windows only)
|
|
|
|
|
2015-05-26 17:07:21 +03:00
|
|
|
class WmfHandler(object):
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
def open(self, im):
|
|
|
|
im.mode = "RGB"
|
|
|
|
self.bbox = im.info["wmf_bbox"]
|
|
|
|
|
|
|
|
def load(self, im):
|
2014-08-26 17:47:10 +04:00
|
|
|
im.fp.seek(0) # rewind
|
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
|
|
|
return Image.frombytes(
|
2010-07-31 06:52:47 +04:00
|
|
|
"RGB", im.size,
|
|
|
|
Image.core.drawwmf(im.fp.read(), im.size, self.bbox),
|
|
|
|
"raw", "BGR", (im.size[0]*3 + 3) & -4, -1
|
|
|
|
)
|
|
|
|
|
|
|
|
register_handler(WmfHandler())
|
|
|
|
|
|
|
|
#
|
|
|
|
# --------------------------------------------------------------------
|
|
|
|
# Read WMF file
|
|
|
|
|
|
|
|
def _accept(prefix):
|
|
|
|
return (
|
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
|
|
|
prefix[:6] == b"\xd7\xcd\xc6\x9a\x00\x00" or
|
|
|
|
prefix[:4] == b"\x01\x00\x00\x00"
|
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 Windows metafiles.
|
|
|
|
|
|
|
|
class WmfStubImageFile(ImageFile.StubImageFile):
|
|
|
|
|
|
|
|
format = "WMF"
|
|
|
|
format_description = "Windows Metafile"
|
|
|
|
|
|
|
|
def _open(self):
|
|
|
|
|
|
|
|
# check placable header
|
|
|
|
s = self.fp.read(80)
|
|
|
|
|
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[:6] == b"\xd7\xcd\xc6\x9a\x00\x00":
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
# placeable windows metafile
|
|
|
|
|
|
|
|
# get units per inch
|
|
|
|
inch = word(s, 14)
|
|
|
|
|
|
|
|
# get bounding box
|
2014-08-26 17:47:10 +04:00
|
|
|
x0 = short(s, 6)
|
|
|
|
y0 = short(s, 8)
|
|
|
|
x1 = short(s, 10)
|
|
|
|
y1 = short(s, 12)
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
# normalize size to 72 dots per inch
|
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
|
|
|
size = (x1 - x0) * 72 // inch, (y1 - y0) * 72 // inch
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
self.info["wmf_bbox"] = x0, y0, x1, y1
|
|
|
|
|
|
|
|
self.info["dpi"] = 72
|
|
|
|
|
2016-11-19 03:19:43 +03:00
|
|
|
# print(self.mode, self.size, self.info)
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
# sanity check (standard metafile header)
|
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[22:26] != b"\x01\x00\t\x00":
|
2010-07-31 06:52:47 +04:00
|
|
|
raise SyntaxError("Unsupported WMF file format")
|
|
|
|
|
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
|
|
|
elif dword(s) == 1 and s[40:44] == b" EMF":
|
2010-07-31 06:52:47 +04:00
|
|
|
# enhanced metafile
|
|
|
|
|
|
|
|
# get bounding box
|
2016-11-27 19:03:51 +03:00
|
|
|
x0 = _long(s, 8)
|
|
|
|
y0 = _long(s, 12)
|
|
|
|
x1 = _long(s, 16)
|
|
|
|
y1 = _long(s, 20)
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
# get frame (in 0.01 millimeter units)
|
2016-11-27 19:03:51 +03:00
|
|
|
frame = _long(s, 24), _long(s, 28), _long(s, 32), _long(s, 36)
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
# normalize size to 72 dots per inch
|
|
|
|
size = x1 - x0, y1 - y0
|
|
|
|
|
|
|
|
# calculate dots per inch from bbox and frame
|
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
|
|
|
xdpi = 2540 * (x1 - y0) // (frame[2] - frame[0])
|
|
|
|
ydpi = 2540 * (y1 - y0) // (frame[3] - frame[1])
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
self.info["wmf_bbox"] = x0, y0, x1, y1
|
|
|
|
|
|
|
|
if xdpi == ydpi:
|
|
|
|
self.info["dpi"] = xdpi
|
|
|
|
else:
|
|
|
|
self.info["dpi"] = xdpi, ydpi
|
|
|
|
|
|
|
|
else:
|
|
|
|
raise SyntaxError("Unsupported file format")
|
|
|
|
|
|
|
|
self.mode = "RGB"
|
|
|
|
self.size = size
|
|
|
|
|
|
|
|
loader = self._load()
|
|
|
|
if loader:
|
|
|
|
loader.open(self)
|
|
|
|
|
|
|
|
def _load(self):
|
|
|
|
return _handler
|
|
|
|
|
|
|
|
|
|
|
|
def _save(im, fp, filename):
|
|
|
|
if _handler is None or not hasattr("_handler", "save"):
|
|
|
|
raise IOError("WMF save handler not installed")
|
|
|
|
_handler.save(im, fp, filename)
|
|
|
|
|
|
|
|
#
|
|
|
|
# --------------------------------------------------------------------
|
|
|
|
# Registry stuff
|
|
|
|
|
|
|
|
Image.register_open(WmfStubImageFile.format, WmfStubImageFile, _accept)
|
|
|
|
Image.register_save(WmfStubImageFile.format, _save)
|
|
|
|
|
|
|
|
Image.register_extension(WmfStubImageFile.format, ".wmf")
|
|
|
|
Image.register_extension(WmfStubImageFile.format, ".emf")
|