Re: inline viewing can't display CJK characters

[Leo <sdl.web@gmail.com>]

----- Katsumi Yamaoka (2007-06-04) 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.

Ah, thanks for the explanation. TeX files have a mimetype
"application/x-tex" and "elisp" files have a mimetype
"application/emacs-lisp" as defined in /etc/mime.types. So when I
attached test.el Gnus automatically picked up "application/emacs-lisp".

>> 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''.

Command `K i' exists in article buffer, but does not work properly.
Try to use this command in article buffer will cause an error:

,----
| Debugger entered--Lisp error: (error "No article is displayed")
|   signal(error ("No article is displayed"))
|   error("No article is displayed")
|   gnus-article-part-wrapper(3 gnus-mime-inline-part)
|   gnus-article-inline-part(3)
|   call-interactively(gnus-article-inline-part)
|   gnus-article-read-summary-keys(3)
|   call-interactively(gnus-article-read-summary-keys)
`----

> Only with No Gnus, you can add the coding cookie to such a file
> in order to specify the charset MIME parameter.  For examples:
> 
> 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.

It appears that mailcap does not define such mimetype. A bug in mailcap?

>
> Regards,

Thanks,
-- 
Leo <sdl.web AT gmail.com>                         (GPG Key: 9283AA3F)