Search found 5 matches
- 2011-12-16T09:46:47-07:00
- Forum: Developers
- Topic: File format detection problem
- Replies: 5
- Views: 11530
Re: File format detection problem
I'm trying only with dynamic build. Coder path is what you gave, and, as I mentioned at the beginning, most formats are detected properly. The problem exists only for extensions that are supported by other coders, i.e. CIN (coders/cin.c), CCI (coders/bmp.c), RGB (coders/rgb.c).
- 2011-12-16T05:06:40-07:00
- Forum: Developers
- Topic: File format detection problem
- Replies: 5
- Views: 11530
Re: File format detection problem
Thanks for the answer. My coder uses module name "FAIL" (First Atari Image Library), and the function is "IsFAIL". However, it doesn't get called (neither do analogous functions in other coders, like IsBMP or IsCIN), at least when using display. Using explicit format as you suggested also does not ...
- 2011-12-15T10:58:15-07:00
- Forum: Developers
- Topic: File format detection problem
- Replies: 5
- Views: 11530
File format detection problem
Hi, I'm developing an ImageMagick coder for decoding Atari XL/XE images (sources and example images are at http://fail.sourceforge.net/ ), which handles about 50 different (sometimes rare) image formats. Some file name extensions that are supported by FAIL coder (they are registered in the coder.xml ...
- 2011-04-16T06:32:55-07:00
- Forum: Bugs
- Topic: Custom coders don't compile on Linux.
- Replies: 1
- Views: 3723
Custom coders don't compile on Linux.
MagickCoderKit and any other custom coder based on it don't compile on Linux because of missing header files (at least). ./configure passes without problems, but make does not: MagickCoderKit-1.0.0$ make depbase=`echo mgk.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ /bin/bash ./libtool --tag=CC --mode ...
- 2011-04-04T14:29:22-07:00
- Forum: Bugs
- Topic: coder.xml does not conform to DTD which it contains itself.
- Replies: 1
- Views: 3521
coder.xml does not conform to DTD which it contains itself.
Default coder.xml file in 6.6.9-3-Q16 windows installation does not conform to DTD which it contains itself. There's a <!ELEMENT codermap (coder)+> declaration, which states that at least one "coder" element is required inside "codermap" element. However, there's no coders (besides three commented ...