Issue 18 in pylibtiff: TIFF.write_image writes incorrect ORIENTATION tag

[pyli...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 18 by fluid.th...@gmail.com: TIFF.write_image writes incorrect
ORIENTATION tag
http://code.google.com/p/pylibtiff/issues/detail?id=18

What steps will reproduce the problem?
1. Write image data using TIFF.open(filename, 'w').write(data)

What is the expected output? What do you see instead?

The created diff file has orientation 6 (

The offending lines are in libtiff_ctypes.py, lines 403, 420, and 453:

self.SetField(TIFFTAG_ORIENTATION, ORIENTATION_RIGHTTOP)

The correct value is 1, not 6. See, for example,

http://www.awaresystems.be/imaging/tiff/tifftags/orientation.html

Note also that simply not setting the orientation tag also results in a
correct image.

What version of the product are you using? On what operating system?

pylibtiff 0.1svn, Linux Ubuntu 10.10

Please provide any additional information below.

[pyli...@googlecode.com]

Comment #1 on issue 18 by fluid.th...@gmail.com: TIFF.write_image writes

incorrect ORIENTATION tag
http://code.google.com/p/pylibtiff/issues/detail?id=18

Correction: the offending function call is:

TIFF.open(filename, 'w').write_image(data)

[pyli...@googlecode.com]

Comment #2 on issue 18 by eric.p...@gmail.com: TIFF.write_image writes

incorrect ORIENTATION tag
http://code.google.com/p/pylibtiff/issues/detail?id=18

Please note that the patch provided in issue 21 should contain a fix for
this issue.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[pyli...@googlecode.com]

Comment #3 on issue 18 by eric.p...@gmail.com: TIFF.write_image writes

[pyli...@googlecode.com]

Updates:
Status: Done

Comment #4 on issue 18 by pearu.peterson: TIFF.write_image writes incorrect
ORIENTATION tag
https://code.google.com/p/pylibtiff/issues/detail?id=18

Patch from issue 21 has been applied to svn.