From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Juri Linkov <juri@jurta.org>,
schwab@suse.de, emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: UCS-2BE
Date: Fri, 01 Sep 2006 20:30:26 +0900 [thread overview]
Message-ID: <wl3bbbvn71.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <E1GIxh0-000751-00@etlken>
>>>>> On Fri, 01 Sep 2006 10:19:34 +0900, Kenichi Handa <handa@m17n.org> said:
> UCS-XXX are CEF, and UTF-XXX are CES. So, UCS-XXX are not
> appropriate lavel names for specifing how to byte-serialize
> characters (i.e. on saving characters in a file). At least, that is
> the official definition in Unicode.
IIUC, UCS is in the ISO/IEC 10646 terminology, rather than in the
Unicode terminology except Unicode 1.1 (though there would be some
references in the documentations, of course.)
"Unicode Technical Report #17, Character Encoding Model"
(http://www.unicode.org/reports/tr17/index.html) says:
Examples of encoding forms as applied to particular coded character
sets:
Name Encoding forms
Unicode 4.0 UTF-16 (default), UTF-8, or UTF-32 encoding form
Unicode 3.0 either UTF-16 (default) or UTF-8 encoding form
Unicode 1.1 either UCS-2 (default) or UTF-8 encoding form
ISO/IEC 10646, depending on the declared implementation levels, may
have UCS-2, UCS-4, UTF-16, or UTF-8.
Examples of Unicode Character Encoding Schemes:
The Unicode Standard has seven character encoding schemes: UTF-8,
UTF-16, UTF-16BE, UTF-16LE, UTF-32, UTF-32BE, and UTF-32LE.
Unicode 1.1 had three character encoding schemes: UTF-8, UCS-2BE,
and UCS-2LE, although the latter two were not named that way at
the time.
I suspect "UCS-2BE" is just a customary name and not explicitly
defined even in ISO/IEC 10646.
"UTF-8 and Unicode FAQ" (http://www.cl.cam.ac.uk/~mgk25/unicode.html)
says:
No endianess is implied by the encoding names UCS-2, UCS-4, UTF-16,
and UTF-32, though ISO 10646-1 says that Bigendian should be
preferred unless otherwise agreed. It has become customary to
append the letters "BE" (Bigendian, high-byte first) and "LE"
(Littleendian, low-byte first) to the encoding names in order to
explicitly specify a byte order.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2006-09-01 11:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 22:54 UCS-2BE Juri Linkov
2006-08-31 9:09 ` UCS-2BE Jason Rumney
2006-08-31 10:23 ` UCS-2BE Kenichi Handa
2006-08-31 10:39 ` UCS-2BE Jason Rumney
2006-08-31 10:55 ` UCS-2BE Kenichi Handa
2006-08-31 11:56 ` UCS-2BE Andreas Schwab
2006-08-31 12:16 ` UCS-2BE Kenichi Handa
2006-08-31 14:33 ` UCS-2BE Andreas Schwab
2006-08-31 22:48 ` UCS-2BE Kenichi Handa
2006-08-31 23:02 ` UCS-2BE Andreas Schwab
2006-09-01 1:22 ` UCS-2BE Kenichi Handa
2006-09-01 9:01 ` UCS-2BE Andreas Schwab
2006-09-01 11:28 ` UCS-2BE Kenichi Handa
2006-08-31 23:32 ` UCS-2BE Juri Linkov
2006-09-01 1:19 ` UCS-2BE Kenichi Handa
2006-09-01 11:30 ` YAMAMOTO Mitsuharu [this message]
2006-09-01 12:26 ` UCS-2BE Kenichi Handa
2006-09-01 12:30 ` UCS-2BE Andreas Schwab
2006-09-01 12:57 ` UCS-2BE Kenichi Handa
2006-09-01 17:08 ` UCS-2BE Stefan Monnier
2006-09-01 23:45 ` UCS-2BE Juri Linkov
2006-09-02 1:27 ` UCS-2BE Kenichi Handa
[not found] <E1GIw3v-00059X-TI@monty-python.gnu.org>
2006-08-31 23:36 ` UCS-2BE Jonathan Yavner
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=wl3bbbvn71.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=juri@jurta.org \
--cc=schwab@suse.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.