summaryrefslogtreecommitdiff
path: root/man/basic.texi
diff options
context:
space:
mode:
authorKenichi Handa <handa@m17n.org>2005-10-13 05:28:12 +0000
committerKenichi Handa <handa@m17n.org>2005-10-13 05:28:12 +0000
commit170e42a17e3fe9d983b0cd4a5f6a19eb447ba823 (patch)
tree27d4a0276c8b507a91556c50b0a99b7734e36345 /man/basic.texi
parentf086544bb146c7e6f6e347d9562a0e882d6f2f3b (diff)
downloademacs-170e42a17e3fe9d983b0cd4a5f6a19eb447ba823.tar.gz
(Position Info): Fix previous change.
Diffstat (limited to 'man/basic.texi')
-rw-r--r--man/basic.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/man/basic.texi b/man/basic.texi
index 292de46fc7c..2c78de612ad 100644
--- a/man/basic.texi
+++ b/man/basic.texi
@@ -642,11 +642,11 @@ safely and with a single byte (@pxref{Coding Systems}). If the
character's encoding is longer than one byte, Emacs shows @samp{file ...}.
However, if the character displayed is in the range 0200 through
-0377 octal, there's a case that it actually represents an invalid
-UTF-8 byte. Emacs represents such a byte in a buffer by a sequence of
-8-bit characters, but displays only the original invalid byte in octal
-form. In such a case, Emacs shows @samp{part of display ...} instead
-of @samp{file}.
+0377 octal, it may actually stand for an invalid UTF-8 byte read from
+a file. In Emacs, that byte is represented as a sequence of 8-bit
+characters, but all of them together display as the original invalid
+byte, in octal code. In this case, @kbd{C-x =} shows @samp{part of
+display ...} instead of @samp{file}.
@samp{point=} is followed by the position of point expressed as a character
count. The front of the buffer counts as position 1, one character later