From: Kenichi Handa <handa@m17n.org>
Cc: juri@jurta.org, jasonr@gnu.org, emacs-devel@gnu.org
Subject: Re: UCS-2BE
Date: Fri, 01 Sep 2006 07:48:53 +0900 [thread overview]
Message-ID: <E1GIvLB-0005Mc-00@etlken> (raw)
In-Reply-To: <jey7t59dqh.fsf@sykes.suse.de> (message from Andreas Schwab on Thu, 31 Aug 2006 16:33:26 +0200)
In article <jey7t59dqh.fsf@sykes.suse.de>, Andreas Schwab <schwab@suse.de> writes:
> Kenichi Handa <handa@m17n.org> writes:
>>> See <http://www.unicode.org/versions/Unicode4.0.0/appC.pdf>.
> >
> > It says nothing about "UCS-2BE", either.
> C.2 [...] The 32-bit form is referred to as UCS-4 (Universal Character
> Set coded in 4 octets), and the 16-bit form is referred to as UCS-2
> (Universal Character Set coded in 2 octets).
??? So, what is "UCS-2BE"?
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-08-31 22:48 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 ` Kenichi Handa [this message]
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 ` UCS-2BE YAMAMOTO Mitsuharu
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=E1GIvLB-0005Mc-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=juri@jurta.org \
/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.