diff options
author | wl <wl> | 2008-10-04 13:25:29 +0000 |
---|---|---|
committer | wl <wl> | 2008-10-04 13:25:29 +0000 |
commit | 2b2d88b7af579c74a62bac601f441ee6cb325e0a (patch) | |
tree | 3cc9bf9bc271acbfab24b0492fc70e0b407a52fa | |
parent | ac388bf7ed1c99b779632d856e43aac287bf6c4c (diff) | |
download | groff-2b2d88b7af579c74a62bac601f441ee6cb325e0a.tar.gz |
s/with other words/in other words/
-rw-r--r-- | doc/groff.texinfo | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/groff.texinfo b/doc/groff.texinfo index f3a8f4b8..ce1055d5 100644 --- a/doc/groff.texinfo +++ b/doc/groff.texinfo @@ -4857,7 +4857,7 @@ the necessary glyphs. @pindex ec.tmac Due to the importance of the Euro glyph in Europe, the groff package now comes with a @sc{PostScript} font called @file{freeeuro.pfa} which -provides various glyph shapes for the Euro. With other words, +provides various glyph shapes for the Euro. In other words, @w{latin-9} encoding is supported for the @option{-Tps} device out of the box (@w{latin-2} isn't). @@ -5946,7 +5946,7 @@ The argument to @code{\R} usually has to be enclosed in quotes. @xref{Escapes}, for details on parameter delimiting characters. The @code{\R} escape doesn't produce an input token in @code{gtroff}; -with other words, it vanishes completely after @code{gtroff} has +in other words, it vanishes completely after @code{gtroff} has processed it. @endDefreq @@ -6985,7 +6985,7 @@ start-up, groff only assigns hyphenation codes to the letters @samp{a}-@samp{z} (mapped to themselves) and to the letters @samp{A}-@samp{Z} (mapped to @samp{a}-@samp{z}); all other hyphenation codes are set to zero. Normally, hyphenation patterns contain only -lowercase letters which should be applied regardless of case. With +lowercase letters which should be applied regardless of case. In other words, the words `FOO' and `Foo' should be hyphenated exactly the same way as the word `foo' is hyphenated, and this is what @code{hcode} is good for. Words which contain other letters won't be hyphenated @@ -7921,7 +7921,7 @@ The right way to write the above translation is @endExample @noindent -With other words, the first argument of @code{tr} should be an input +In other words, the first argument of @code{tr} should be an input character or entity, and the second one a glyph entity. @item @@ -10634,7 +10634,7 @@ Now consider this example. @noindent The definition of macro @code{bar} replaces the old object this name is -linked to. However, the alias to @code{foo} is still active! With +linked to. However, the alias to @code{foo} is still active! In other words, @code{foo} is still linked to the same object as @code{bar}, and the result of calling @code{bar} is an infinite, recursive loop which finally leads to an error. @@ -11575,7 +11575,7 @@ The highest and lowest point of the baseline, respectively, in @item rst @itemx rsb Like the @code{st} and @code{sb} registers, but takes account of the -heights and depths of glyphs. With other words, this gives the highest +heights and depths of glyphs. In other words, this gives the highest and lowest point of @var{text}. Values below the baseline are negative. @item ct |