From: Collin Funk <collin.funk1@gmail.com>
Date: Fri, 19 Dec 2025 03:29:49 +0000 (-0800)
Subject: doc: Use UTF-8 in Texinfo sources.
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b784f3ded1fa80ea79278f593a1bb11e5ba4c7da;p=thirdparty%2Fgnulib.git

doc: Use UTF-8 in Texinfo sources.

* doc/gnulib-intro.texi (Portability and Application Code): Use ï
instead of @"{@dotless{i}}.
---

diff --git a/ChangeLog b/ChangeLog
index d3891a103f..c297091d0f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2025-12-19  Collin Funk  <collin.funk1@gmail.com>
+
+	doc: Use UTF-8 in Texinfo sources.
+	* doc/gnulib-intro.texi (Portability and Application Code): Use ï
+	instead of @"{@dotless{i}}.
+
 2025-12-19  Bruno Haible  <bruno@clisp.org>
 
 	signbit-no-c++: New module.
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 @@ There is no clear borderline between both areas.
 
 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.