Bug 99248
| Summary: | tiffsplit does not obey endian status of original file | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Johnathon Walls <johnathon.walls> |
| Component: | libtiff | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-05-19 20:04:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Filed upstream: http://bugzilla.remotesensing.org/show_bug.cgi?id=574 |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 Description of problem: Hello, I am using tiffsplit from libtiff to split a multipage tiff file into its components. The source file is in big-endian format. Running tiffsplit creates files with the little-endian format flag, but the data is still in big-endian format. In other words, only the flag has changed. Thus viewing this in display (ImageMagick) or another viewer results in data that is incorrect. Version-Release number of selected component (if applicable): libtiff-3.5.7-11 How reproducible: Always Steps to Reproduce: 1. Get a multipage big-endian tiff file 2. Run tiffsplit on it from a little-endian machine. 3. Actual Results: The new files have the little-endian file set, but the data is stored in big-endian format. Expected Results: The new files should either have the big-endian flag set and be in big-endian format, or should be in little-endian format with the little-endian flag. Additional info: I have checked the source code from libtiff.org, and this bug is present even in v3.6beta.