Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: ding@gnus.org
Subject: Re: Invalid characters, or something else?
Date: Mon, 18 Oct 2010 08:30:46 +1100	[thread overview]
Message-ID: <877hhgtsl5.fsf@blah.blah> (raw)
In-Reply-To: <87d3r9r7p2.fsf@windlord.stanford.edu> (Russ Allbery's message of "Sat, 16 Oct 2010 17:20:25 -0700")

Russ Allbery <rra@stanford.edu> writes:
>
> unlabelled Windows code pages.

Or labelled as <?xml encoding="iso-8859-1"> but in fact dos 1252 :-(.
I suppose if you assume there won't be any 8-bit ansi control char
thingies then could decode as 1252 instead automatically.  The blame
belongs squarely with the feed generator of course and it seems bad to
pander to the worst ones, even if it works out in practice, especially
as bad feeds are each bad in their own different way :-).  For what it's
worth in my own program I chucked in a charset override option and left
it at that (having also struck some latin-1 vs utf-8 feed
mis-declarations ...).



      parent reply	other threads:[~2010-10-17 21:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-17  0:05 Lars Magne Ingebrigtsen
2010-10-17  0:20 ` Russ Allbery
2010-10-17 13:07   ` Lars Magne Ingebrigtsen
2010-10-17 13:17     ` Lars Magne Ingebrigtsen
2010-10-17 13:22       ` Lars Magne Ingebrigtsen
2010-10-17 13:34         ` Lars Magne Ingebrigtsen
2010-10-17 17:57           ` Lars Magne Ingebrigtsen
2010-10-17 21:34           ` James Cloos
2010-10-17 21:33       ` James Cloos
2010-10-18  6:11         ` Reiner Steib
2010-10-18 18:32         ` Lars Magne Ingebrigtsen
2010-10-17 21:30   ` Kevin Ryde [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877hhgtsl5.fsf@blah.blah \
    --to=user42@zip.com.au \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).