unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Colin Woodbury <colin@fosskers.ca>
To: guile-devel@gnu.org
Subject: [PATCH] Clarify file encoding details regarding UTF-8
Date: Tue, 6 Dec 2022 10:00:39 +0900	[thread overview]
Message-ID: <1a5707fd-c69a-c82d-c46f-b9b076999dcf@fosskers.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 240 bytes --]

Hi again folks, here's a clarification of the default encoding of Guile 
source files. I've basically made the two pages match in their message, 
please let me know if anything is incorrect.

This also includes a minor spelling correction.

[-- Attachment #2: 0001-doc-Clarify-file-encoding-details-regarding-UTF-8.patch --]
[-- Type: text/x-patch, Size: 2398 bytes --]

From 6a2555db257faaf784d2e7ad78b361377114ed11 Mon Sep 17 00:00:00 2001
From: Colin Woodbury <colin@fosskers.ca>
Date: Sat, 3 Dec 2022 11:42:41 +0900
Subject: [PATCH] doc: Clarify file encoding details regarding UTF-8

Since UTF-8 is stated as the default assumed encoding, this point has
been emphasized.

This also fixes a minor spelling mistake.
---
 doc/ref/api-evaluation.texi | 4 ++--
 doc/ref/scheme-scripts.texi | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/ref/api-evaluation.texi b/doc/ref/api-evaluation.texi
index df7623f87..464694d8c 100644
--- a/doc/ref/api-evaluation.texi
+++ b/doc/ref/api-evaluation.texi
@@ -1080,7 +1080,7 @@ three arguments.
 @cindex source file encoding
 @cindex primitive-load
 @cindex load
-Scheme source code files are usually encoded in ASCII or UTF-8, but the
+Scheme source code files are usually encoded in UTF-8 or ASCII, but the
 built-in reader can interpret other character encodings as well.  When
 Guile loads Scheme source code, it uses the @code{file-encoding}
 procedure (described below) to try to guess the encoding of the file.
@@ -1125,7 +1125,7 @@ ASCII.
 There might be a scenario in which one would want to read non-ASCII
 code from a port, such as with the function @code{read}, instead of
 with @code{load}.  If the port's character encoding is the same as the
-encoding of the code to be read by the port, not other special
+encoding of the code to be read by the port, no other special
 handling is necessary.  The port will automatically do the character
 encoding conversion.  The functions @code{setlocale} or by
 @code{set-port-encoding!} are used to set port encodings
diff --git a/doc/ref/scheme-scripts.texi b/doc/ref/scheme-scripts.texi
index 221c8ba20..4019c6540 100644
--- a/doc/ref/scheme-scripts.texi
+++ b/doc/ref/scheme-scripts.texi
@@ -62,8 +62,8 @@ operating system never reads this far, but Guile treats this as the end
 of the comment begun on the first line by the @samp{#!} characters.
 
 @item
-If this source code file is not ASCII or ISO-8859-1 encoded, a coding
-declaration such as @code{coding: utf-8} should appear in a comment
+If this source code file is not UTF-8 or ASCII encoded, a coding
+declaration such as @code{coding: iso-8859-1} should appear in a comment
 somewhere in the first five lines of the file: see @ref{Character
 Encoding of Source Files}.
 
-- 
2.38.1


                 reply	other threads:[~2022-12-06  1:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/guile/

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

  git send-email \
    --in-reply-to=1a5707fd-c69a-c82d-c46f-b9b076999dcf@fosskers.ca \
    --to=colin@fosskers.ca \
    --cc=guile-devel@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.
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).