DO NOT REPLY [Bug 11301] - most jpgs with icc profiles are rendered black in pdf

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

RE: Black images

FYI, the temporary fix was to replace org.apache.fop.image.JpegImage in fop-0.20.3 and fop-0.20.4 with the version of this class in fop-0.20.2. Now JPEGs with ICC profiles come in as before. Code questions: 1) Why isn't the org.apache.fop.fo.properties package included in the source? 2) Wh

DO NOT REPLY [Bug 11301] New: - most jpgs with icc profiles are rendered black in pdf

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

RE: javadocs

Keiron Liddle wrote: > Are you generating the javadocs from the distribution? > The problem sounds like a packaging issue. Those files have the line > endings for the OS they are checked out on. > As far as I know javadocs has always worked from cvs. I was generating the javadocs from cvs. Howev

RE: Black images

Thanks Jeremias, I will check bugzilla. Thanks a bunch for the code hints, we will try that. Darrel -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 1:34 AM To: [EMAIL PROTECTED] Subject: Re: Black images Probably. Support was added for

RE: javadocs

On Tue, 2002-07-30 at 04:28, Victor Mote wrote: > FOP Committers: > > The underlying problem was that lib/bin/antRun had DOS line endings in it (I > am running on Linux 6.1), causing it to fail when used by javadoc from > within Ant. This cannot be fixed from within the build.xml file using > fix

Re: [PATCH] CTM - PDF CTMHelper

Thanks Kevin, Patch committed. On Tue, 2002-07-30 at 13:57, Kevin O'Neill wrote: > I've separated the specific PDFRender functionality from the CTM class > and created a small utility class for the renderer to use. > > This solves the problem I was having using the CTM and PDF classes > outside

cvs commit: xml-fop/src/org/apache/fop/area CTM.java

keiron 2002/07/30 06:04:06 Modified:src/org/apache/fop/render/pdf PDFRenderer.java src/org/apache/fop/area CTM.java Added: src/org/apache/fop/render/pdf CTMHelper.java Log: separated the specific PDFRender functionality from the CTM class and created a smal

Re: FO to RTF, request for a systematic approach

On Mon, 2002-07-29 at 17:52, Bertrand Delacretaz wrote: > I'd go for 2.2 as this avoids having to maintain two RTF document libraries > (jfor and FOP) during the transition. I think that's what Chris Scott is > working on, but I haven't seen his code or design yet, hence my request to > him for

RE: [PDF Viewer] Utility request

Heh...just give me some time. We might get Java 1.1 compatibility dynamically loaded yet. ;) -Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED]] Sent: Monday, July 29, 2002 7:44 PM To: [EMAIL PROTECTED] Subject: Re: [PDF Viewer] Utility request Victor, The IAC, by this

[PATCH] CTM - PDF CTMHelper

I've separated the specific PDFRender functionality from the CTM class and created a small utility class for the renderer to use. This solves the problem I was having using the CTM and PDF classes outside of the FOP context. -k Index: org/apache/fop/area/CTM.java +AD0APQA9AD0APQA9AD0APQA9AD0AP

DO NOT REPLY [Bug 11278] - cannot build FOP - .SerializeHyphPattern cannot be found

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

DO NOT REPLY [Bug 11277] - illegal char value nnn in FO PDF driver.run()

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

DO NOT REPLY [Bug 11278] New: - cannot build FOP - .SerializeHyphPattern cannot be found

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

DO NOT REPLY [Bug 11277] New: - illegal char value nnn in FO PDF driver.run()

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

Re: any limitation to "generate-id()"

On Tue, 2002-07-30 at 11:14, Kutz Clemens (PEA-FE2/BA-T) wrote: > Good idea. How can I do this? AFAIK fop doesn't have this output option. > (I think it's a silly newbie question for the one's, who are familiar with > xalan, xerces, ... but I think I only need a sample commandline) do this: java

AW: AW: AW: any limitation to "generate-id()"

>First thing I would suggest is to generate the fo file. Then search the >file to see if the id is repeated twice (or more). Good idea. How can I do this? AFAIK fop doesn't have this output option. (I think it's a silly newbie question for the one's, who are familiar with xalan, xerces, ... but I

cvs commit: xml-fop/src/org/apache/fop/apps FOPException.java

pbwest 2002/07/30 01:51:37 Modified:src/org/apache/fop/apps Tag: FOP_0-20-0_Alt-Design FOPException.java Log: Added cvs keywords Revision ChangesPath No revision No revision 1.9.4.1 +3 -1

cvs commit: xml-fop/src/org/apache/fop/datatypes ColorSpace.java

pbwest 2002/07/30 01:49:12 Modified:src/org/apache/fop/datatypes Tag: FOP_0-20-0_Alt-Design ColorSpace.java Log: Added cvs keywords Revision ChangesPath No revision No revision 1.3.4.2 +4 -1

cvs commit: xml-fop/src/org/apache/fop/fo Properties.java

pbwest 2002/07/30 01:45:22 Modified:src/org/apache/fop/fo Tag: FOP_0-20-0_Alt-Design Properties.java Log: Completed font shorthand. Other minor changes realted to shorthand processing and verification of expression parsing. Revision ChangesPath

Re: Black images

Probably. Support was added for JPEG images to be embedded directly into PDF. Until then JPEGS were read into memory by Jimi and written to the PDF as a normal bitmap equal to the way GIFs and PNGs are written (using non-lossy ZLib compression). So probably, Jimi was able to open those JPEG images

Re: AW: AW: any limitation to "generate-id()"

Hi Kutz, First thing I would suggest is to generate the fo file. Then search the file to see if the id is repeated twice (or more). Then use the fo file as the input to fop. Note where the error occurs, id, page. Then delete everything (keeping valid xml) after that id. If possible delete everyth

AW: AW: any limitation to "generate-id()"

I tried the whole day to locate it ... I removed some other templates (not in any way related to TT) and suddenly the error disappeared. But nevertheless the removed templates are NOT responsible for the error. Because at a second time I removed other templates and kept these one I removed first a

DO NOT REPLY [Bug 11274] New: - avalon-framework.jar in distribution does not support log4j logging

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