|
|
Posted by Dylan Parry on 08/24/05 10:12
Using a pointed stick and pebbles, Toby Inkster scraped:
> Nor here, though it looked fine in my newsreader. It's probably because
> Google isn't sending a charset in their HTTP headers. Manually selecting
> UTF-8 seems to have fixed it.
As pointed out by someone else in this thread, it works if you view the
"parsed" version of the Google archive. Is there any chance, Toby, that
you could make message-id.net point to the parsed version of articles
rather than the source?
--
Dylan Parry
http://electricfreedom.org -- Where the Music Progressively Rocks!
Navigation:
[Reply to this message]
|