Cameron McCormack wrote:
Thomas DeWeese:
It is really unfortunate the svggen tests are failing, short of sorting the tags I can't think of a good way to address this issue (I suppose adding support for accepted variation could be one route, but for some reason it doesn't seem as good to me).
The tests could, instead of comparing the generated files directly, parse them back into Documents and then compare them node by node. This wouldn't address the different orderings of the CSS properties, though.
Well you could use the SAC to check the CSS side of the house. It would be a fair amount of code to do this of course.
The text-i18n has a text char where it should probably have only whitespace, it is easy to fix, replace "</text>><text" with: "</text><text".
Ah, I see. Has someone told the WG?
I think the WG is aware of the problem, but the test suite we are using is the old 1.0 test suite. There really weren't any 'new' tests from 1.1 (the old tests were modified for the profiles). When 1.2 comes out we should probably investigate updating which test suite we use.
Looking at your output you are probably OK to deliver (I'm a bit nervous about the memory leak - does the clean 1.5.1 have the same problem?), but moving forward we should add support for accepted variations for the transcoder and svggen because 160 errors is too many to examine closely.
Is there a CVS tag I can use to get the 1.5.1 sources?
Yes, there is: 'batik-1_5_1'
You can get a list of all the tags (and checkin comments) with 'cvs log <file>' I usually use build.xml, just because it has been part of the repository essentially from day 1.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
