[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gnustandards ChangeLog standards.texi
From: |
Karl Berry |
Subject: |
gnustandards ChangeLog standards.texi |
Date: |
Sat, 10 Dec 2011 16:27:20 +0000 |
CVSROOT: /sources/gnustandards
Module name: gnustandards
Changes by: Karl Berry <karl> 11/12/10 16:27:20
Modified files:
. : ChangeLog standards.texi
Log message:
UTF-8 not upward compatible with Latin 1
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.146&r2=1.147
http://cvs.savannah.gnu.org/viewcvs/gnustandards/standards.texi?cvsroot=gnustandards&r1=1.208&r2=1.209
Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.146
retrieving revision 1.147
diff -u -b -r1.146 -r1.147
--- ChangeLog 6 Dec 2011 00:20:37 -0000 1.146
+++ ChangeLog 10 Dec 2011 16:27:20 -0000 1.147
@@ -1,3 +1,8 @@
+2011-12-10 Karl Berry <address@hidden>
+
+ * standards.texi (Quote Characters): UTF-8 is not compatible
+ with Latin 1.
+
2011-12-05 Karl Berry <address@hidden>
* standards.texi (Semantics, Errors, Character Set): more strongly
Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.208
retrieving revision 1.209
diff -u -b -r1.208 -r1.209
--- standards.texi 6 Dec 2011 00:20:37 -0000 1.208
+++ standards.texi 10 Dec 2011 16:27:20 -0000 1.209
@@ -3,7 +3,7 @@
@setfilename standards.info
@settitle GNU Coding Standards
@c This date is automagically updated when you save this file:
address@hidden lastupdate December 4, 2011
address@hidden lastupdate December 10, 2011
@c %**end of header
@dircategory GNU organization
@@ -611,10 +611,9 @@
Utilities reading files should not drop NUL characters, or any other
nonprinting characters @emph{including those with codes above 0177}.
The only sensible exceptions would be utilities specifically intended
-for interface to certain types of terminals or printers
-that can't handle those characters.
-Whenever possible, try to make programs work properly with
-sequences of bytes that represent multibyte characters;
+for interface to certain types of terminals or printers that can't
+handle those characters. Whenever possible, try to make programs work
+properly with sequences of bytes that represent multibyte characters;
UTF-8 is the most important.
@cindex error messages
@@ -766,12 +765,13 @@
@noindent
Line numbers should start from 1 at the beginning of the file, and
-column numbers should start from 1 at the beginning of the line. (Both
-of these conventions are chosen for compatibility.) Calculate column
-numbers assuming that space and all ASCII printing characters have
-equal width, and assuming tab stops every 8 columns. For non-ASCII
-characters, Unicode character widths should be used when in a UTF-8
-locale; GNU libc and GNU gnulib provide suitable @code{wcwidth} functions.
+column numbers should start from 1 at the beginning of the line.
+(Both of these conventions are chosen for compatibility.) Calculate
+column numbers assuming that space and all ASCII printing characters
+have equal width, and assuming tab stops every 8 columns. For
+non-ASCII characters, Unicode character widths should be used when in
+a UTF-8 locale; GNU libc and GNU gnulib provide suitable
address@hidden functions.
The error message can also give both the starting and ending positions
of the erroneous text. There are several formats so that you can
@@ -3175,9 +3175,9 @@
(but not required) to use non-ASCII characters to represent proper
names of contributors in change logs (@pxref{Change Logs}).
-If you need to use non-ASCII characters, you should normally stick with
-one encoding, certainly within a single file. UTF-8 is likely to be
-the best choice.
+If you need to use non-ASCII characters, you should normally stick
+with one encoding, certainly within a single file. UTF-8 is likely to
+be the best choice.
@node Quote Characters
@@ -3208,8 +3208,7 @@
the @samp{`} character we use was standardized there as a grave
accent. Moreover, Latin1 is still not universally usable.
-Unicode contains the unambiguous quote characters required, and its
-common encoding UTF-8 is upward compatible with Latin1. However,
+Unicode contains the unambiguous quote characters required. However,
Unicode and UTF-8 are not universally well-supported, either.
This may change over the next few years, and then we will revisit