From: Dan Jacobson <jidanni@jidanni.org>
Cc: ding@gnus.org
Subject: mm-util.el should know as many charsets as iconv
Date: Mon, 19 Jun 2006 22:46:09 +0800 [thread overview]
Message-ID: <E1FsL0z-0004bV-5S@jidanni1> (raw)
In the buffer *Messages* I have painstakingly traced the non "$0"
prefixed message "Unknown charset: windows-874" to the file
/usr/share/emacs/site-lisp/gnus/lisp/mm-util.el
And how unfair it is that windows-874 is unknown. Compare
$ iconv -l |grep 874|xargs
874// CP874// CSISO153GOST1976874// GOST_1976874// IBM874// WINDOWS-874//
So maybe if mm-util.el doesn't know a charset, perhaps it should
upcase the name, and pass the work over to iconv to give it a try.
OK, I did
(codepage-setup 874)(define-coding-system-alias 'windows-874 'cp874)
like the Info page said. The Info page should say why we must do this
by hand as it is not done automatically for us for all "windows-" sets.
$ man Encode::Supported says for example,
All cp* are also available as ibm-*, ms-*, and windows-* .
(By the way, the characters shown were squares unless I used emacs -nw
or used echo in a shell buffer. Perhaps I don't have a bold Thai font
installed.)
next reply other threads:[~2006-06-19 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 14:46 Dan Jacobson [this message]
2006-06-19 21:30 ` Reiner Steib
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=E1FsL0z-0004bV-5S@jidanni1 \
--to=jidanni@jidanni.org \
--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).