doc: Use UTF-8 in Texinfo sources.

[Collin Funk]

Any objections to using UTF-8 in the Texinfo sources?

I see we already have some non-breaking spaces and accented characters,
found using the following command:

    $ git ls-files | grep '\.texi' \
        | xargs perl -ne 'print "$ARGV:$_" if /[^\x00-\x7F]/'

So I hope it is okay.

I find the Texinfo macros for accents hard to remember [1], and they
make reading the source more difficult, in my opinion.

I noticed these ones in Gnulib files while doing the same in Coreutils.

Collin

[1] 
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Inserting-Accents.html


>From d4957cb3123d225bdd94d6872f3f6977307a0602 Mon Sep 17 00:00:00 2001
Message-ID: <d4957cb3123d225bdd94d6872f3f6977307a0602.1766115033.git.collin.fu...@gmail.com>
From: Collin Funk <collin.fu...@gmail.com>
Date: Thu, 18 Dec 2025 19:29:49 -0800
Subject: [PATCH] doc: Use UTF-8 in Texinfo sources.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* doc/gnulib-intro.texi (Portability and Application Code): Use ï
instead of @"{@dotless{i}}.
* doc/parse-datetime.texi (Authors of parse_datetime): Use ç instead of
@,{c}.
---
 ChangeLog               | 8 ++++++++
 doc/gnulib-intro.texi   | 2 +-
 doc/parse-datetime.texi | 2 +-
 3 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index fe19efcc4b..06bf056f83 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2025-12-18  Collin Funk  <collin.fu...@gmail.com>
+
+	doc: Use UTF-8 in Texinfo sources.
+	* doc/gnulib-intro.texi (Portability and Application Code): Use ï
+	instead of @"{@dotless{i}}.
+	* doc/parse-datetime.texi (Authors of parse_datetime): Use ç instead of
+	@,{c}.
+
 2025-12-15  Collin Funk  <collin.fu...@gmail.com>
 
 	nanosleep: Avoid a redefinition on mingw.
diff --git a/doc/gnulib-intro.texi b/doc/gnulib-intro.texi
index d07dbcacae..982fcc2a9f 100644
--- a/doc/gnulib-intro.texi
+++ b/doc/gnulib-intro.texi
@@ -127,7 +127,7 @@ @node Portability and Application Code
 
 For example, Gnulib has a facility for generating the name of backup
 files.  While this task is entirely at the application level---no
-standard specifies an API for it---the na@"{@dotless{i}}ve code has
+standard specifies an API for it---the naïve code has
 some portability problems because on some platforms the length of file
 name components is limited to 30 characters or so.  Gnulib handles
 that.
diff --git a/doc/parse-datetime.texi b/doc/parse-datetime.texi
index 51c6f74148..682aeee077 100644
--- a/doc/parse-datetime.texi
+++ b/doc/parse-datetime.texi
@@ -620,6 +620,6 @@ @node Authors of parse_datetime
 
 @cindex Pinard, F.
 @cindex Berry, K.
-This chapter was originally produced by Fran@,{c}ois Pinard
+This chapter was originally produced by François Pinard
 (@email{pinard@@iro.umontreal.ca}) from the @file{parse_datetime.y} source code,
 and then edited by K. Berry (@email{kb@@cs.umb.edu}).
-- 
2.52.0