RE: Syslog Internationalization - Message size

[Andrew Ross]

Hi Rainer,

Having an unusual header in the MSG part of the syslog message would be
fine, but also adding some readable code to determine the encoding type
would be good.

@@$$##USASCII or @@$$##Base64 etc.

Syslog message are meant to be read by humans after all :)

Even if we can't decode the text that follows, we will know that it is
encoded and in what form.

Cheers

Andrew



-----Original Message-----
From: Rainer Gerhards [mailto:[EMAIL PROTECTED]
Sent: Friday, 18 July 2003 1:10 a.m.
To: Andrew Ross
Cc: [EMAIL PROTECTED]
Subject: RE: Syslog Internationalization - Message size


> Any one have any thoughts on the syntax to specify the encoding?
>
> Encoding=USASCII
> Encoding=Base64

How about borrowing somthing from mime?

Anyhow, I think the sequence must start with some "unusual sequence" so
that it most probably can not mistakenly occur within a non-i18n
message. For example something like (wihtout quotes) "@@$$##". This at
the very beginning (byte 0) of the MSG part means that it is an
i18n-enabled payload.

Does this make sense?

Rainer