May 04

--- Comment #1 from Berni44 <> ---
Reading the unicode standard, I think, I erred here on what should happen. Actually, the invalid 0xff character should be replaced by a 0xFFFD-replacement character in both versions (or both versions should throw, but that is not recommended any more, because it might permit a denial of service attack).