Nor in english, not that this is any great surprise to anyone. (And it looks like nearly half the spam my filters catch isn't Latin-1/Unicode. I don't know if this is an argument for or against dumping all the non-Unicode encodings... :)
This piece actually made it through the filters, which was mildly interesting. I'm not 100% sure it actually is spam (my Japanese isn't very good) but after a half hour or so with the dictionary and grammar reference it sure looks like it. I expect I'll poke at it some more, but on the off chance I'm really missing something, anyone care to give it a quick read? I'd hate to misread an actual offer of help. (Though I'm really thinking that this... isn't)
[message chopped out -- yep, it was spam]
(Quick update -- this is, in fact, Unicode, though it's not getting tagged properly for some reason. Text encodings, all of them, suck)
Posted by Dan at October 31, 2004 12:42 PM | TrackBack (0)Hi Dan,
I believe I can explain what is happening. Apache is serving this document as iso-8859-1.
(This is what LiveHTTPHeaders is showing: Content-Type: text/html; charset=iso-8859-1)
You might be a victim of AddDefaultCharset
Posted by: Steve Jenson at October 31, 2004 01:28 PMAh, that was it--thanks! The offending line's been commented out, so now we'll see what it breaks. :)
Posted by: Dan at October 31, 2004 02:00 PMIt is spam, and you can delete it - more accurately, it's something of a sex ad. (I'd rather not go into details, but that's what I figured from a few moments of looking at it.) Y'know, almost like an ad you'd find in the personals, with "if you reply I'll send photos of myself" and so on.
So yeah. Deletion. ^^;
Posted by: Jasmine Pues at October 31, 2004 04:01 PMWell, that explains some of the things that were tricky to find in the dictionary. I think I need a better one... :) Thanks for looking it over.
Posted by: Dan at November 1, 2004 08:06 AMIf all text encodings suck, what would we use in their place?
Posted by: Jack at November 6, 2004 02:41 AM