Mike, I have created an issue to track this.
http://issues.apache.org/jira/browse/LOG4NET-22 Nicko > -----Original Message----- > From: Mike Blake-Knox [mailto:[EMAIL PROTECTED] > Sent: 24 March 2005 16:01 > To: Log4NET User > Cc: Log4J Users List > Subject: Re: chainsaw and "escaping" XML entities > > To be honest, I was really more concerned by the log being > completely dropped. Either of your suggestions would be a > step forward. I'd think of substituting some visible > character giving an appearance like a hex dump where > unprintable characters are often replaced with periods. > > What I've done here is to scan the text before call log4net > and replacing most of the control characters with \xnn where > nn is the hex value of the offending character. I've done > this as I can foresee using the log/trace as a source of test > data and a filtered one wouldn't be sufficient. > > Mike > > On Thu, 24 Mar 2005 09:34:39 -0000, Nicko Cadell > <[EMAIL PROTECTED]> wrote: > > If chainsaw can only parse XML 1.0 then we will need to ensure that > > our output can be configured to be XML 1.0 compatible. > Presumably this > > means just stripping the characters that are invalid in XML. > > > > The XML faq basically says that you should use XML elements to > > represent control characters. Presumably they had some complaints > > about this and therefore allowed them in XML 1.1. If the data is > > binary then it should be base64 escaped. > > > > By the way, what do you want chainsaw to do with your control > > characters? If we just stripped them out would that be ok? > Or could we > > replace them with spaces? > > > > Nicko > > > > > -----Original Message----- > > > From: Mike Blake-Knox [mailto:[EMAIL PROTECTED] > > > Sent: 23 March 2005 14:03 > > > To: Log4NET User > > > Subject: Re: chainsaw and "escaping" XML entities > > > > > > I changed the xml version to 1.1. Unfortunately, messages "XML > > > version "1.0" is recognized, but not "1.1"" are displayed when it > > > tries to parse it. (In some perverse way, that's an > improvement in > > > that you get the message on the display for each received > log; using > > > xml 1.0, it just dropped the message and dumped into the console). > > > > > > I'm using jdk 1.4.2_06. > > > > > > Mike > > > > > > On Mon, 21 Mar 2005 14:58:54 -0000, Nicko Cadell > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > In XML 1.1 so called restricted chars are allowed to be > included > > > > as numeric character references (i.e. ). > > > > > > > > For details see > > > > http://www.w3.org/TR/2004/REC-xml11-20040204/#charsets > > > > and also > > > > http://www.w3.org/International/questions/qa-controls#answer > > > > > > > > If you change the version header at the top of the XML file > > > to 1.1 can > > > > chainsaw parse the event? > > > > > > > > I will have a look and see if it is possible to control the > > > behaviour > > > > of the XmlTextWriter with respect to the target XML version. > > > > > > > > Nicko > > > > > > > > > > > > -- > Mike Blake-Knox >
