From: Cyprian Laskowski <swagbelly@yahoo.com>
Subject: Re: coding-system difficulties
Date: Thu, 14 Nov 2002 05:33:44 GMT [thread overview]
Message-ID: <m3isz0g10a.fsf@swagbelly.net> (raw)
In-Reply-To: <84y97x5utn.fsf@lucy.cs.uni-dortmund.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Sometimes, the charset header is bogus. You can type `1 g' then
> enter the charset to force Gnus to use a different charset.
Wow, I didn't know about that feature: neat. However, for some
reason, it doesn't work for me in this case; or maybe I'm missing
something. Here's some more details:
I wrote the following function to facilitate matters a bit (I wonder
if functions/interfaces for these sorts of investigations already
exist in splendid form?):
(defun list-buffer-coding-systems-and-charsets ()
"Show list of charsets and possible coding systems for the buffer."
(interactive)
(let ((charsets (find-charset-region (point-min) (point-max))))
(pop-to-buffer "*Coding Systems*")
(erase-buffer)
(mapc (lambda (charset)
(insert "Charset: "
(symbol-name charset)
"\n"
"Coding systems: "
(prin1-to-string
(find-coding-systems-for-charsets
(list charset)))
"\n\n"))
charsets)))
Now, to be concrete, if I run this function on a certain *Article*
buffer with Greek text, it yields this:
,----
| Charset: ascii
| Coding systems: (undecided)
`----
But if I save the article in a file with the command sequence
mentioned before, and rerun the function from that buffer, I get:
,----
| Charset: ascii
| Coding systems: (undecided)
|
| Charset: greek-iso8859-7
| Coding systems: (iso-2022-jp-2 greek-iso-8bit tibetan-iso-8bit-with-esc thai-tis620-with-esc lao-with-esc korean-iso-8bit-with-esc japanese-iso-8bit-with-esc hebrew-iso-8bit-with-esc greek-iso-8bit-with-esc iso-latin-9-with-esc iso-latin-8-with-esc iso-latin-5-with-esc iso-latin-4-with-esc iso-latin-3-with-esc iso-latin-2-with-esc iso-latin-1-with-esc in-is13194-devanagari-with-esc cyrillic-iso-8bit-with-esc chinese-iso-8bit-with-esc compound-text iso-2022-8bit-ss2 iso-2022-7bit-lock iso-2022-7bit-ss2 iso-2022-7bit raw-text emacs-mule no-conversion)
`----
Now when I try `1 g greek-iso8859-7 RET' I still get unreadable text.
I even tried exhaustively running through all the charsets associated
with the greek-iso8859-7-compatible coding-systems listed above, but
still none of them was successful. I don't understand what's
happening here, since obviously is able to render the text correctly
(as in the file).
Incidentally, here are content-type-related header lines in the
message, as far as I can tell.
,----
| MIME-Version: 1.0
| Content-Type: multipart/alternative; boundary="0-1503940496-1037189069=:69315"
| Content-Transfer-Encoding: 8bit
| X-Content-Length: 4518
`----
As an aside, I wonder: is there a way (perhaps in BBDB) to associate a
person with a charset, or coding-system or something? Then when you
read a message from that person, or write a messag to them, the
correct setup is used, and you're totally in business.
Thanks to everyone for all the responses so far, as well as any more
to come. :)
cyp
next prev parent reply other threads:[~2002-11-14 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 15:21 Cyprian Laskowski
[not found] ` <84y97x5utn.fsf@lucy.cs.uni-dortmund.de>
2002-11-14 5:33 ` Cyprian Laskowski [this message]
2002-11-14 14:18 ` Kai Großjohann
[not found] ` <m31y5oc8yo.fsf@swagbelly.net>
[not found] ` <843cq3hn3g.fsf@lucy.cs.uni-dortmund.de>
2002-11-15 5:49 ` Fredrik Staxeng
[not found] ` <1mr8dps4ix.fsf@Tempo.Update.UU.SE>
[not found] ` <v9wunhckt2.fsf@marauder.physik.uni-ulm.de>
[not found] ` <m3bs4sg069.fsf@swagbelly.net>
2002-11-14 12:23 ` Fredrik Staxeng
2002-11-14 13:01 ` Hugh Baker
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=m3isz0g10a.fsf@swagbelly.net \
--to=swagbelly@yahoo.com \
/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).