all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: MON KEY <monkey@sandpframing.com>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, miles@gnu.org
Subject: Re: raw-byte and char-table
Date: Fri, 27 Aug 2010 12:45:50 +0900	[thread overview]
Message-ID: <tl71v9k4t1t.fsf@m17n.org> (raw)
In-Reply-To: <AANLkTimyj413zuWLDZciQMA1xPNo33qxCoY8ZrPqg6DW@mail.gmail.com> (message from MON KEY on Thu, 26 Aug 2010 23:30:38 -0400)

In article <AANLkTimyj413zuWLDZciQMA1xPNo33qxCoY8ZrPqg6DW@mail.gmail.com>, MON KEY <monkey@sandpframing.com> writes:

> On Thu, Aug 26, 2010 at 3:09 AM, Miles Bader <miles@gnu.org> wrote:
>>> Convert the byte BYTE to a character representing BYTE.
> > ...
>>> Likewise multibyte-char-to-unibyte => char-to-byte:
> >
> > Those names seem a bit more clear to me as well.
> >

> Yes. Me too.

> Is there some reason why these names might be confusing or otherwise
> add to the existing confusion?

Until Emacs 22, we treated a 8-bit byte as a character of the
current unibyte charset.  So, in Latin-1 env.,
  (unibyte-char-to-multibyte #xC0) => LATIN CAPITAL LETTER A WITH GRAVE
but in Cyrillic-KO8 env., 
  (unibyte-char-to-multibyte #xC0) => CYRILLIC SMALL LETTER YU

---
Kenichi Handa
handa@m17n.org



  reply	other threads:[~2010-08-27  3:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26  2:58 raw-byte and char-table MON KEY
2010-08-26  3:34 ` Kenichi Handa
2010-08-26  5:30   ` MON KEY
2010-08-26  6:48     ` Kenichi Handa
2010-08-26  7:09       ` Miles Bader
2010-08-27  3:30         ` MON KEY
2010-08-27  3:45           ` Kenichi Handa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-24  1:11 Kenichi Handa
2010-08-24  3:06 ` Eli Zaretskii
2010-08-24  4:29   ` Kenichi Handa
2010-08-24 17:08     ` Eli Zaretskii
2010-08-25  4:05       ` Kenichi Handa
2010-08-26  0:01         ` Stefan Monnier

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=tl71v9k4t1t.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monkey@sandpframing.com \
    --cc=monnier@iro.umontreal.ca \
    /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.