I don't think there's a considerable difference. The identity
transformer in Xalan-J is essentially a SAXParser and a 1:1
piping-through of SAX events. It's just a bit more setup code for the
Transformer variant, I think. The choice about what to use is really
personal preference. I simply think
Sorry for the delay.
On 16.07.2004 19:00:25 Victor Mote wrote:
Jeremias Maerki wrote:
Making these parts into separate components is in line with
what I have in mind when can talk about a shared repository
between Batik and FOP. I hope I can take a good look into
Good. I think it
I agree; however we are none the worse off for Simon's
SAXParser example, and we even got a more powerful
DefaultHandler object in our API as a bonus.
Glen
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
I simply think that the
Transformer pattern is very
universal and quite easy to use and
Jeremias Maerki wrote:
I'm simply thinking that adding statics is a lot easier than
removing them again. I usually create non-static classes and
create singletons around them if necessary or convenient.
That's basically it.
One of the main purposes of
FontServer was to share as much
Chris, Jeremias, and anyone else looking at FOray code:
I have created the following branch in FOray's CVS that you will want to use
for your evaluation:
rel_0_1_branch
I have started some other changes in the root that should probably be
evaluated separately.
I apologize for the
Fopsters,
I have been discussing with Jeremias offline the appropriateness or
otherwise of my being on the XML Graphics PMC. On reflection, I had
some reservations, and I have decided to withdraw my nomination for the
XML Graphics PMC, on the understanding that I will continue to take a
keen
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=25248.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
