From: John Darrington <john@darrington.wattle.id.au>
Date: Sun, 25 Oct 2020 07:41:59 +0000 (+0100)
Subject: User manual: Use italic typeface for latin abbreviations
X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4056e461fd8f8d9ba7feca63c73d2f50a2048b63;p=pspp

User manual: Use italic typeface for latin abbreviations
---

diff --git a/doc/combining.texi b/doc/combining.texi
index 9b013fe99b..5eb8ff54ab 100644
--- a/doc/combining.texi
+++ b/doc/combining.texi
@@ -88,7 +88,7 @@ Each @subcmd{FILE} subcommand may be followed by any number of @subcmd{RENAME}
 subcommands that specify a parenthesized group or groups of variable
 names as they appear in the input file, followed by those variables'
 new names, separated by an equals sign (@subcmd{=}),
-e.g. @subcmd{/RENAME=(OLD1=NEW1)(OLD2=NEW2)}.  To rename a single
+@i{e.g.} @subcmd{/RENAME=(OLD1=NEW1)(OLD2=NEW2)}.  To rename a single
 variable, the parentheses may be omitted: @subcmd{/RENAME=@var{old}=@var{new}}.
 Within a parenthesized group, variables are renamed simultaneously, so
 that @subcmd{/RENAME=(@var{A} @var{B}=@var{B} @var{A})} exchanges the
diff --git a/doc/data-io.texi b/doc/data-io.texi
index 81911983c8..747e32d9b5 100644
--- a/doc/data-io.texi
+++ b/doc/data-io.texi
@@ -190,7 +190,7 @@ The DATASET DECLARE command creates a new dataset that is initially
 ``empty,'' that is, it has no dictionary or data.  If a dataset with
 the given name already exists, this has no effect.  The new dataset
 can be used with commands that support output to a dataset,
-e.g. AGGREGATE (@pxref{AGGREGATE}).
+@i{e.g.} AGGREGATE (@pxref{AGGREGATE}).
 
 @vindex DATASET CLOSE
 The DATASET CLOSE command deletes a dataset.  If the active dataset is
diff --git a/doc/expressions.texi b/doc/expressions.texi
index c205024a79..acffd925a9 100644
--- a/doc/expressions.texi
+++ b/doc/expressions.texi
@@ -636,7 +636,7 @@ empty string.
 Returns the number produced when @var{string} is interpreted according
 to format specifier @var{format}.  If the format width @var{w} is less
 than the length of @var{string}, then only the first @var{w}
-characters in @var{string} are used, e.g.@: @code{NUMBER("123", F3.0)}
+characters in @var{string} are used, @i{e.g.}@: @code{NUMBER("123", F3.0)}
 and @code{NUMBER("1234", F3.0)} both have value 123.  If @var{w} is
 greater than @var{string}'s length, then it is treated as if it were
 right-padded with spaces.  If @var{string} is not in the correct
diff --git a/doc/files.texi b/doc/files.texi
index cdc23fc2f5..54c26c89b7 100644
--- a/doc/files.texi
+++ b/doc/files.texi
@@ -610,12 +610,12 @@ value is 1.
 The @subcmd{VARIABLES} subcommand, which is required, specifies the positions
 at which each variable can be found.  For each variable, specify its
 name, followed by its start and end column separated by @samp{-}
-(e.g.@: @samp{0-9}), followed by an input format type (e.g.@:
-@samp{F}) or a full format specification (e.g.@: @samp{DOLLAR12.2}).
+(@i{e.g.}@: @samp{0-9}), followed by an input format type (@i{e.g.}@:
+@samp{F}) or a full format specification (@i{e.g.}@: @samp{DOLLAR12.2}).
 For this command, columns are numbered starting from 0 at
 the left column.  Introduce the variables in the second and later
 lines of a case by a slash followed by the number of the line within
-the case, e.g.@: @samp{/2} for the second line.
+the case, @i{e.g.}@: @samp{/2} for the second line.
 
 @subsubheading Examples
 
diff --git a/doc/flow-control.texi b/doc/flow-control.texi
index 6c7a88ded1..bbb2f41c89 100644
--- a/doc/flow-control.texi
+++ b/doc/flow-control.texi
@@ -122,7 +122,7 @@ variable PRINT would not be substituted into the word PRINTOUT.
 
 New variable names used as replacements are not automatically created
 as variables, but only if used in the code block in a context that
-would create them, e.g.@: on a @cmd{NUMERIC} or @cmd{STRING} command
+would create them, @i{e.g.}@: on a @cmd{NUMERIC} or @cmd{STRING} command
 or on the left side of a @cmd{COMPUTE} assignment.
 
 Any command may appear within @subcmd{DO REPEAT}, including nested @subcmd{DO REPEAT}
diff --git a/doc/invoking.texi b/doc/invoking.texi
index 9590f093b8..fbc7009e5c 100644
--- a/doc/invoking.texi
+++ b/doc/invoking.texi
@@ -98,7 +98,7 @@ Use @samp{-} as @var{output-file} to write output to standard output.
 
 If no @option{-o} option is used, then @pspp{} writes text and CSV
 output to standard output and other kinds of output to whose name is
-based on the format, e.g.@: @file{pspp.pdf} for PDF output.
+based on the format, @i{e.g.}@: @file{pspp.pdf} for PDF output.
 
 @item @option{-O @var{option}=@var{value}}
 Sets an option for the output file configured by a preceding
@@ -108,7 +108,7 @@ A few options that apply generically are listed below.
 @item @option{-O format=@var{format}}
 @pspp{} uses the extension of the file name given on @option{-o} to
 select an output format.  Use this option to override this choice by
-specifying an alternate format, e.g.@: @option{-o pspp.out -O format=html} to
+specifying an alternate format, @i{e.g.}@: @option{-o pspp.out -O format=html} to
 write HTML to a file named @file{pspp.out}.  Use @option{--help} to
 list the available formats.
 
@@ -226,8 +226,8 @@ given on @option{-o} does not end in @file{.pdf}, @file{.ps}, or
 @file{.svg}.
 
 @item @option{-O paper-size=@var{paper-size}}
-Paper size, as a name (e.g.@: @code{a4}, @code{letter}) or
-measurements (e.g.@: @code{210x297}, @code{8.5x11in}).
+Paper size, as a name (@i{e.g.}@: @code{a4}, @code{letter}) or
+measurements (@i{e.g.}@: @code{210x297}, @code{8.5x11in}).
 
 The default paper size is taken from the @env{PAPERSIZE} environment
 variable or the file indicated by the @env{PAPERCONF} environment
@@ -456,7 +456,7 @@ output just below the table as a single field prefixed by
 
 @item Footnotes
 Within a table, footnote markers are output as bracketed letters
-following the cell's contents, e.g.@tie{}@samp{[a]}, @samp{[b]},
+following the cell's contents, @i{e.g.}@tie{}@samp{[a]}, @samp{[b]},
 @enddots{}  The footnotes themselves are output following the body of
 the table, as a separate two-column table introduced with a line that
 says @samp{Footnotes:}.  Each row in the table represent one footnote:
diff --git a/doc/language.texi b/doc/language.texi
index 55ca55ffdc..9fcfde677b 100644
--- a/doc/language.texi
+++ b/doc/language.texi
@@ -115,7 +115,7 @@ tokens, @samp{8945} and @samp{.}, if it is the last token on a line.
 @cindex case-sensitivity
 Strings are literal sequences of characters enclosed in pairs of
 single quotes (@samp{'}) or double quotes (@samp{"}).  To include the
-character used for quoting in the string, double it, e.g.@:
+character used for quoting in the string, double it, @i{e.g.}@:
 @samp{'it''s an apostrophe'}.  White space and case of letters are
 significant inside strings.
 
@@ -158,7 +158,7 @@ Most of these appear within the syntax of commands, but the period
 punctuator only as the last character on a line (except white space).
 When it is the last non-space character on a line, a period is not
 treated as part of another token, even if it would otherwise be part
-of, e.g.@:, an identifier or a floating-point number.
+of, @i{e.g.}@:, an identifier or a floating-point number.
 @end table
 
 @node Commands
@@ -1235,7 +1235,7 @@ Time or dates narrower than the field width are right-justified within
 the field.
 
 When a time or date exceeds the field width, characters are trimmed from
-the end until it fits.  This can occur in an unusual situation, e.g.@:
+the end until it fits.  This can occur in an unusual situation, @i{e.g.}@:
 with a year greater than 9999 (which adds an extra digit), or for a
 negative value on MTIME, TIME, or DTIME (which adds a leading minus sign).
 
@@ -1366,9 +1366,9 @@ name of a file as a string, that is, enclosed within @samp{'} or
 A file name string that begins or ends with @samp{|} is treated as the
 name of a command to pipe data to or from.  You can use this feature
 to read data over the network using a program such as @samp{curl}
-(e.g.@: @code{GET '|curl -s -S http://example.com/mydata.sav'}), to
+(@i{e.g.}@: @code{GET '|curl -s -S http://example.com/mydata.sav'}), to
 read compressed data from a file using a program such as @samp{zcat}
-(e.g.@: @code{GET '|zcat mydata.sav.gz'}), and for many other
+(@i{e.g.}@: @code{GET '|zcat mydata.sav.gz'}), and for many other
 purposes.
 
 @pspp{} also supports declaring named file handles with the @cmd{FILE
@@ -1382,9 +1382,9 @@ for more information.
 
 In some circumstances, @pspp{} must distinguish whether a file handle
 refers to a system file or a portable file.  When this is necessary to
-read a file, e.g.@: as an input file for @cmd{GET} or @cmd{MATCH FILES},
+read a file, @i{e.g.}@: as an input file for @cmd{GET} or @cmd{MATCH FILES},
 @pspp{} uses the file's contents to decide.  In the context of writing a
-file, e.g.@: as an output file for @cmd{SAVE} or @cmd{AGGREGATE}, @pspp{}
+file, @i{e.g.}@: as an output file for @cmd{SAVE} or @cmd{AGGREGATE}, @pspp{}
 decides based on the file's name: if it ends in @samp{.por} (with any
 capitalization), then @pspp{} writes a portable file; otherwise, @pspp{}
 writes a system file.
diff --git a/doc/pspp-convert.texi b/doc/pspp-convert.texi
index 4c31f5229a..17acffa607 100644
--- a/doc/pspp-convert.texi
+++ b/doc/pspp-convert.texi
@@ -77,7 +77,7 @@ specify the format for unrecognized extensions.
 @item @option{-O @var{format}}
 @itemx @option{--output-format=@var{format}}
 Sets the output format, where @var{format} is one of the extensions
-listed above, e.g.: @option{-O csv}.  Use @option{--help} to list
+listed above, @i{e.g.}: @option{-O csv}.  Use @option{--help} to list
 the supported output formats.
 
 @item -c @var{maxcases}
@@ -98,7 +98,7 @@ By default, @command{pspp-convert} includes all the variables from the
 input file.  Use this option to list specific variables to include;
 any variables not listed will be dropped.  The variables in the output
 file will also be reordered into the given order.  The variable list
-may use @code{TO} in the same way as in PSPP syntax, e.g.@: if the
+may use @code{TO} in the same way as in PSPP syntax, @i{e.g.}@: if the
 dictionary contains consecutive variables @code{a}, @code{b},
 @code{c}, and @code{d}, then @option{--keep='a to d'} will include all
 of them (and no others).
diff --git a/doc/transformation.texi b/doc/transformation.texi
index 5635903df2..cad85b3fb9 100644
--- a/doc/transformation.texi
+++ b/doc/transformation.texi
@@ -218,7 +218,7 @@ On most modern computers, this is  @acronym{ASCII} or a superset thereof.
 
 The aggregation functions listed above exclude all user-missing values
 from calculations.  To include user-missing values, insert a period
-(@samp{.}) at the end of the function name.  (e.g.@: @samp{SUM.}).
+(@samp{.}) at the end of the function name.  (@i{e.g.}@: @samp{SUM.}).
 (Be aware that specifying such a function as the last token on a line
 will cause the period to be interpreted as the end of the command.)
 
diff --git a/doc/utilities.texi b/doc/utilities.texi
index 6549e94f2c..7128545c14 100644
--- a/doc/utilities.texi
+++ b/doc/utilities.texi
@@ -263,7 +263,7 @@ this is not desired.
 The following example runs @code{rsync} to copy a file from a remote
 server to the local file @file{data.txt}, writing @code{rsync}'s own
 output to @file{rsync-log.txt}.  PSPP displays the command's error
-output, if any.  If @code{rsync} needs to prompt the user (e.g.@: to
+output, if any.  If @code{rsync} needs to prompt the user (@i{e.g.}@: to
 obtain a password), the command fails.  Only if the @code{rsync}
 succeeds, PSPP then runs the @code{sha512sum} command.
 
@@ -349,7 +349,7 @@ the following forms:
 @item @subcmd{LOCALE}
 The encoding used by the system locale, or as overridden by the
 @cmd{SET} command (@pxref{SET}).  On GNU/Linux and other Unix-like systems,
-environment variables, e.g.@: @env{LANG} or @env{LC_ALL}, determine the
+environment variables, @i{e.g.}@: @env{LANG} or @env{LC_ALL}, determine the
 system locale.
 
 @item @var{charset_name}
diff --git a/doc/variables.texi b/doc/variables.texi
index a47de44afd..c1f8fa96bb 100644
--- a/doc/variables.texi
+++ b/doc/variables.texi
@@ -396,7 +396,7 @@ The @subcmd{DISPLAY} subcommand displays information about defined multiple
 response sets.  Its syntax is the same as the @subcmd{DELETE} subcommand.
 
 Multiple response sets are saved to and read from system files by,
-e.g., the @cmd{SAVE} and @cmd{GET} command.  Otherwise, multiple
+@i{e.g.}, the @cmd{SAVE} and @cmd{GET} command.  Otherwise, multiple
 response sets are currently used only by third party software.
 
 @node NUMERIC