inline viewing can't display CJK characters

inline viewing can't display CJK characters

[Leo]

[-- Attachment #1: Type: text/plain, Size: 113 bytes --]

Dear Gnus,

To see the problem, go to the attachment in this post, hit 'E' and you
will see garbled characters.


[-- Attachment #2: test.el --]
[-- Type: application/emacs-lisp, Size: 54 bytes --]

[-- Attachment #3: Type: text/plain, Size: 161 bytes --]


Tested in GNU Emacs 23.0.0.6 (i686-pc-linux-gnu, X toolkit) of
2007-05-31.

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

Re: inline viewing can't display CJK characters

[ssSslang]

Leo <sdl.web@gmail.com> writes:

> Dear Gnus,
>
> To see the problem, go to the attachment in this post, hit 'E' and you
> will see garbled characters.
>
> (defun text ()
>   "这个是函数。"
>   (do-nothing))
>
> Tested in GNU Emacs 23.0.0.6 (i686-pc-linux-gnu, X toolkit) of
> 2007-05-31.

Here I don't. And I had some CJK font installed.

-- 
ssSslang

Re: inline viewing can't display CJK characters

[Leo]

----- ssSslang (2007-06-04) wrote:-----

>> Dear Gnus,
>>
>> To see the problem, go to the attachment in this post, hit 'E' and you
>> will see garbled characters.
>>
>> (defun text ()
>>   "这个是函数。"
>>   (do-nothing))
>>
>> Tested in GNU Emacs 23.0.0.6 (i686-pc-linux-gnu, X toolkit) of
>> 2007-05-31.
>
> Here I don't. And I had some CJK font installed.

That is weird. I check your post in firefox and it is garbled:

http://permalink.gmane.org/gmane.emacs.gnus.general/64749

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

Re: inline viewing can't display CJK characters

[ssSslang]

Leo <sdl.web@gmail.com> writes:

> That is weird. I check your post in firefox and it is garbled:
>
> http://permalink.gmane.org/gmane.emacs.gnus.general/64749


I do in opera. I guess maybe gnus not encode the characters.
'decode-coding-region' also doesn't work. And I cannot find any encoding
description in you message. Should it be encoded to utf-8?

-- 
ssSslang

Re: inline viewing can't display CJK characters

[Katsumi Yamaoka]

[-- 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,

Re: inline viewing can't display CJK characters

[Leo]

----- 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)

Re: inline viewing can't display CJK characters

[Katsumi Yamaoka]

>>>>> In <m2lkf0qdt2.fsf@sl392.st-edmunds.cam.ac.uk> Leo wrote:

> 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)
> `----

I could reproduce it when only the article window is displayed
in the Emacs frame.  That is indeed a bug, but I think it is not
so serious.  But it seems to be not so easy to fix.  I'll try it
when I have time.

>> 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?

I don't know.  What you should do first might be to register
such one in some RFC or other as a new MIME type.

Regards,

Re: inline viewing can't display CJK characters

[Katsumi Yamaoka]

>>>>> In <b4mabvg6npk.fsf@jpl.org> Katsumi Yamaoka wrote:
>>>>>> In <m2lkf0qdt2.fsf@sl392.st-edmunds.cam.ac.uk> Leo wrote:

>> Command `K i' exists in article buffer, but does not work properly.

[...]

> I could reproduce it when only the article window is displayed
> in the Emacs frame.  That is indeed a bug, but I think it is not
> so serious.  But it seems to be not so easy to fix.  I'll try it
> when I have time.

I realized it will be a problem to people who like to read
articles without displaying the summary buffer.  I've fixed it
in the trunk.

Regards,

Re: inline viewing can't display CJK characters

[Leo]

----- Katsumi Yamaoka (2007-06-05) wrote:-----

>>> Command `K i' exists in article buffer, but does not work properly.
>
> [...]
>
>> I could reproduce it when only the article window is displayed
>> in the Emacs frame.  That is indeed a bug, but I think it is not
>> so serious.  But it seems to be not so easy to fix.  I'll try it
>> when I have time.
>
> I realized it will be a problem to people who like to read
> articles without displaying the summary buffer.  I've fixed it
> in the trunk.

Indeed. Works now. Thanks.

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