Re: typos

[Ralf Wildenhues]

Hello Bruno,

* Bruno Haible wrote on Tue, Aug 08, 2006 at 02:59:47PM CEST:
> 
> Thanks for the spelling fixes. I'm applying the obvious typos and
> spelling fixes.

Thanks.

> I'm not applying the en_GB -> en_US changes.

While I could care less about which of the two spellings were used in
manuals, I do think that they should be uniform.  On the grounds that
the majority of documentation is written in en_US, I choose that
usually.

There is a very practical reason for me to prefer uniformity: it
allows me to read faster, with less interruption.  However short,
my eyes stumble over inconsistent spelling.  YMMV.

> I'm also not applying the following changes because I cannot find
> justification for it in the dictionary:
>     "i.e.", "hard-code", "proven"

Oh, surely there are contentious points other than locale.  I simply
went with the dictionary I had, and some personal taste, where I was
unsure.

But one point is rather uncontentious IMHO: if you do not add a comma
after 'i.e.' and it does not end a sentence, then it should be followed
by '@:' in texinfo format, for proper spacing in DVI output; this is
documented in the Texinfo manual.  See an updated patch below which does
that for the places that you did not change, and also for the 'the the'
that you missed amongst the Americanisms, and the superfluous comma that
I found just now.  ;-)

> and those for which my dictionary says the opposite of yours:
>     "labelled"

Oh well.  What's the dictionary you use, if I may ask?
For my patches I should credit Vim 7 and its spell feature,
and http://dict.leo.org/ and bad memory for special cases.

Cheers,
Ralf

gettext-runtime/doc:
        * nls.texi: Fix 1 typo.

gettext-runtime/libasprintf:
        * autosprintf.texi: Fix 1 typo.

gettext-tools/doc:
        * gettext.texi: Fix 8 typos.
        * msgcat.texi: Fix 1 typo.
        * msgcomm.texi: Fix 1 typo.
        * msgfilter.texi: Fix 1 typo.

Index: gettext-runtime/doc/nls.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-runtime/doc/nls.texi,v
retrieving revision 1.17
diff -u -r1.17 nls.texi
--- gettext-runtime/doc/nls.texi        8 Aug 2006 11:33:46 -0000       1.17
+++ gettext-runtime/doc/nls.texi        8 Aug 2006 19:44:17 -0000
@@ -93,7 +93,7 @@
 will probably detect the previously built and installed @file{libintl.a}
 file and will decide to use this.  This might not be desirable.
 You should use the more recent version of the GNU @code{gettext}
-library.  I.e. if the file @file{intl/VERSION} shows that the library
+library.  I.e.@: if the file @file{intl/VERSION} shows that the library
 which comes with this package is more recent, you should use
 
 @example
Index: gettext-runtime/libasprintf/autosprintf.texi
===================================================================
RCS file: 
/cvsroot/gettext/gettext/gettext-runtime/libasprintf/autosprintf.texi,v
retrieving revision 1.5
diff -u -r1.5 autosprintf.texi
--- gettext-runtime/libasprintf/autosprintf.texi        12 Apr 2006 15:02:09 
-0000      1.5
+++ gettext-runtime/libasprintf/autosprintf.texi        8 Aug 2006 19:44:17 
-0000
@@ -134,7 +134,7 @@
 
 An instance of class @code{autosprintf} just contains a string with the
 formatted output result. Such an instance is usually allocated as an
-automatic storage variable, i.e. on the stack, not with @code{new} on the
+automatic storage variable, i.e.@: on the stack, not with @code{new} on the
 heap.
 
 The constructor @code{autosprintf (const char *format, ...)} takes a format
Index: gettext-tools/doc/gettext.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/gettext.texi,v
retrieving revision 1.96
diff -u -r1.96 gettext.texi
--- gettext-tools/doc/gettext.texi      8 Aug 2006 11:33:46 -0000       1.96
+++ gettext-tools/doc/gettext.texi      8 Aug 2006 19:44:22 -0000
@@ -2156,7 +2156,7 @@
 exists because the original code does not pass any parameters.
 
 @code{xgettext} of course could make a wrong decision the other way
-round, i.e. a string marked as a format string actually is not a format
+round, i.e.@: a string marked as a format string actually is not a format
 string.  In this case the @code{msgfmt} might give too many warnings and
 would prevent translating the @file{.po} file.  The method to prevent
 this wrong decision is similar to the one used above, only the comment
@@ -3999,7 +3999,7 @@
 @efindex address@hidden, PO Mode command}
 However, PO files initially created by PO mode itself, while marking
 strings in source files, are normalised differently.  So are PO
-files resulting of the the @samp{M-x normalize} command.  Until these
+files resulting of the @samp{M-x normalize} command.  Until these
 discrepancies between PO mode and other GNU @code{gettext} tools get
 fully resolved, the translator should stay aware of normalisation issues.
 
@@ -6002,9 +6002,9 @@
 their program free, or want other kinds of freedom.  The simplest
 answer is ``normally not''.
 
-The @code{gettext-runtime} part of GNU @code{gettext}, i.e. the
+The @code{gettext-runtime} part of GNU @code{gettext}, i.e.@: the
 contents of @code{libintl}, is covered by the GNU Library General Public
-License.  The @code{gettext-tools} part of GNU @code{gettext}, i.e. the
+License.  The @code{gettext-tools} part of GNU @code{gettext}, i.e.@: the
 rest of the GNU @code{gettext} package, is covered by the GNU General
 Public License.
 
@@ -9131,7 +9131,7 @@
 @noindent
 
 The @code{GetString} function returns a string's translation.  Note that this
-function returns null when a translation is missing (i.e. not even found in
+function returns null when a translation is missing (i.e.@: not even found in
 the fallback resource file).
 
 @item
@@ -9795,7 +9795,7 @@
 @end example
 
 The exact rule is: You can omit the surrounding quotes, when the hash
-key is a valid C (!) identifier, i.e. when it starts with an
+key is a valid C (!) identifier, i.e.@: when it starts with an
 underscore or an ASCII letter and is followed by an arbitrary number
 of underscores, ASCII letters or digits.  Other Unicode characters
 are @emph{not} allowed, regardless of the @code{use utf8} pragma.
@@ -10158,7 +10158,7 @@
 @end group
 @end example
 
-Please do not forget, that the line breaks are real, i.e. they
+Please do not forget that the line breaks are real, i.e.@: they
 translate into newline characters that will consequently show up in
 the resulting POT file.
 
Index: gettext-tools/doc/msgcat.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/msgcat.texi,v
retrieving revision 1.3
diff -u -r1.3 msgcat.texi
--- gettext-tools/doc/msgcat.texi       22 Oct 2003 10:49:14 -0000      1.3
+++ gettext-tools/doc/msgcat.texi       8 Aug 2006 19:44:22 -0000
@@ -10,7 +10,7 @@
 It finds messages which are common to two or more of the specified PO files.
 By using the @code{--more-than} option, greater commonality may be requested
 before messages are printed.  Conversely, the @code{--less-than} option may be
-used to specify less commonality before messages are printed (i.e.
+used to specify less commonality before messages are printed (i.e.@:
 @samp{--less-than=2} will only print the unique messages).  Translations,
 comments and extract comments will be cumulated, except that if
 @code{--use-first} is specified, they will be taken from the first PO file
Index: gettext-tools/doc/msgcomm.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/msgcomm.texi,v
retrieving revision 1.3
diff -u -r1.3 msgcomm.texi
--- gettext-tools/doc/msgcomm.texi      22 Oct 2003 10:49:15 -0000      1.3
+++ gettext-tools/doc/msgcomm.texi      8 Aug 2006 19:44:22 -0000
@@ -9,7 +9,7 @@
 of the specified PO files.
 By using the @code{--more-than} option, greater commonality may be requested
 before messages are printed.  Conversely, the @code{--less-than} option may be
-used to specify less commonality before messages are printed (i.e.
+used to specify less commonality before messages are printed (i.e.@:
 @samp{--less-than=2} will only print the unique messages).  Translations,
 comments and extract comments will be preserved, but only from the first
 PO file to define them.  File positions from all PO files will be
Index: gettext-tools/doc/msgfilter.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/msgfilter.texi,v
retrieving revision 1.5
diff -u -r1.5 msgfilter.texi
--- gettext-tools/doc/msgfilter.texi    29 Mar 2006 11:31:35 -0000      1.5
+++ gettext-tools/doc/msgfilter.texi    8 Aug 2006 19:44:22 -0000
@@ -143,7 +143,7 @@
 
 @item --keep-header
 @opindex address@hidden, @code{msgfilter} option}
-Keep the header entry, i.e. the message with @samp{msgid ""}, unmodified,
+Keep the header entry, i.e.@: the message with @samp{msgid ""}, unmodified,
 instead of filtering it.  By default, the header entry is subject to
 filtering like any other message.