I'm talking about Unix diff command. Of course it would report a diff on the #charset line but that doesn't really help at all if there's a 0xA4 character on line 4711 in both versions since diff doesn't know its interpretation varies with the charset.
The gotcha was that you pointed to a ISO-8859-x encoding where Euro was included, but I now revised the example in 10728746 to use "\x2122" instead.
Regardless, I'd rather see a discussion on the #multiline syntax than this sub-topic. If you still don't understand the example I can live with that.
/ Jonas Walldén
Previous text:
2003-09-23 00:46: Subject: Re: wish: string with other quoting then \
Tell that to the Windows computer I used last week that insisted Euro should be stored as 0x80... :-)
"windows-1252" is also a valid character encoding for Pike source code, so you can use that if it helps. ;-)
Anyway, this is off-topic but I'm curious to find out how diff would recognize which charset the file is using. If I have another string with the currency sign (0xA4 in ISO-8859-1) I'm quite certain it would report it as identical to Euro (0xA4 in ISO-8859-15). But for the sake of this argument I'll say "\x2122" (trademark) instead. (Gotcha! :-)
If you change the encoding of the file from ISO-8859-1 to ISO-8859-15, diff will report a change on the #charset line. Your phrasing "another string" puzzles me a bit though. Are you talking about the diff function in Pike? It works on wide strings.
I'm not sure what the "gotcha" was concerning trademark, could you expand on that perhaps?
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)