unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: handa@m17n.org, emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Unibyte characters
Date: Fri, 31 Oct 2008 10:41:47 -0400	[thread overview]
Message-ID: <jwvk5boq17r.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <uiqr9vwby.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 31 Oct 2008 13:27:13 +0200")

>> Text in a unibyte buffer is simply a bunch of binary characters
>> 0-255

> Here you are saying what I was saying: that these are just raw 8-bit
> bytes.

>> you can interpret them however you want, of course, but that's
>> not how emacs sees it.

> I don't mind saying that displaying such a buffer or string or
> movement by characters _interprets_ each byte as a single character.
> But interpretation and essence are two different things, and the
> manual does not make a point of telling that what it describes is the
> Emacs interpretation of such buffers, not what is actually held there.

> Thanks for the feedback, I will try to rephrase that text to make this
> distinction more clear.

IIUC, this part of the manual dates back to the introduction of Mule,
when many people were using Emacs in unibyte mode.  Nowadays unibyte
mode is not recommended (I'd even be all happy to remove it altogether)
and unibyte buffers should only be used for binary, undecoded data
(i.e. for bytes, not for chars).

So I agree with Eli that we should update this text to insist that
a unibyte buffer only contains bytes, and then explain that if the
buffer is displayed, those bytes will be interpreted in
a particular way.

BTW IIRC the non-ascii part will just be displayed as \NNN nowadays,
rather than in some locale-dependent charset (such as latin-1).


        Stefan




  reply	other threads:[~2008-10-31 14:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 11:05 Unibyte characters Eli Zaretskii
2008-10-31 11:18 ` Miles Bader
2008-10-31 11:27   ` Eli Zaretskii
2008-10-31 14:41     ` Stefan Monnier [this message]
2008-10-31 15:02       ` Juanma Barranquero
2008-10-31 18:44       ` Eli Zaretskii
2008-10-31 21:15         ` Stefan Monnier
2008-11-01 10:47           ` Stephen J. Turnbull
2008-11-02  1:59             ` Stefan Monnier
2008-10-31 19:30 ` Richard M. Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvk5boq17r.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=miles@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).