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=9145.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=9113.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Sorry for crossposting, but the problem occures, if I try to get the Parser
from FOInputHandler in the junit test case. inputHandler.getParser() throws
a FOPException:
org.apache.fop.apps.FOPException: org.apache.xerces.parsers.SAXParser is not
a SAX driver
at
Hi,
Comment:
Good idea.
Suggestion:
It probably wouldn't hurt to go ahead (on the page) and
answer the inevitable, Can you please tell me when to
expect the release FOP0.20.4|FOP10 DR1 announced
on your status page?
The same answer that would otherwise appear here,
that is.
Complaint:
My
Hi,
just for information, for anyone, who gets in the same trouble!
I've found the problem with the obsoleter SAX-2 implementation. In my
classpath are 2 different xml-api's (I know about that, but I cannot avoid
that, because of foreign parts in our app are delivered with this api
contained in
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=6997.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=6997.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=6997.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Keiron Liddle schrieb:
One reason for waiting was to see how it would work. There are some user
issues that have popped up but nothing too serious. It would be good to
know how people should deal with this situation.
A new patch would certainly help. Christian might be able to say more
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-05-16/xml-fop.html
Buildfile: build.xml
init-avail:
init-filters-xalan2:
[copy] Copying 1
Hy Keiron.
I suppose you have an SCM problem with Batik class. The actual release
delivered with FOP last build xml-fop_20020516103601.tar.gz
As you wrote PDFGraphics2D.java, I send you that mail. As I'm not very
graphics today, I just wrote this empty method
public VolatileImage
These notes apply to fo:external-graphic under FOP 0.20.1:
o FOP images are kept as XObjects until the end of job, because
- the image is written to the output file
- and the complete image object is added to the XObjects vector in order to
build the ressource dictionary at the
I have found the problem and worked out its repair.
The modified code is attached below.
The problem stems from a bug in java's handling of drawing of
AttributedStrings when a font attribute is specified. Bug parade
#4650042 describes a similar problem unique to jdk 1.4, but
makes also
Keiron Liddle schrieb:
Hi,
Since a new beta of batik has been released I think we can go with this
for the next release.
I will put the new batik into cvs and update the code to work with it.
Is it possible to make Fop work without batik.jar ? (of course if no svg
is used)
Keiron.
[EMAIL PROTECTED] schrieb:
I've had a couple folks ask me for the modified code so the proper character
encoding is returned on the toString().getBytes()
is US-ASCII. This is cool that other people besides me need this.
[..]
I downloaded this snapshot xml-fop_20020515162132 and I don't see
Keiron Liddle schrieb:
Hi,
I added some status info to the website. So hopefully this will answer
Cool
some peoples questions (I'm sure they will still want to know more
things that are unknown).
Sure ;-)
Any comments, complaints, suggestions? (apart from my poor spelling!)
Maybe put
Hello Christian,
yes, it is possible to run FOP without batik, but you have to change the
source.
You have to remove all the imports to packages svg... and kick out all the
references to classes having
to do with svg.
In fact we did this and we have a working version based on FOP 0.20.3
running
GALLO Jean-Claude wrote:
I suppose you have an SCM problem with Batik class. The actual release
delivered with FOP last build xml-fop_20020516103601.tar.gz
...
But running result build, I get the following.
..
WARNING: child LM not a BPLayoutManager:
18 matches
Mail list logo