On Sun, 2003-12-14 at 22:16, Darren Salt wrote: > I demand that Scott James Remnant may or may not have written... > > > On Sat, 2003-12-13 at 08:47, Herbert Xu wrote: > >> Colin Walters <firstname.lastname@example.org> wrote: > >>> But your message didn't include a Content-Type header specifying that, so > >>> it's likely to come through as garbage for most MUAs... > >> Right, here it is again > >> \xEF\xBB\xBF\xE8\xBE\xAD\xE6\xB5\xB7 > > > Now that's just the hand-printed bytecodes of raw UTF-8 :-) > > > Now, if my by-hand Unicode isn't rusty, I make this out to be > > > U+FEFF ZERO WIDTH NO_BREAK SPACE > > [...] > > Slightly rusty: since that's at the start of the string, it's telling you > which endianness is in use in the string. > True for UCS-2 or UCS-4, but you can only write UTF-8 one way (Big-Endian) deliberately so there wouldn't be this issue. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
Description: This is a digitally signed message part