From b6d78a0d8019a92f94ce3fc41ddb0886f8b70d85 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Fri, 18 Jan 2019 10:51:57 +0200 Subject: [PATCH] Fix a typo in ELisp manual * doc/lispref/nonascii.texi (Converting Representations): Fix inconsistency between @defun and the argument description of 'byte-to-string'. (Bug#34119) --- doc/lispref/nonascii.texi | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/lispref/nonascii.texi b/doc/lispref/nonascii.texi index ab15ea7d9b2..66d12033d82 100644 --- a/doc/lispref/nonascii.texi +++ b/doc/lispref/nonascii.texi @@ -287,12 +287,11 @@ unibyte string, it is returned unchanged. Use this function for characters. @end defun -@c FIXME: Should '@var{character}' be '@var{byte}'? @defun byte-to-string byte @cindex byte to string This function returns a unibyte string containing a single byte of -character data, @var{character}. It signals an error if -@var{character} is not an integer between 0 and 255. +character data, @var{byte}. It signals an error if @var{byte} is not +an integer between 0 and 255. @end defun @defun multibyte-char-to-unibyte char -- 2.39.5