trans-coord/gnun/server/gnun gnun.texi

[Yavor Doganov]

CVSROOT:        /cvsroot/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/03/16 11:17:42

Modified files:
        gnun/server/gnun: gnun.texi 

Log message:
        (Webmaster Tips): Typo fix.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/gnun.texi?cvsroot=trans-coord&r1=1.22&r2=1.23

Patches:
Index: gnun.texi
===================================================================
RCS file: /cvsroot/trans-coord/trans-coord/gnun/server/gnun/gnun.texi,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- gnun.texi   16 Mar 2008 08:36:11 -0000      1.22
+++ gnun.texi   16 Mar 2008 11:17:41 -0000      1.23
@@ -1328,12 +1328,12 @@
 Use @emph{only} US-ASCII characters and HTML entities for the others.
 This is required because the English text in the articles serves as a
 replacement of the translation when the latter is not complete.  So if
-you use, say, the character @'e (e-accute) directly in an English
-page---which is UTF-8 as declared in @file{server/header.html}, it will
-appear broken on those translated pages who use a different encoding.
-This specific advice is pretty much mandatory---the build fails if the
-original article contains such characters---but we are ready to fix any
-errors a webmaster makes.
+you use, say, the character @'e (e-acute) directly in an English
+page---which is UTF-8 as declared in @file{server/header.html}, it
+will appear broken on those translated pages who use a different
+encoding.  This specific advice is pretty much mandatory---the build
+fails if the original article contains such characters---but we are
+ready to fix any errors a webmaster makes.
 
 The script @command{validate-html} is useful for webmasters who want to
 verify if their (potentially intrusive) changes result in a valid