From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs 23 character code space Date: Mon, 03 Nov 2008 22:13:37 +0200 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1225743260 21263 80.91.229.12 (3 Nov 2008 20:14:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Nov 2008 20:14:20 +0000 (UTC) Cc: emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 03 21:15:22 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Kx5pX-0005eY-LG for ged-emacs-devel@m.gmane.org; Mon, 03 Nov 2008 21:15:19 +0100 Original-Received: from localhost ([127.0.0.1]:38751 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kx5oQ-0001KC-Kc for ged-emacs-devel@m.gmane.org; Mon, 03 Nov 2008 15:14:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kx5o0-0001AI-M9 for emacs-devel@gnu.org; Mon, 03 Nov 2008 15:13:44 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kx5o0-00019w-4M for emacs-devel@gnu.org; Mon, 03 Nov 2008 15:13:44 -0500 Original-Received: from [199.232.76.173] (port=41600 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kx5nz-00019p-SJ for emacs-devel@gnu.org; Mon, 03 Nov 2008 15:13:43 -0500 Original-Received: from mtaout4.012.net.il ([84.95.2.10]:50755) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kx5nz-0006e3-Gq for emacs-devel@gnu.org; Mon, 03 Nov 2008 15:13:43 -0500 Original-Received: from HOME-C4E4A596F7 ([77.127.192.143]) by i_mtaout4.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K9R00HB0XLFITJ0@i_mtaout4.012.net.il> for emacs-devel@gnu.org; Mon, 03 Nov 2008 22:15:24 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 9.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:105311 Archived-At: > From: Kenichi Handa > CC: eliz@gnu.org, emacs-devel@gnu.org > Date: Mon, 03 Nov 2008 21:45:20 +0900 > > I tried to rewrite nonascii.texi to clear the things. I > finished upto the "Character Code" section as attached. > What do you think about it? Thanks, this definitely helps. Unfortunately, you worked from a non-current version of nonascii.texi; I already modified the first section heavily. Please take a look when you can: I intend to downplay the unibyte stuff heavily, while the previous version gave unibyte and multibyte almost equal coverage. In any case, I will certainly use what you wrote. Thanks! > @acronym{ASCII} characters occupy one > byte, non-@acronym{ASCII} characters occupy two to five bytes So I guess you agree that NEWS is not entirely correct saying that we use UTF-8 internally: UTF-8 uses only 1 to 4 bytes, not 1 to 5. Should I fix NEWS in this regard, saying that the internal representation is based on UTF-8, but extends it to handle additional characters?