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. > 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? > 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? Cameron -- Cameron McCormack | Web: http://mcc.id.au/ | ICQ: 26955922 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
