DO NOT REPLY [Bug 13866] New: - [PATCH] Support for CCITT encoding of TIFF images in PDF output

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13866>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13866

[PATCH] Support for CCITT encoding of TIFF images in PDF output

           Summary: [PATCH] Support for CCITT encoding of TIFF images in PDF
                    output
           Product: Fop
           Version: 0.20.4
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: images
        AssignedTo: fop-dev@xml.apache.org
        ReportedBy: mm@arcus.com.au


Just realized that patches should go into BugZilla
==================================================

Finally got around to do the patch.

Its against the current version from the maintenance branch.

The patch, apart from adding support for CCFFilters for TIFF images in PDF 
files, attempts a few other fixes:

1. The FopImageFactory had code with needed explicit uncommenting to support 
JAI. This is now done dynamically, no source editing required, based on a 
ClassForName test if JAI is present.

2. The build scripts have been changed to include the jai_codec and jai_core 
jars in the class path. As for Jimi, which was already included, it doesn't 
matter if they are not there. This means to build fop with JAI support the only 
action required is to put the JAI jars into the lib directory (same as for 
Jimi).

3. A CCITT Group 4 encoded TIFF file has been added to the docs/graphics 
directory and the docs/examples/fo/image.fo file has been modified to include 
this TIFF file as an external graphic. Note: This graphic will not display if 
fop is compiled without JAI support however a valid PDF file will still be 
produced.

4. The FopImageFactory has been modified to now, hopefully correctly, resolve 
URIs relative to the baseDir configuration parameter. The previous 
implementation of resolving relative URIs was broken, especially with respect 
to the current test cases in docs/examples/fo.

5. The Fop ant task has been modified to set the baseDir parameter given to it. 
The previous implementation accepted the baseDir parameter but never set it in 
the Configuration. This caused the automatic builds of the example suite to 
fail (with respect to resolving relative URIs in external-graphic tags).

6. The shell script to make the example suite was also modified to include the 
JAI jars.

I hope the attached file with the diffs and the new files is in the correct 
format and one of the committers finds the time to look at it and if acceptable 
include it into the upcoming 20.5 release.

Unfortunately some of the diffs are pretty big because my text editor changed 
the line endings to LFs and tabs to spaces as per published Apache conventions.

And a final note: Would it be possible to include logkit-1.0.jar in the 
distribution? Without it, or another avalon compatible logger, the scripts for 
building the examples or running the tests don't work. Its just nicer if 
things "work out of the box".

Manuel

-----Original Message-----
From: Jeremias Maerki [mailto:dev.jeremias@greenmail.ch]
Sent: Tuesday, 13 August 2002 12:54
To: fop-dev@xml.apache.org
Subject: Re: Encoding Filters(Formally Re: Hope this helps-
RunLengthEncod eFilter)


Manuel

Looks like I missed this. At least, I can say that I could profit from
CCITT group 4 because we have a project at work where we have to include
several different monochrome images in a lot of documents. So this may
decrease file size when compared to the FlateEncodeFilter. If it's
dependent on JAI, so be it. That just means we have to make it optional,
somehow. Want to send a patch?


On 13.08.2002 04:49:56 Manuel Mall wrote:
> I did (sort of) integrate the CCITT/TIFF compression based on JAI earlier
> this year. See http://marc.theaimsgroup.com/?l=fop-dev&m=101125782918974&w=2
> 
> But nobody seemed to be interested at the time.

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org