RendererFactory - hardcoded list of RendererMakers

Hi I was thinking about packaging a smaller subset of FOP with only those renderers inside that are necessary (in the end I decided against it for the moment since the size benefit didn't seem to warrant it). I noticed though that the type RendererFactory has a hardcoded list of

Re: custom properties on xsl:fo element possible?

Hi Andreas, Your point is definitely valid, and I think I'm going to apply this change. If no other devs object to this, that is... (Later we may add an 'else' to that 'if', to deal with possible extension properties.) sounds good to me - other devs is that o.k. to put in? Thanks Nils

Re: custom properties on xsl:fo element possible?

hi, me again I looked into this some more and it seems to me that if PropertyList would check attribute namespaces before trying to convert them this would be handled nicely (i figured out that fobj has a reference to the responsible element so accessing its namespace is easy). I might be going

Re: System.err System.out

Hi Jeremias You sound as if using a System.out/err is a sacrilege. sorry, you're right - I should have checked the code whether the System.err/out make sense where left. Let me get back to you on that Thanks Nils

build.xml and if=junit.present

Hi could someone put this tiny patch in that makes target junit-layout-standard check if=junit.present? Otherwise build 'all' fails if no junit is present. Thanks Nils build_xml_patch.patch Description: 1591452348-build_xml_patch.patch

Re: problem with identity comparison in types inheriting from org.apache.fop.fo.FONode

Hi thanks for the quick response from everyone. Sounds reasonable to me--I think I should have done the validation that way to begin with (IIRC =='s are Not Good with Strings anyway yes, I think so as well. Since String.equals() does the == check first anyways there shouldn't be a