texinfo ChangeLog doc/texinfo.txi

[karl]

CVSROOT:        /sources/texinfo
Module name:    texinfo
Changes by:     karl <karl>     13/01/12 16:56:42

Modified files:
        .              : ChangeLog 
        doc            : texinfo.txi 

Log message:
        (Internationalization of Document Strings): small changes

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/texinfo/ChangeLog?cvsroot=texinfo&r1=1.1510&r2=1.1511
http://cvs.savannah.gnu.org/viewcvs/texinfo/doc/texinfo.txi?cvsroot=texinfo&r1=1.517&r2=1.518

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/texinfo/texinfo/ChangeLog,v
retrieving revision 1.1510
retrieving revision 1.1511
diff -u -b -r1.1510 -r1.1511
--- ChangeLog   11 Jan 2013 22:45:18 -0000      1.1510
+++ ChangeLog   12 Jan 2013 16:56:40 -0000      1.1511
@@ -1,3 +1,8 @@
+2013-01-12  Karl Berry  <address@hidden>
+
+       * doc/texinfo.txi (Internationalization of Document Strings):
+       small changes.
+
 2013-01-11  Karl Berry  <address@hidden>
 
        * configure.ac (AC_PREREQ): remove, better to rely on

Index: doc/texinfo.txi
===================================================================
RCS file: /sources/texinfo/texinfo/doc/texinfo.txi,v
retrieving revision 1.517
retrieving revision 1.518
diff -u -b -r1.517 -r1.518
--- doc/texinfo.txi     8 Jan 2013 21:57:03 -0000       1.517
+++ doc/texinfo.txi     12 Jan 2013 16:56:41 -0000      1.518
@@ -1,5 +1,5 @@
 \input texinfo.tex    @c -*-texinfo-*-
address@hidden $Id: texinfo.txi,v 1.517 2013/01/08 21:57:03 pertusus Exp $
address@hidden $Id: texinfo.txi,v 1.518 2013/01/12 16:56:41 karl Exp $
 @c Ordinarily, Texinfo files have the extension .texi.  But texinfo.texi
 @c clashes with texinfo.tex on 8.3 filesystems, so we use texinfo.txi.
 
@@ -603,8 +603,8 @@
 * Invoking texi2any::        Running the translator from a shell.
 * texi2any Printed Output::  Calling @command{texi2dvi}.
 * Pointer Validation::       How to check that pointers point somewhere.
-* Internationalization of Strings::
 * Customization Variables::  Configuring @command{texi2any}.
+* Internationalization of Document Strings:: Translating program-inserted text.
 * texi2html::                An ancestor of @command{texi2any}.
 
 Customization Variables
@@ -13511,7 +13511,9 @@
 
 @cindex Internationalization
 Texinfo has some support for writing in languages other than English,
-although this area still needs considerable work.
+although this area still needs considerable work.  (If you are
+yourself helping to translate the fixed strings written to documents,
address@hidden of Document Strings}.)
 
 For a list of the various accented and special characters Texinfo
 supports, see @ref{Inserting Accents}.
@@ -16619,8 +16621,8 @@
 * Invoking texi2any::        Running the translator from a shell.
 * texi2any Printed Output::  Calling @command{texi2dvi}.
 * Pointer Validation::       How to check that pointers point somewhere.
-* Internationalization of Strings::
 * Customization Variables::  Configuring @command{texi2any}.
+* Internationalization of Document Strings:: Translating program-inserted text.
 * texi2html::                An ancestor of @command{texi2any}.
 @end menu
 
@@ -17283,102 +17285,6 @@
 @code{makeinfo} checks that every node except the `Top' node is
 referenced in a menu.
 
address@hidden Internationalization of Strings
address@hidden Internationalization of Strings in the Output Document
-
address@hidden I18n
address@hidden Internationalization of strings in the output document
address@hidden Output documentation, internationalization of
-
address@hidden documentlanguage @r{customization variable}
address@hidden writes some fixed strings in the generated document
-at various places: for cross references, in page footers, on the help
-page, alternate text for images, and so on.  The string chosen depends
-on the value of the @code{documentlanguage} at the time of the string 
-being output (@address@hidden@@documentlanguage}}, for the Texinfo command 
-interface).
-
address@hidden libintl-perl @r{Gettext implementation}
-The Gettext framework is used for those strings (@pxref{,,,
-gettext, Gettext}).  The @code{libintl-perl} package is used as
-the @code{gettext} implementation; more specifically, the pure Perl
-implementation is used, so Texinfo can support consistent behavior
-across all platforms and installations, which would not otherwise be
-possible.  @code{libintl-perl} is included in the Texinfo distribution
-and always installed, to be sure that it is available if needed.  It
-is also possible to use the system @code{gettext} (currently decided
-at build-time).  
-
address@hidden texinfo_document @r{Gettext domain}
address@hidden Perl format strings for translation
-The Gettext domain @samp{texinfo_document} is used for the strings.
-Translated strings are written as Texinfo, and may include
-@@-commands.  In translated strings, the varying parts of the string
-are not usually denoted by @code{%s} and the like, but by
address@hidden@address@hidden  (This convention is common for @code{gettext} in
-Perl and is fully supported in GNU Gettext; @pxref{perl-format,, Perl
-Format Strings, gettext, GNU Gettext}.)  For example, in the
-following, @address@hidden@}} will be replaced by the section name:
-
address@hidden
-see @address@hidden
address@hidden example
-
-These Perl-style brace format strings are used for two reasons: first,
-changing the order of @code{printf} arguments is only available since
address@hidden; second, and more importantly, the order of the
-argument is unpredictable, since @@-command expansion may lead to
-different orders depending on the output format.  The expansion of
-a translation string is done like this:
-
address@hidden
address@hidden First, the string is translated.  The locale 
-is @var{@@address@hidden@var{@@documentencoding}.
-
address@hidden @code{us-ascii} encoding, and translations
-If the @var{@@documentlanguage} has the form @var{ll_CC}, @var{ll_CC}
-is tried first, and then @var{ll}.  If that does not exist, and the
-encoding is not @code{us-ascii}, then @code{us-ascii} is tried.  The
-idea is that if there is a @code{us-ascii} encoding, it means that all
-the characters in the charset may be expressed as @@-commands.  For
-example, there is a @code{fr.us-ascii} locale that can accommodate any
-encoding, since all the address@hidden characters have associated
-@@-commands.  On the other hand, Japanese has only a translation
address@hidden, since there are no @@-commands for Japanese
-characters.
-
address@hidden Next, the string is expanded as Texinfo, and converted.
-The arguments are substituted; for example, @address@hidden@}} is 
-replaced by the corresponding actual argument.
-
address@hidden enumerate
-
-In the following example, @address@hidden@}}, @address@hidden@}}
-and @address@hidden@}} are the arguments of the string.  Since they
-are used in @code{@@uref}, their order is not predictable.
address@hidden@address@hidden, @address@hidden@}} and @address@hidden@}} are 
-substituted after the expansion:
-
address@hidden
-Generated on @@address@hidden@address@hidden@} using
-@@address@hidden@address@hidden, @@address@hidden@address@hidden@address@hidden
address@hidden example
-
-This approach is admittedly a bit complicated.  Its usefulness is that
-it supports having translations available in different encodings for
-encodings which can be covered by @@-commands, and also specifying how
-the formatting for some commands is done, independently of the output
-format---yet still be language dependent.  For example, an
address@hidden@@pxref} translation string may be:
-
address@hidden
-see @address@hidden section address@hidden@}\' in 
@@address@hidden@address@hidden@}
address@hidden example
-
address@hidden
-which allows specifying a string independently of the output format,
-but with rich formatting that may be translated appropriately in many
-languages.
 
 @node Customization Variables
 @section Customization Variables
@@ -18175,6 +18081,108 @@
 @end vtable
 
 
address@hidden Internationalization of Document Strings
address@hidden Internationalization of Document Strings
+
address@hidden I18n, of document strings
address@hidden Internationalization of document strings
address@hidden Document strings, internationalization of
address@hidden Output document strings, internationalization of
address@hidden Translating strings in output documents
+
address@hidden documentlanguage @r{customization variable}
address@hidden writes fixed strings into the output document at
+various places: cross references, page footers, the help page,
+alternate text for images, and so on.  The string chosen depends on
+the value of the @code{documentlanguage} at the time of the string
+being output (@address@hidden@@documentlanguage}}, for the Texinfo
+command interface).
+
address@hidden libintl-perl @r{Gettext implementation}
+The Gettext framework is used for those strings (@pxref{Top,,,
+gettext, Gettext}).  The @code{libintl-perl} package is used as the
address@hidden implementation; more specifically, the pure Perl
+implementation is used, so Texinfo can support consistent behavior
+across all platforms and installations, which would not otherwise be
+possible.  @code{libintl-perl} is included in the Texinfo distribution
+and always installed, to ensure that it is available if needed.  It is
+also possible to use the system @code{gettext} (the choice can be made
+at build-time).
+
address@hidden texinfo_document @r{Gettext domain}
address@hidden Perl format strings for translation
+The Gettext domain @samp{texinfo_document} is used for the strings.
+Translated strings are written as Texinfo, and may include
+@@-commands.  In translated strings, the varying parts of the string
+are not usually denoted by @code{%s} and the like, but by
address@hidden@address@hidden  (This convention is common for @code{gettext} in
+Perl and is fully supported in GNU Gettext; @pxref{perl-format,, Perl
+Format Strings, gettext, GNU Gettext}.)  For example, in the
+following, @address@hidden@}} will be replaced by the section name:
+
address@hidden
+see @address@hidden
address@hidden example
+
+These Perl-style brace format strings are used for two reasons: first,
+changing the order of @code{printf} arguments is only available since
address@hidden; second, and more importantly, the order of arguments
+is unpredictable, since @@-command expansion may lead to different
+orders depending on the output format.
+
+The expansion of a translation string is done like this:
+
address@hidden
address@hidden First, the string is translated.  The locale 
+is @var{@@address@hidden@var{@@documentencoding}.
+
address@hidden @code{us-ascii} encoding, and translations
+If the @var{@@documentlanguage} has the form @samp{ll_CC}, that is
+tried first, and then just @samp{ll}.  If that does not exist, and the
+encoding is not @code{us-ascii}, then @code{us-ascii} is tried.
+
+The idea is that if there is a @code{us-ascii} encoding, it means that
+all the characters in the charset may be expressed as @@-commands.
+For example, there is a @code{fr.us-ascii} locale that can accommodate
+any encoding, since all the address@hidden characters have associated
+@@-commands.  On the other hand, Japanese has only a translation
address@hidden, since there are no @@-commands for Japanese
+characters.
+
address@hidden Next, the string is expanded as Texinfo, and converted.
+The arguments are substituted; for example, @address@hidden@}} is 
+replaced by the corresponding actual argument.
+
address@hidden enumerate
+
+In the following example, @address@hidden@}}, @address@hidden@}}
+and @address@hidden@}} are the arguments of the string.  Since they
+are used in @code{@@uref}, their order is not predictable.
address@hidden@address@hidden, @address@hidden@}} and @address@hidden@}} are 
+substituted after the expansion:
+
address@hidden
+Generated on @@address@hidden@address@hidden@} using
+@@address@hidden@address@hidden, @@address@hidden@address@hidden@address@hidden
address@hidden example
+
+This approach is admittedly a bit complicated.  Its usefulness is that
+it supports having translations available in different encodings for
+encodings which can be covered by @@-commands, and also specifying how
+the formatting for some commands is done, independently of the output
+format---yet still be language-dependent.  For example, the
address@hidden@@pxref} translation string can be like this:
+
address@hidden
+see @address@hidden section address@hidden@}\' in 
@@address@hidden@address@hidden@}
address@hidden example
+
address@hidden
+which allows for specifying a string independently of the output
+format, while nevertheless with rich formatting it may be translated
+appropriately in many languages.
+
+
 @node texi2html
 @section @command{texi2html}: Ancestor of @command{texi2any}
 @pindex texi2html
@@ -21900,7 +21908,7 @@
 as:
 
 @example
-$Id: texinfo.txi,v 1.517 2013/01/08 21:57:03 pertusus Exp $
+$Id: texinfo.txi,v 1.518 2013/01/12 16:56:41 karl Exp $
 @end example
 
 (This is potentially useful in all sources that use version control,