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=9570.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I'd like to make some research this evening (CET) to provide some more
thought-through comments. In the meantime I'd like to point out a few
things:
- Thanks, Jörg, for starting this. I'm in favor of redesigning the API.
- I don't believe we will be able to finalize the API this week. There's
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=7063.
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=7131.
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=7146.
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=635.
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=7200.
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=7323.
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=7903.
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=8023.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hello,
I have an application that producesPDF as
output.
When I run it through FOP 0.20.3 I get this
error:
org.apache.fop.apps.FOPException:
org.apache.xml.dtm.DTMException: No more DTM IDs are available
Anyone have any idea why I am getting this
error?
Thanks,
József Koncsek
[EMAIL
I will start with some comments on caching since I have looked at this.
There is another type of caching needed. Caching objects in memory to
disk (or other medium) to avoid excess memory growth. The obvious case
is when there are lots of forward references on every page. The page can
be saved
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=8990.
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=4510.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
The original exception comes from Xalan. DTM is a Xalan thing. Try
running your stylesheet with Xalan alone leaving FOP for the moment. See
if the problem persists. You may find hints on the Xalan pages or you
can try to switch to another version of Xalan. Good luck!
I have an application that
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=9583.
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=5469.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Some remarks:
Jeremias Maerki wrote:
- I'm not sure if we should change the API in the maintenance branch.
Breaking backwards-compatibility produces and deprecating old
interfaces and classes is not so popular, usually.
Of course, that's why I thought of keeping the old interface for
I'd actually like to hear more about this. I like the idea at first glance...it seems
like it might result in a cleaner codebase...but I really would like to hear more on
how MIME-types could be used to replace the subclassing technique. Jeremias, are you
suggesting a monolithic class for
Hi all,
as you probably have noticed the date for the release candidate has been
reached but I would like to see the following things done for 0.20.4:
(new target date: next weekend ;-)
- fix broken PDFs
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9054
ewitness - Ben Fowler wrote:
[..]
A 'proper' XML editor/IDE would be very useful for examining XML
and FO files, parsing and validating them and processing with
XSLT.
Is there already a project in existence that does this?
Jedit (www.jedit.org) seems to do is (and a lot more ..)
I just
The MIME types for renderer selection is not a new idea. But I don't
know anymore when it came up for the first time.
The idea is to eliminate the hardcoded references to the renderers. That
way it's easier to include new ones or special-purpose renderers
subclassed from existing ones. Instead
I've got Oleg Tkachenko's image renderer on my tasklist. The problem is
time, as usual. I'm going to try to do this this week. I'll update you,
if I manage to do any items on your list.
There's also this one:
- Improvements on PS renderer (Huikang Xu)
23 matches
Mail list logo