From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: inline viewing can't display CJK characters
Date: Mon, 04 Jun 2007 12:39:21 +0900 [thread overview]
Message-ID: <b4mira4qtg6.fsf@jpl.org> (raw)
In-Reply-To: <m2d50c34o4.fsf@sl392.st-edmunds.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
>>>>> In <m2d50c34o4.fsf@sl392.st-edmunds.cam.ac.uk> Leo wrote:
> To see the problem, go to the attachment in this post, hit 'E' and you
> will see garbled characters.
Because the supertype of that part is `application', not `text',
Gnus considers there is no human readable text in it. It is
decoded only by base64, as the part specifies.
> Content-Type: application/emacs-lisp
> Content-Disposition: attachment; filename=test.el
> Content-Transfer-Encoding: base64
> Content-Description: test.el
OTOH, `2 K i' or `i' on the button shows the decoded Chinese
text, because the `i' command is for the use of ``View As Text,
In This Buffer''.
Only with No Gnus, you can add the coding cookie to such a file
in order to specify the charset MIME parameter. For examples:
[-- Attachment #2: test1.el --]
[-- Type: application/emacs-lisp, Size: 80 bytes --]
;; -*- coding: utf-8; -*-
(defun text ()
"这个是函数。"
(do-nothing))
[-- Attachment #3: test2.el --]
[-- Type: application/emacs-lisp, Size: 100 bytes --]
(defun text ()
"这个是函数。"
(do-nothing))
;; Local Variables:
;; coding: utf-8
;; End:
[-- Attachment #4: Type: text/plain, Size: 216 bytes --]
What handles such a parameter of an `application' MIME part
might be only No Gnus, though.
Or it might be better to use `text/emacs-lisp' instead, though
I'm not sure such a type is widely known, either.
Regards,
next prev parent reply other threads:[~2007-06-04 3:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 1:10 Leo
2007-06-04 2:06 ` ssSslang
2007-06-04 2:42 ` Leo
2007-06-04 3:02 ` ssSslang
2007-06-04 3:39 ` Katsumi Yamaoka [this message]
2007-06-04 9:17 ` Leo
2007-06-04 10:03 ` Katsumi Yamaoka
2007-06-05 9:32 ` Katsumi Yamaoka
2007-06-05 10:01 ` Leo
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=b4mira4qtg6.fsf@jpl.org \
--to=yamaoka@jpl.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).