Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Have Emacs guess the charset?
Date: Mon, 20 Aug 2001 11:26:43 +1000	[thread overview]
Message-ID: <87r8u7zfl8.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <m37kvzsh35.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 20 Aug 2001 02:36:14 +0200")

On Mon, 20 Aug 2001, Lars Magne Ingebrigtsen wrote:
> Daniel Pittman <daniel@rimspace.net> writes:
> 
>> `detect-coding-region'
> 
> Thanks.
> 
> I've just tried it in an (unmarked) big5 message.  (Well, I'm guessing
> it was big5.)  The function returned the following list:
> 
> (iso-latin-1-unix raw-text-unix chinese-big5-unix no-conversion)
> 
> Which means that the correct answer is the third-most-likely guess...
> Is big5 particularly difficult to guess, or is the function bad at
> guessing?

I think that the answer is probably "both", but I am not really certain.
I don't know too much about MULE, but both Kai and I have tried to
support it at various times with TRAMP.

So, my recollection of BIG5 encoding is that it is an escaped-in set of
bytes in the 128-255 range, with iso-2022 codeset shifts to get to and
from ASCII.

That means it's probably not that easy to pick. Which, you understand,
does not make the function all that smart.

Under XEmacs, it's pretty simplistic in it's detection of possible
coding system matches.

Er, you did call it on the region that *DID NOT* include the ASCII email
headers, right?

If that's true, I guess that you are pretty much short of luck. :(
        Daniel

-- 
There is censorship in this country, all right, make no mistake about that,
but also make no mistake about its source...While the government will not
censor, apparently the networks will. The irreparable damage to the public is
all the same.
        -- Nicholas Johnson, Federal Communications Commissioner, _
           New York Times_, (April 8, 1969)


  reply	other threads:[~2001-08-20  1:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 14:01 Kai Großjohann
2001-08-19 20:41 ` Lars Magne Ingebrigtsen
2001-08-19 23:46   ` Daniel Pittman
2001-08-20  0:36     ` Lars Magne Ingebrigtsen
2001-08-20  1:26       ` Daniel Pittman [this message]
2001-08-20  6:35         ` Lars Magne Ingebrigtsen
2001-08-20  7:26           ` Daniel Pittman
2001-08-20  8:25             ` Lars Magne Ingebrigtsen
2001-08-20  9:13               ` Daniel Pittman
2001-08-20 10:02                 ` Lars Magne Ingebrigtsen
2001-08-20  9:34               ` Kai Großjohann
2001-08-20 10:02                 ` Lars Magne Ingebrigtsen
2001-09-01 16:32       ` Dave Love
2001-08-21  0:07     ` ShengHuo ZHU
2001-08-21 21:58       ` Lars Magne Ingebrigtsen
2001-09-01 16:32       ` Dave Love

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=87r8u7zfl8.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.net \
    /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).