Re: Updating syslog(3), syslogd(8) to support RFC-5424

[der Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>>> Personally, I think message bodies should be encoding-agnostic
>>> octet strings, [...]
>> [...] control characters and escape sequences [...]
> And what do you do about NUL?  If we're talking about real (not
> Modified) UTF-8, now we're going to have 0x0 in the syslog output,

What's "real" UTF-8?  If you're talking about RFC3629 UTF-8 (and I
can't see any reason to use any other), a 0x00 octet appears in the
UTF-8 encoding when, and only when, a U+0000 character appears in the
character string being encoded.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B