gnustandards-commit
[Top][All Lists]
Advanced

[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: Tue, 06 Dec 2011 00:20:37 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       11/12/06 00:20:37

Modified files:
        .              : ChangeLog standards.texi 

Log message:
        more strongly recommend UTF-8 when non-ASCII is needed

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.145&r2=1.146
http://cvs.savannah.gnu.org/viewcvs/gnustandards/standards.texi?cvsroot=gnustandards&r1=1.207&r2=1.208

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.145
retrieving revision 1.146
diff -u -b -r1.145 -r1.146
--- ChangeLog   3 Dec 2011 01:06:25 -0000       1.145
+++ ChangeLog   6 Dec 2011 00:20:37 -0000       1.146
@@ -1,11 +1,17 @@
+2011-12-05  Karl Berry  <address@hidden>
+
+       * standards.texi (Semantics, Errors, Character Set): more strongly
+       recommend supporting/using UTF-8 if anything non-ASCII is done.
+       Suggestion from Joseph Myers.
+
 2011-12-02  Karl Berry  <address@hidden>
 
-       * maintain.texi (Standard Mailing Lists): recommending describing
-       mailing lists in README and/or AUTHORS.
+       * maintain.texi (Standard Mailing Lists): recommend describing
+       mailing lists in README and/or AUTHORS.  Suggestion from Werner Koch.
 
 2011-10-12  Karl Berry  <address@hidden>
 
-       * maintain.texi (Copyright Papers): new option for US contributors
+       * maintain.texi (Copyright Papers): new option for US contributors.
 
 2011-09-26  Karl Berry  <address@hidden>
 

Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.207
retrieving revision 1.208
diff -u -b -r1.207 -r1.208
--- standards.texi      25 Sep 2011 23:38:06 -0000      1.207
+++ standards.texi      6 Dec 2011 00:20:37 -0000       1.208
@@ -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 September 25, 2011
address@hidden lastupdate December 4, 2011
 @c %**end of header
 
 @dircategory GNU organization
@@ -614,8 +614,8 @@
 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, using encodings
-such as UTF-8 and others.
+sequences of bytes that represent multibyte characters; 
+UTF-8 is the most important.
 
 @cindex error messages
 Check every system call for an error return, unless you know you wish
@@ -769,7 +769,9 @@
 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.
+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.
 
 The error message can also give both the starting and ending positions
 of the erroneous text.  There are several formats so that you can
@@ -3170,11 +3172,12 @@
 the application domain.  For example, if source code deals with the
 French Revolutionary calendar, it is OK if its literal strings contain
 accented characters in month names like ``Flor@'eal''.  Also, it is OK
-to use non-ASCII characters to represent proper names of contributors in
-change logs (@pxref{Change Logs}).
+(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, as one cannot in general mix encodings reliably.
+one encoding, certainly within a single file.  UTF-8 is likely to be
+the best choice.
 
 
 @node Quote Characters
@@ -4163,7 +4166,7 @@
 scope of what a software distribution needs to include.
 
 Referring to a web site that describes or recommends a non-free
-program is promoting that program, so please do not make links (or
+program is promoting that program, so please do not make links to (or
 mention by name) web sites that contain such material.  This policy is
 relevant particularly for the web pages for a GNU package.
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]