> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of [email protected] > Sent: Friday, January 22, 2010 11:07 AM > To: rsyslog-users > Subject: Re: [rsyslog] PostgreSQL: Problems with character encoding > > On Fri, 22 Jan 2010, Rainer Gerhards wrote: > > >> my thought is that just like we have a filter to change control > >> characters > >> to escape sequences, it would be good to have a filter to escape > non- > >> ascii > >> characters. this will mangle other character sets, but they are > unlikly > >> to > >> go through cleanly anyway. > > > > Just to be on the right path, you suggest escaping charactes with hex > values > >> 7f? > > correct. they can cause as much grief (or more) than control > characters. > > since control characters get escaped by default, rsyslog will already > mangle UTF8 text sent to it if the final byte is in that range.
jup, just wanted to be sure. that can probably be best implemented as a property replacer option (or at the parser level, but then it applies to everything). Note that many European languages use these characters (and without grief), much as Asian languages use sequences which would be destroyed by the current escaping (which thus can be turned off). But I definitely see the value. Given it looks easy to implement, I'll see if I can integrate an option. Rainer > > David Lang > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
