From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 14 Aug 2025 22:58:58 -0500 Subject: removing all downloaded devdocs files --- devdocs/elisp/loading-non_002dascii.html | 6 ------ 1 file changed, 6 deletions(-) delete mode 100644 devdocs/elisp/loading-non_002dascii.html (limited to 'devdocs/elisp/loading-non_002dascii.html') diff --git a/devdocs/elisp/loading-non_002dascii.html b/devdocs/elisp/loading-non_002dascii.html deleted file mode 100644 index 094e2ec4..00000000 --- a/devdocs/elisp/loading-non_002dascii.html +++ /dev/null @@ -1,6 +0,0 @@ -

Loading Non-ASCII Characters

When Emacs Lisp programs contain string constants with non-ASCII characters, these can be represented within Emacs either as unibyte strings or as multibyte strings (see Text Representations). Which representation is used depends on how the file is read into Emacs. If it is read with decoding into multibyte representation, the text of the Lisp program will be multibyte text, and its string constants will be multibyte strings. If a file containing Latin-1 characters (for example) is read without decoding, the text of the program will be unibyte text, and its string constants will be unibyte strings. See Coding Systems.

In most Emacs Lisp programs, the fact that non-ASCII strings are multibyte strings should not be noticeable, since inserting them in unibyte buffers converts them to unibyte automatically. However, if this does make a difference, you can force a particular Lisp file to be interpreted as unibyte by writing ‘coding: raw-text’ in a local variables section. With that designator, the file will unconditionally be interpreted as unibyte. This can matter when making keybindings to non-ASCII characters written as ?vliteral.

-

- Copyright © 1990-1996, 1998-2022 Free Software Foundation, Inc.
Licensed under the GNU GPL license.
- https://www.gnu.org/software/emacs/manual/html_node/elisp/Loading-Non_002dASCII.html -

-
-- cgit v1.2.3