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 d3891a103fb9815f0c336d39ba575f1f10ca070e..c297091d0f890f158930cbaa68f2517a179647ca 100644 (file)
--- 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 d07dbcacae29226d3e3ef4800a26d8b18eed90ea..982fcc2a9f5dd1bf7027c052f11bd1244bcfbe87 100644 (file)
--- 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.