Rainer: > > Encoding has been discussed and we have agreed upon > US-ASCII and UTF-8 > > in appropriate places. Could we add a language tag as an > element in > > an SD-ID to indicate the language of the MSG? > > If so, we should include the *character set* not the > language. In respect to existing implementations, that would > also be usefule. We should strongly consider to allow (but > not recommend) other encodings, too (like popular JIS or > EUC). I also posted this in my previous mail.
By character sets, do you suggest the use of the various locale-specific encodings instead of using Unicode with some UTF-8? I think that horrible legacy of gazillion local-specific encodings should be avoided at all cost! It is a dead-end. Unicode resolved that issue -- we should stick to it. I thought this was an accepted direction at IETF. It is in the industry too. If I understand correctly, Chris was proposing a mere indication of the language(s) used, which could be useful to the person analyzing the message. I don't think Chris was proposing to do something instead of UTF-8, which covers all of Unicode, which in turn covers all languages. Or did I misinterpret? Thanks, Anton _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
