all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 23 character code space
Date: Mon, 03 Nov 2008 22:13:37 +0200	[thread overview]
Message-ID: <umyggva8e.fsf@gnu.org> (raw)
In-Reply-To: <E1Kwyo4-0007Vt-Ai@etlken.m17n.org>

> From: Kenichi Handa <handa@m17n.org>
> 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?




  reply	other threads:[~2008-11-03 20:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-01 14:20 Emacs 23 character code space Eli Zaretskii
2008-11-01 16:46 ` Eli Zaretskii
2008-11-03  1:34 ` Kenichi Handa
2008-11-03 12:45   ` Kenichi Handa
2008-11-03 20:13     ` Eli Zaretskii [this message]
2008-11-04  7:35       ` Kenichi Handa
2008-11-04 20:19         ` Eli Zaretskii
2008-11-05 12:27           ` Kenichi Handa
2008-11-05 18:23             ` Eli Zaretskii
2008-11-22 18:25             ` Eli Zaretskii
2008-11-26  1:41               ` Kenichi Handa
2008-11-26  4:13                 ` Eli Zaretskii
2008-11-26  4:24                   ` Kenichi Handa
2008-11-26  4:58                     ` Kenichi Handa
2008-11-26 20:26                       ` Eli Zaretskii
2008-11-26 22:52                         ` Juanma Barranquero
2008-11-27  1:10                         ` Stephen J. Turnbull
2008-11-27  1:35                           ` Kenichi Handa
2008-11-26 20:18                     ` Eli Zaretskii
2008-11-27  1:29                       ` Kenichi Handa
2008-11-29 17:12                         ` Eli Zaretskii
2008-12-02  5:40                           ` Kenichi Handa
2008-11-28 13:19                 ` Eli Zaretskii
2008-12-02  5:44                   ` Kenichi Handa
2008-12-02 19:40                     ` Eli Zaretskii
2008-11-29 12:01             ` Eli Zaretskii
2008-11-22 16:28     ` Eli Zaretskii
2008-11-23  4:16       ` Stefan Monnier
2008-11-23 11:22         ` Eli Zaretskii
2008-11-26  1:51         ` Kenichi Handa
2008-11-23  8:29       ` Ulrich Mueller
2008-11-23 11:11         ` Eli Zaretskii
2008-11-23 11:55           ` Ulrich Mueller
2008-11-24  3:06         ` Stefan Monnier
2008-11-26  1:31       ` Kenichi Handa
2008-11-22 17:03     ` New function: what-file-line, used when writing gdb script richardeng
2008-11-07  7:21 ` Emacs 23 character code space Kenichi Handa
2008-11-07 10:27   ` Eli Zaretskii
2008-11-07 11:52     ` Kenichi Handa

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=umyggva8e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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.