Is there a workaround for that? I mean this can't be intended behaviour
:) But as I interpret your answer, this has most likely something to do with
the Mono Framework, not with log4net, right?
Mit freundlichen Grüßen / Regards
Johannes Frank
Not sure if this behavior is intended or not, but
One clarification here would seem to be in order. UTF-8 is a
variable-length encoding. The length of any given code point will be
between 1 and 4 bytes long. UTF-8 is a byte stream and so there really is
no byte ordering (unlike UTF-16). Hence, the BOM is pretty useless for
UTF-8.
For