2010-07-31 06:52:47 +04:00
|
|
|
#
|
|
|
|
# The Python Imaging Library
|
|
|
|
# $Id$
|
|
|
|
#
|
|
|
|
# base class for raster font file parsers
|
|
|
|
#
|
|
|
|
# history:
|
|
|
|
# 1997-06-05 fl created
|
|
|
|
# 1997-08-19 fl restrict image width
|
|
|
|
#
|
|
|
|
# Copyright (c) 1997-1998 by Secret Labs AB
|
|
|
|
# Copyright (c) 1997-1998 by Fredrik Lundh
|
|
|
|
#
|
|
|
|
# See the README file for information on usage and redistribution.
|
|
|
|
#
|
|
|
|
|
|
|
|
import os
|
2013-03-07 20:20:28 +04:00
|
|
|
from PIL import Image, _binary
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
import marshal
|
|
|
|
|
|
|
|
try:
|
|
|
|
import zlib
|
|
|
|
except ImportError:
|
|
|
|
zlib = None
|
|
|
|
|
|
|
|
WIDTH = 800
|
|
|
|
|
|
|
|
def puti16(fp, values):
|
|
|
|
# write network order (big-endian) 16-bit sequence
|
|
|
|
for v in values:
|
|
|
|
if v < 0:
|
2014-05-10 08:36:15 +04:00
|
|
|
v += 65536
|
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
|
|
|
fp.write(_binary.o16be(v))
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
##
|
|
|
|
# Base class for raster font file handlers.
|
|
|
|
|
|
|
|
class FontFile:
|
|
|
|
|
|
|
|
bitmap = None
|
|
|
|
|
|
|
|
def __init__(self):
|
|
|
|
|
|
|
|
self.info = {}
|
|
|
|
self.glyph = [None] * 256
|
|
|
|
|
|
|
|
def __getitem__(self, ix):
|
|
|
|
return self.glyph[ix]
|
|
|
|
|
|
|
|
def compile(self):
|
|
|
|
"Create metrics and bitmap"
|
|
|
|
|
|
|
|
if self.bitmap:
|
|
|
|
return
|
|
|
|
|
|
|
|
# create bitmap large enough to hold all data
|
|
|
|
h = w = maxwidth = 0
|
|
|
|
lines = 1
|
|
|
|
for glyph in self:
|
|
|
|
if glyph:
|
|
|
|
d, dst, src, im = glyph
|
|
|
|
h = max(h, src[3] - src[1])
|
|
|
|
w = w + (src[2] - src[0])
|
|
|
|
if w > WIDTH:
|
2014-05-10 08:36:15 +04:00
|
|
|
lines += 1
|
2010-07-31 06:52:47 +04:00
|
|
|
w = (src[2] - src[0])
|
|
|
|
maxwidth = max(maxwidth, w)
|
|
|
|
|
|
|
|
xsize = maxwidth
|
|
|
|
ysize = lines * h
|
|
|
|
|
|
|
|
if xsize == 0 and ysize == 0:
|
|
|
|
return ""
|
|
|
|
|
|
|
|
self.ysize = h
|
|
|
|
|
|
|
|
# paste glyphs into bitmap
|
|
|
|
self.bitmap = Image.new("1", (xsize, ysize))
|
|
|
|
self.metrics = [None] * 256
|
|
|
|
x = y = 0
|
|
|
|
for i in range(256):
|
|
|
|
glyph = self[i]
|
|
|
|
if glyph:
|
|
|
|
d, dst, src, im = glyph
|
|
|
|
xx, yy = src[2] - src[0], src[3] - src[1]
|
|
|
|
x0, y0 = x, y
|
|
|
|
x = x + xx
|
|
|
|
if x > WIDTH:
|
|
|
|
x, y = 0, y + h
|
|
|
|
x0, y0 = x, y
|
|
|
|
x = xx
|
|
|
|
s = src[0] + x0, src[1] + y0, src[2] + x0, src[3] + y0
|
|
|
|
self.bitmap.paste(im.crop(src), s)
|
|
|
|
# print chr(i), dst, s
|
|
|
|
self.metrics[i] = d, dst, s
|
|
|
|
|
|
|
|
|
|
|
|
def save1(self, filename):
|
|
|
|
"Save font in version 1 format"
|
|
|
|
|
|
|
|
self.compile()
|
|
|
|
|
|
|
|
# font data
|
|
|
|
self.bitmap.save(os.path.splitext(filename)[0] + ".pbm", "PNG")
|
|
|
|
|
|
|
|
# font metrics
|
|
|
|
fp = open(os.path.splitext(filename)[0] + ".pil", "wb")
|
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
|
|
|
fp.write(b"PILfont\n")
|
|
|
|
fp.write((";;;;;;%d;\n" % self.ysize).encode('ascii')) # HACK!!!
|
|
|
|
fp.write(b"DATA\n")
|
2010-07-31 06:52:47 +04:00
|
|
|
for id in range(256):
|
|
|
|
m = self.metrics[id]
|
|
|
|
if not m:
|
|
|
|
puti16(fp, [0] * 10)
|
|
|
|
else:
|
|
|
|
puti16(fp, m[0] + m[1] + m[2])
|
|
|
|
fp.close()
|
|
|
|
|
|
|
|
|
|
|
|
def save2(self, filename):
|
|
|
|
"Save font in version 2 format"
|
|
|
|
|
|
|
|
# THIS IS WORK IN PROGRESS
|
|
|
|
|
|
|
|
self.compile()
|
|
|
|
|
|
|
|
data = marshal.dumps((self.metrics, self.info))
|
|
|
|
|
|
|
|
if zlib:
|
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
|
|
|
data = b"z" + zlib.compress(data, 9)
|
2010-07-31 06:52:47 +04:00
|
|
|
else:
|
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
|
|
|
data = b"u" + data
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
fp = open(os.path.splitext(filename)[0] + ".pil", "wb")
|
|
|
|
|
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
|
|
|
fp.write(b"PILfont2\n" + self.name + "\n" + "DATA\n")
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
fp.write(data)
|
|
|
|
|
|
|
|
self.bitmap.save(fp, "PNG")
|
|
|
|
|
|
|
|
fp.close()
|
|
|
|
|
|
|
|
|
|
|
|
save = save1 # for now
|