The warning is an indicator that there are still a few things in RTF
support that need fixing.
So is there someone who owns this class? How long has it been
out-of-sync - that is, is it in the same condition as TXTRenderer?
Also, while this is probably not the correct forum for this question,
On Sep 20, 2005, at 17:40, Matthew L Daniel wrote:
Hi Matthew,
The least this would do is avoid a number of unnecessary calls to
instanceof.
You're on the right track, and maybe that switch impl would be an
80/20 win over the cost of the Right Way. But that huge if-instance
case
is exactly
TableBody et al
The warning is an indicator that there are still a few things in RTF
support that need fixing.
So is there someone who owns this class? How long has it been
out-of-sync - that is, is it in the same condition as TXTRenderer?
Also, while this is probably not the correct forum
ignoring TableBody et al
On Sep 20, 2005, at 00:28, Matthew L Daniel wrote:
I am using trunk code and with an input FO that produces excellent PDF
output, I am seeing the following messages about lots of ignored
instances.
After checking RTFHandler.java, it seems they are omitted from the very
On 20.09.2005 17:50:03 Matthew L Daniel wrote:
The warning is an indicator that there are still a few things in RTF
support that need fixing.
So is there someone who owns this class?
No. There are no class owners in Apache projects.
How long has it been
out-of-sync - that is, is it in
I am using trunk code and with an input FO that produces excellent PDF
output, I am seeing the following messages about lots of ignored
instances.
After checking RTFHandler.java, it seems they are omitted from the very
large instance-switch in invokeDeferredEvent.
My question is if this is in
