Ah, ok. That makes more sense. I was puzzled as to why the data was encoded, as it didn't need to be. The encoding has nothing to do with the data being in XML but is instead to do with it being used in an URL.

The different encoding must just be down to the way "file:" URLs are parsed on Windows and the Mac.

The Mac encoding looks very odd "Ste%CC%81phane". So the "e" is there and then some encoding presumably to indicate it has an accent.

Mind you, the Windows encoding looks odd as well. I would expect é (e-acute) to be encoded as "%e9".

I guess it must be some double byte nastiness. I guess we must be dealing with some Latin codepage rather than Unicode and that "%C3%A9" is the encoding for it. That would explain why the Mac version is different, due to different code pages. I still don't understand why the Mac version has "e" and the encoded value though.

P.S. did I mention that I hate dealing with double byte nonsense...