[Date Prev][Date Next][Thread Prev][][Date Index][Thread Index]

Re: shimbun.el: ISO-2022-JP as default Content-type charset?

(We're talking about the default MIME charset that the function
 `shimbun-header-insert-and-buffer-string' uses.)

>>>>>> In [emacs-w3m : No.09576] Eugene Oleinik wrote:

>> I use Shimbun's `rss-hash' backend to read articles with
>> cyrillic and occasionally CJK characters, almost always
>> encoded in utf-8 nowdays.

>> With default setup I get

>>   Content-Type: text/html; charset=ISO-2022-JP

>> in header,


>> -    (setq charset "ISO-2022-JP"))
>> +    (setq charset "utf-8"))

>>>>> In [emacs-w3m : No.09577] Katsumi Yamaoka wrote:

> I use "UTF-8" so that it may follow in FLIM's convention.

This function is used also when generating text/plain articles
and this change makes it always use UTF-8 (even if the text
contains only ASCII letters).  However, UTF-8 is not necessarily
available (Emacs 21's native UTF-8 does not support CJK text,
for instance) and is not necessarily efficient for Japanese text.
So, I've changed it to the value that the function
`detect-mime-charset-region' determines, in the CVS trunk.  It is
defined in APEL, and is being used with MUAs including Wanderlust
for a long time.

(I'm now revising sb-mainichi.el to follow the site change and
noticed it.)