On further inspection it seems to be because I am using the .Net 1.0 method of creating an XmlTextReader which does not enable character checking: XmlTextReader reader = new XmlTextReader(thestream); msdn says this is deprecated in .Net 2.0 in favour of: XmlReader r = XmlReader.Create(thestream); using the new method character checking seems to be enabled by default. So its not a bug in mono its just that the XmlReader is slightly lax by default.
There is a plan to move beagle to .Net-2.0 pretty soon (this or next release). Would the filter break in that case ? -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user