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=11274.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
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
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
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=11278.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
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 an
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
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
fixcrlf
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
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. However,
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=11301.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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)
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=11301.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
14 matches
Mail list logo