Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: text/plain; charset=UTF-8 doesn't work anymore
Date: Fri, 14 Jan 2005 13:04:30 +0100	[thread overview]
Message-ID: <v98y6wjjxt.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b9yvfa0qqzq.fsf@jpl.org>

On Fri, Jan 14 2005, Katsumi Yamaoka wrote:

>>>>>> In <v9acrcs7fk.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:
>
>> I'd strongly recommend to get rid of mule-ucs in Emacs 21.
>
> But it is essential if a user want to encode Japanese (and
> possibly Chinese, Korean, etc.) text with the released versions
> of Emacs 21 (i.e., 21.3 and earlier).  

Sorry, I wasn't aware of this.  I know that CJK support in Emacs 21.3
is not very good.  As Steinar is from Norway, this is probably not
very important for him, though.

I seem to remember that Mule-UCS has some problem with Emacs 21.

> Try the following without Mule-UCS.
>
> (let ((str (string (make-char 'japanese-jisx0208 36 34))))
>   (list str
> 	(decode-coding-string
> 	 (encode-coding-string str 'utf-8)
> 	 'utf-8)))

,----
| *** Welcome to IELM ***  Type (describe-mode) for help.
| ELISP> (let ((str (string (make-char 'japanese-jisx0208 36 34))))
| 	 (list str
| 	(decode-coding-string
| 	 (encode-coding-string str 'utf-8)
| 	 'utf-8)))
| ("あ" "�")
| 
| ELISP> emacs-version
| "21.3.1"
| ELISP> 
`----

Okay, it should have been the same character, I guess, but it isn't:

,----
|   character: あ (0151042, 53794, 0xd222)
|     charset: japanese-jisx0208 (JISX0208.1983/1990 Japanese Kanji: ISO-IR-87)
|  code point: 36 34
|      syntax: word
|    category: H:Japanese Hiragana characters of 2-byte character sets  
| 	     j:Japanese  
| 	     |:While filling, we can break a line at this character.  
| buffer code: 0x92 0xA4 0xA2
|   file code: not encodable by coding system iso-latin-9
|        font: -Misc-Fixed-Medium-R-Normal--14-130-75-75-C-140-JISX0208.1983-0
`----

,----
|   character: � (01175275, 326333, 0x4fabd)
|     charset: mule-unicode-e000-ffff
| 	     (Unicode characters of the range U+E000..U+FFFF.)
|  code point: 117 61
|      syntax: word
|    category:
| buffer code: 0x9C 0xF3 0xF5 0xBD
|   file code: not encodable by coding system iso-latin-9
|        font: -Misc-Fixed-Medium-R-Normal--14-130-75-75-C-70-ISO10646-1
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2005-01-14 12:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14  6:26 Steinar Bang
2005-01-14  9:09 ` Reiner Steib
2005-01-14  9:50   ` Katsumi Yamaoka
2005-01-14 12:04     ` Reiner Steib [this message]
2005-01-15  9:38   ` Steinar Bang
2005-01-15 17:51     ` Steinar Bang

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=v98y6wjjxt.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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).