Here's a proposed patch that attempts to address the above issues.
Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.210
diff -c -r1.210 standards.texi
*** standards.texi 23 Dec 2011 00:30:29 -0000 1.210
--- standards.texi 23 Dec 2011 05:50:22 -0000
***************
*** 2374,2380 ****
* System Functions:: Portability and ``standard'' library
functions.
* Internationalization:: Techniques for internationalization.
* Character Set:: Use ASCII by default.
! * Quote Characters:: Use `...' in the C locale.
* Mmap:: How you can safely use @code{mmap}.
@end menu
--- 2374,2380 ----
* System Functions:: Portability and ``standard'' library
functions.
* Internationalization:: Techniques for internationalization.
* Character Set:: Use ASCII by default.
! * Quote Characters:: Use "..." or '...' in the C locale.
* Mmap:: How you can safely use @code{mmap}.
@end menu
***************
*** 3049,3060 ****
around each string that might need translation---like this:
@example
! printf (gettext ("Processing file `%s'..."));
@end example
@noindent
This permits GNU gettext to replace the string @code{"Processing file
! `%s'..."} with a translated version.
Once a program uses gettext, please make a point of writing calls to
@code{gettext} when you add new strings that call for translation.
--- 3049,3060 ----
around each string that might need translation---like this:
@example
! printf (gettext ("Processing file \"%s\"..."), file);
@end example
@noindent
This permits GNU gettext to replace the string @code{"Processing file
! \"%s\"..."} with a translated version.