doc: use ASCII in .texi files where UTF-8 isn't needed

[gnulib.git] / doc / intprops.texi

diff --git a/doc/intprops.texi b/doc/intprops.texi
index b4a8c6a..5ef7cb9 100644 (file)
--- a/doc/intprops.texi
+++ b/doc/intprops.texi
@@ -1,7 +1,7 @@
 @node Integer Properties
 @section Integer Properties
 
-@c Copyright (C) 011 Free Software Foundation, Inc.
+@c Copyright (C) 2011-2014 Free Software Foundation, Inc.
 
 @c Permission is granted to copy, distribute and/or modify this document
 @c under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -31,14 +31,14 @@ misbehave badly after overflow occurs.
 
 Many techniques have been proposed to attack these problems.  These
 include precondition testing, GCC's @option{-ftrapv} option, GCC's
-no-undefined-overflow branch, the As-if Infinitely Ranged (AIR) model
+no-undefined-overflow branch, the as-if infinitely ranged (AIR) model
 implemented in Clang, saturation semantics where overflow reliably
 yields an extreme value, the RICH static transformer to an
 overflow-checking variant, and special testing methods.  For more
 information about these techniques, see: Dannenberg R, Dormann W,
 Keaton D @emph{et al.},
 @url{http://www.sei.cmu.edu/library/abstracts/reports/10tn008.cfm,
-As-if Infinitely Ranged integer model -- 2nd ed.}, Software Engineering
+As-if infinitely ranged integer model}, 2nd ed., Software Engineering
 Institute Technical Note CMU/SEI-2010-TN-008, April 2010.
 
 Gnulib supports the precondition testing technique, as this is easy to
@@ -57,14 +57,15 @@ while the second, for integer types, is easier to use.
 @subsection Integer Type Determination
 
 @findex TYPE_IS_INTEGER
-@code{TYPE_IS_INTEGER (@var{t})} expands to an integer constant
-expression that is 1 if the arithmetic type @var{t} is a integer type.
+@code{TYPE_IS_INTEGER (@var{t})} expands to a constant
+expression that is 1 if the arithmetic type @var{t} is an integer type.
 @code{_Bool} counts as an integer type.
 
 @findex TYPE_SIGNED
-@code{TYPE_SIGNED (@var{t})} expands to an integer constant expression
+@code{TYPE_SIGNED (@var{t})} expands to a constant expression
 that is 1 if the arithmetic type @var{t} is a signed integer type or a
-floating type.
+floating type.  If @var{t} is an integer type, @code{TYPE_SIGNED (@var{t})}
+expands to an integer constant expression.
 
 Example usage:
 
@@ -142,7 +143,7 @@ in_off_t_range (intmax_t a)
 These macros yield 1 if the corresponding C operators might not yield
 numerically correct answers due to arithmetic overflow.  They do not
 rely on undefined or implementation-defined behavior.  They expand to
-integer constant expresssions if their arguments are.  Their
+integer constant expressions if their arguments are.  Their
 implementations are simple and straightforward, but they are typically
 harder to use than the integer type overflow macros.  @xref{Integer
 Type Overflow}.
@@ -256,7 +257,7 @@ These macros yield 1 if the corresponding C operators might not yield
 numerically correct answers due to arithmetic overflow of an integer
 type.  They work correctly on all known practical hosts, and do not
 rely on undefined behavior due to signed arithmetic overflow.  They
-expand to integer constant expresssions if their arguments are.  They
+expand to integer constant expressions if their arguments are.  They
 are easier to use than the integer range overflow macros
 (@pxref{Integer Range Overflow}).