[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Groff-commit] groff ./INSTALL ./NEWS ./PROBLEMS ./README doc/...
|
From: |
Werner LEMBERG |
|
Subject: |
[Groff-commit] groff ./INSTALL ./NEWS ./PROBLEMS ./README doc/... |
|
Date: |
Sat, 21 Jan 2006 14:14:09 +0000 |
CVSROOT: /cvsroot/groff
Module name: groff
Branch:
Changes by: Werner LEMBERG <address@hidden> 06/01/21 14:14:09
Modified files:
. : INSTALL NEWS PROBLEMS README
doc : groff.texinfo pic.ms webpage.ms
man : groff.man groff_char.man
Log message:
Don't use future tense.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/groff/groff/INSTALL.diff?tr1=1.13&tr2=1.14&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/groff/groff/NEWS.diff?tr1=1.206&tr2=1.207&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/groff/groff/PROBLEMS.diff?tr1=1.26&tr2=1.27&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/groff/groff/README.diff?tr1=1.14&tr2=1.15&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/groff/groff/doc/groff.texinfo.diff?tr1=1.224&tr2=1.225&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/groff/groff/doc/pic.ms.diff?tr1=1.29&tr2=1.30&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/groff/groff/doc/webpage.ms.diff?tr1=1.22&tr2=1.23&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/groff/groff/man/groff.man.diff?tr1=1.74&tr2=1.75&r1=text&r2=text
http://cvs.savannah.gnu.org/viewcvs/groff/groff/man/groff_char.man.diff?tr1=1.22&tr2=1.23&r1=text&r2=text
Patches:
Index: groff/INSTALL
diff -u groff/INSTALL:1.13 groff/INSTALL:1.14
--- groff/INSTALL:1.13 Thu Dec 16 13:09:54 2004
+++ groff/INSTALL Sat Jan 21 14:14:09 2006
@@ -8,7 +8,7 @@
(For instructions how to build groff with the MinGW tools for
MS-Windows, see the file README.MinGW.)
-groff is written in C++, so you will need a C++ compiler. The C++
+groff is written in C++, so you need a C++ compiler. The C++
source files use a suffix of `.cpp', so your C++ compiler must be able
to handle this. If you don't already have a C++ compiler, I suggest
gcc 2.7.1 or later (gcc version 2 includes GNU C++ as well as GNU C).
@@ -27,8 +27,8 @@
PAGE=xxx ./configure
-where `xxx' should be either `A4' or `letter'. Note that this will only
-affect the paper selection of some device drivers like grops (which can
+where `xxx' should be either `A4' or `letter'. Note that this only
+affects the paper selection of some device drivers like grops (which can
be still overridden on the command line). For compatibility with
ditroff, the default page length in gtroff is always 11 inches. The
page length can be changed with the `pl' request.
@@ -44,7 +44,7 @@
groff.dvi', `make groff.pdf', or `make groff.html', respectively, in the
`doc' subdirectory (after configuring the groff package). Note that you
need texinfo version 4.6 as a prerequisite. Neither older versions nor
-texinfo 4.7 (due to a bug) will work.
+texinfo 4.7 (due to a bug) work.
If you have problems, read the PROBLEMS file. If this doesn't help
send a bug report using the form in the file BUG-REPORT.
Index: groff/NEWS
diff -u groff/NEWS:1.206 groff/NEWS:1.207
--- groff/NEWS:1.206 Mon Oct 17 07:06:41 2005
+++ groff/NEWS Sat Jan 21 14:14:09 2006
@@ -128,15 +128,15 @@
heading, defined by `NH' or `SH', before any automatic page break.
GROWPS
- Sets the first level of heading (set with `NH') which will keep the
+ Sets the first level of heading (set with `NH') which keeps the
same point size as body text.
PSINCR
Sets the point size increment for each level of heading (set with
`NH'), below the threshold level set by `GROWPS'; e.g., if
- \n[PS] = 10, \n[GROWPS] = 3 and \n[PSINCR] = 2.0p, then `.NH 1' will
- produce 14pt headings, `.NH 2' will produce 12pt, and all other levels
- will remain at 10pt (because \n[PS] = 10).
+ \n[PS] = 10, \n[GROWPS] = 3 and \n[PSINCR] = 2.0p, then `.NH 1'
+ produces 14pt headings, `.NH 2' produces 12pt, and all other
+ levels remain at 10pt (because \n[PS] = 10).
. The `SH' macro now accepts a numeric argument, to make heading size
match that of `NH' with same argument value when the `GROWPS'/`PSINCR'
@@ -187,7 +187,7 @@
files named in `so' and `psbb' requests, and files named in \X'ps: file'
and \X'ps: import' escapes.
-o If option `-V' is used more than once, the commands will be both printed
+o If option `-V' is used more than once, the commands are both printed
on standard error and run.
Troff
@@ -342,7 +342,7 @@
.composite from to
- will change the mapping while a composite glyph name is constructed.
+ changes the mapping while a composite glyph name is constructed.
To make \[A ho] yield the expected result,
.composite ho u0328
@@ -737,7 +737,7 @@
final `0' can be omitted.
o `trin' (translate input) is a new request which is similar to `tr' with
- the exception that the `asciify' request will use the character code (if
+ the exception that the `asciify' request uses the character code (if
any) before the character translation. Example:
.trin ax
@@ -858,12 +858,11 @@
The image position parameter names in `IMG' have been changed to `-L',
`-R', and `-C'.
- New macro `PIMG' for inclusion of a PNG image (it will automatically
- convert it into an EPS file if not -Thtml is used).
+ New macro `PIMG' for inclusion of a PNG image (it automatically
+ converts it into an EPS file if not -Thtml is used).
New macro `MPIMG' for putting a PNG image into the left or right margin
- (it will automatically convert it into an EPS file if not
- -Thtml is used).
+ (it automatically converts it into an EPS file if not -Thtml is used).
New macros `HnS', `HnE' to start and end a header line block.
@@ -1019,7 +1018,7 @@
o A new manual page `ditroff.7' is available.
-o The groff texinfo manual will now be installed, together with a bunch
+o The groff texinfo manual is installed now, together with a bunch
of examples.
o A new keyword `papersize' has been added to the DESC file format. Its
@@ -1234,10 +1233,10 @@
inserts its argument into the intermediate output format. The syntax
is similar to .tm1, allowing leading whitespace.
-o The new `spreadwarn' request will make troff warn if spaces in an output
+o The new `spreadwarn' request makes troff warn if spaces in an output
line are widened by a given limit or more.
-o Use `warnscale' to change the scaling indicator troff will use for
+o Use `warnscale' to change the scaling indicator troff uses for
warning messages.
o A new request `dei' (define indirect) has been added. The first and
@@ -1444,7 +1443,7 @@
The obsolete `.LINK' macro has been removed.
.URL, .FTP, and .MAILTO macros now accept an optional third argument which
-will be immediately appended to the second argument (to be used with
+is immediately appended to the second argument (to be used with
punctuation, for example).
Grodvi
@@ -1479,7 +1478,7 @@
Gxditview
---------
-Simplified installation: The Imakefile will now be configured (by groff's
+Simplified installation: The Imakefile is now configured (by groff's
configure script).
Documentation
@@ -1531,7 +1530,7 @@
groff should now be Y2k safe (fixes contributed by Paul Eggert
<address@hidden>).
-Following the GNU standards, groff will now use the prefix `/usr/local/' as
+Following the GNU standards, groff now uses the prefix `/usr/local/' as
the default instead of replacing an existent groff binary.
groff, troff, nroff, and pic now support the -U flag to activate unsafe
@@ -1628,8 +1627,8 @@
VERSION 1.09
============
-\(rn will now produce a character that has the traditional metrics,
-and will form corners with \(ul and \(br. This means that it will not
+\(rn now produces a character that has the traditional metrics,
+and form corners with \(ul and \(br. This means that it does not
align properly with \(sr. Instead there's a new character
\[radicalex] which aligns with \(sr; this is used by eqn for doing
square roots.
@@ -1652,7 +1651,7 @@
Troff
-----
-The escape sequence \V[xxx] will interpolate the value of the
+The escape sequence \V[xxx] interpolates the value of the
environment variable xxx.
Tbl
@@ -1757,7 +1756,7 @@
The `shc' request tells troff which character to insert (instead of
the default \(hy) when a word is hyphenated at a line break.
-A font name of 0 (zero) in the DESC file will cause no font to be
+A font name of 0 (zero) in the DESC file causes no font to be
mounted on the corresponding font position. This is useful for
arranging that special fonts are mounted on positions on which users
are not likely explicitly to mount fonts. All groff devices now avoid
@@ -1812,7 +1811,7 @@
The default value of the -b option is specified by a `broken' command
in the DESC file.
-With the -g option, grops will generate PostScript code that guesses
+With the -g option, grops generates PostScript code that guesses
the page height. This allows documents to be printed on both letter
(8.5x11) and A4 paper without change.
@@ -1840,13 +1839,13 @@
which have the same meaning as $r and $R in earlier groff releases.
In addition, if the $r or $R register is set to a value that would be
correct for for the BSD -me macros and a low resolution device is not
-being used, then an appropriate value for the $v or $V register will
-be derived from the $r or $R register.
+being used, then an appropriate value for the $v or $V register
+is derived from the $r or $R register.
The groff -me macros work with -C and (I think) with Unix troff.
For backward compatibility with BSD -me, the \*{ and \*} strings are
-also available as \*[ and \*]. Of course, \*[ will only be usable
+also available as \*[ and \*]. Of course, \*[ is only usable
with -C.
The \*T string has been deleted. Use \*(Tm instead.
@@ -1881,7 +1880,7 @@
Grotty
------
-Horizontal and vertical lines drawn with \D'l ...' will be rendered
+Horizontal and vertical lines drawn with \D'l ...' are rendered
using -, | and + characters. This is intended to give reasonable
results with boxed tables. It won't work well with pic.
@@ -1894,7 +1893,7 @@
as -mdoc.old. The grog script has been enhanced so that it can
usually determine whether a document requires the old or new versions.
-With -TX75, -TX100 and -TXps, the PSPIC macro will produce a box
+With -TX75, -TX100 and -TXps, the PSPIC macro produces a box
around where the picture would appear with -Tps.
VERSION 1.04
@@ -1941,7 +1940,7 @@
The code field in lines in the charset section of font description
files is now allowed to contain an arbitrary integer (previously it
was required to lie between 0 and 255). Currently grops and grodvi
-use only the low order 8 bits of the value. Grodvi will use the
+use only the low order 8 bits of the value. Grodvi uses the
complete value; however, this is unlikely to be useful with
traditional TeX tools (.tfm files only allow 8 bit character codes.)
@@ -2007,7 +2006,7 @@
--------
Parts of xditview have been rewritten so that it can be used with the
-output of gtroff -Tps. groff -TXps will run gtroff -Tps with
+output of gtroff -Tps. groff -TXps runs gtroff -Tps with
gxditview.
There is a new menu entry `Print' which brings up a dialog box for
@@ -2026,13 +2025,13 @@
for devices with `hor' equal to 1, but it makes groff with -Tascii or
-Tlatin1 behave more like nroff in its treatment of these scale
indicators. Accordingly tmac.tty now calls the `nroff' request so
-that the `n' condition will be true.
+that the `n' condition is true.
The device-specific macros (tmac.ps, tmac.dvi, tmac.tty and tmac.X)
have been made to work at least somewhat with -C. In particular the
special characters defined by these macros now work with -C.
-groff -Tdvi -p will now pass pic the -x flag; this will enable filling
+groff -Tdvi -p now passes pic the -x flag; this enables filling
of arrowheads and boxes, provided that your dvi driver supports the
latest version of the tpic specials.
@@ -2041,7 +2040,7 @@
There is a new `-N' option that tells eqn not to allow newlines in
delimiters. This allows eqn to recover better from missing closing
-delimiters. The groff command will pass on a `-N' option to eqn.
+delimiters. The groff command passes on a `-N' option to eqn.
Grops
-----
@@ -2092,15 +2091,15 @@
request.
There is a request `hym' that can ensure that when the current
-adjustment mode is not `b' a line will not be hyphenated if it is no
+adjustment mode is not `b' a line is not hyphenated if it is no
more than a given amount short, and a request `hys' that can ensure
-that when the current adjustment mode is `b' a line will not be
+that when the current adjustment mode is `b' a line is not
hyphenated if it can be justified by adding no more than a given
amount of extra space to each word space.
There is a request `rj' similar to `ce' that right justifies lines.
-A warning of type `space' will be given when a call is made to an
+A warning of type `space' is given when a call is made to an
undefined request or macro with a name longer than two characters, and
the first two characters of the name make a name that is defined.
This is intended to find places where a space has been omitted been a
@@ -2202,7 +2201,7 @@
that caused a vertical position trap to be sprung.
The `cf' request now behaves sensibly in a diversion. If used in a
-diversion, it will now arrange for the file to be copied to the output
+diversion, it now arranges for the file to be copied to the output
when the diversion is reread.
There is a new request `trf' (transparent file) similar to `cf', but
@@ -2251,7 +2250,7 @@
`if' and `define' constructs) can now be of the form `{ anything }'.
If the `linethick' variable is negative (as it now is initially),
-lines will be drawn with a thickness proportional to the current point
+lines are drawn with a thickness proportional to the current point
size.
The `rand' function now takes no arguments and returns a number between
Index: groff/PROBLEMS
diff -u groff/PROBLEMS:1.26 groff/PROBLEMS:1.27
--- groff/PROBLEMS:1.26 Wed May 18 07:03:06 2005
+++ groff/PROBLEMS Sat Jan 21 14:14:09 2006
@@ -137,7 +137,7 @@
Read the section on incompatibilities in groff_diff(7). Try using
the -C option. Alternatively there's the sed script
-`tmac/fixmacros.sed' which will attempt to edit a file of macros so
+`tmac/fixmacros.sed' which attempts to edit a file of macros so
that it can be used with groff without the -C flag.
----------------------------------------------------------------------
@@ -159,7 +159,7 @@
Yes, it does. You may need to compile fonts with Metafont at these
magnifications. The CompileFonts script in the devdvi/generate
-directory may help you to do this. (It will take a *long* time on
+directory may help you to do this. (It takes a *long* time on
slow computers.)
----------------------------------------------------------------------
@@ -203,8 +203,8 @@
.ps \" restore the previous point size
-(with a tab after the .ps) will NOT restore the previous point-size;
-instead it will be silently ignored. Since this is very likely to be
+(with a tab after the .ps) does NOT restore the previous point-size;
+instead it is silently ignored. Since this is very likely to be
an error, gtroff can give a warning about it. If you want to align
comments, you can do it like this:
@@ -215,7 +215,7 @@
* I don't like the page headers and footers produced by groff -man.
There seem to be many different styles of page header and footer
-produced by different versions of the -man macros. You will need to
+produced by different versions of the -man macros. You need to
put modified macros from tmac/an-old.tmac into man.local. More
information is available in groff_man(7).
@@ -235,8 +235,8 @@
\n(st and \n(sb aren't supposed to give the height and depth of the
string rather they give the minimum and maximum vertical displacement
-of the baseline. For example for \v'2u'\v'-3u', \n(st will be 1 and
-\n(sb will be -2. The height and depth of the string is available in
+of the baseline. For example for \v'2u'\v'-3u', \n(st is 1 and
+\n(sb is -2. The height and depth of the string is available in
the \n[rst] and \n[rsb] registers: these are groff extensions.
----------------------------------------------------------------------
@@ -247,13 +247,13 @@
The -man documentation says that the default scale indicator for TP
macro is `n'. The groff -man macros implement this correctly, so that
-the argument will be evaluated as if it were
+the argument is evaluated as if it were
\w'label'n+2n
The Unix -man macros don't implement this correctly (probably because
it's hard to do in Unix troff); they just append `n' to the entire
-argument, so that it will be evaluated as if it were
+argument, so that it is evaluated as if it were
\w'label'u+2n
@@ -412,7 +412,7 @@
with a body of `help' to address@hidden)
If an EPS file to be included via \X'ps: import' does not start with
-`%!PS-Adobe-...', gtroff will still include the file, but grops will
+`%!PS-Adobe-...', gtroff still includes the file, but grops does
not add any fonts to the generated output file that are listed in the
EPS file, even though the files are listed in the `download' file and
are available in the devps directory.
@@ -550,7 +550,7 @@
make install tmac_wrap=""
-Then no wrapper files are produced, and `-ms' will use groff's `ms'
+Then no wrapper files are produced, and `-ms' uses groff's `ms'
macros.
----------------------------------------------------------------------
@@ -744,13 +744,13 @@
[This has been fixed in z/OS V1R3 (aka OS/390 R13).]
There is a bug in the Language Environment (LE) whereby the test
-program for static destructors fails. You will see the message
-`configure: error: a working C++ compiler is required'
+program for static destructors fails. You see the message
+`configure: error: a working C++ compiler is required'.
Applying PTF UQ42006 is supposed to fix this, but the test program is
still returning the wrong value (1). To work around this problem, you
can comment out the following in the configure script (near line 2029).
-This will effectively bypass the test (static constructors and
+This effectively bypasses the test (static constructors and
destructors do actually work properly):
#if { (eval echo "$as_me:2029: \"$ac_link\"") >&5
Index: groff/README
diff -u groff/README:1.14 groff/README:1.15
--- groff/README:1.14 Fri Jun 24 19:55:03 2005
+++ groff/README Sat Jan 21 14:14:09 2006
@@ -10,8 +10,8 @@
`xditview' previewer, and an implementation of the `-mm' macros
contributed by Joergen Haegg (address@hidden).
-See the file `INSTALL' for installation instructions. You will
-require a C++ compiler.
+See the file `INSTALL' for installation instructions. You require
+a C++ compiler.
The file `NEWS' describes recent user-visible changes to `groff'.
@@ -35,8 +35,8 @@
(Note that you need an `ssh' client for security reasons.)
-This will create a subdirectory, `~/cvswork/groff', with a "checked
-out" copy of the `CVS' repository. An update of this working copy may
+This creates a subdirectory, `~/cvswork/groff', with a `checked
+out' copy of the `CVS' repository. An update of this working copy may
be achieved, at any later time by invoking the commands
cd ~/cvswork/groff
@@ -80,9 +80,9 @@
building from `CVS' sources (either a checked out working copy, or a
daily snapshot). They are not required for building from a stable
release tarball. Also note that the version numbers stated are the
-minimum supported. No version of `texinfo' < 4.8 will work, and the
+minimum supported. No version of `texinfo' < 4.8 works, and the
original release of `bison' 1.875 is known not to work; you *may* find
-that `bison' releases < 1.875 will work, but in case of difficulty,
+that `bison' releases < 1.875 work, but in case of difficulty,
please update to a later version *before* posting a bug report.
For *all* sources, you need ghostscript for creation of either `PDF' or
@@ -91,7 +91,7 @@
formats, then these packages are unnecessary.
In Linux Debian, the installation of `texinfo' is dangerous. For it
-creates a file `install-info' that will block the system installation.
+creates a file `install-info' that blocks the system installation.
So the created `/usr/local/bin/install-info' must be renamed.
The `groff' configure script searches for the X11 headers and
@@ -104,8 +104,8 @@
this is to make sure that FSF has all the information it needs to fix
the bug. At the very least, read the `BUG-REPORT' form and make sure
that you supply all the information that it asks for. Even if you are
-not sure that something is a bug, report it using `BUG-REPORT': this will
-enable us to determine whether it really is a bug or not.
+not sure that something is a bug, report it using `BUG-REPORT': this
+enables us to determine whether it really is a bug or not.
Three mailing lists are available:
Index: groff/doc/groff.texinfo
diff -u groff/doc/groff.texinfo:1.224 groff/doc/groff.texinfo:1.225
--- groff/doc/groff.texinfo:1.224 Fri Nov 18 21:12:56 2005
+++ groff/doc/groff.texinfo Sat Jan 21 14:14:09 2006
@@ -1295,8 +1295,8 @@
@address@hidden'ps: import}} and @address@hidden'ps: file}} escapes.
@end itemize
-The current directory is always searched first. This option may be specified
-more than once; the directories will be searched in the order specified. No
+The current directory is always searched first. This option may be specified
+more than once; the directories are searched in the order specified. No
directory search is performed for files specified using an absolute path.
@end table
@@ -1455,7 +1455,7 @@
@cindex font path
@cindex path, for font files
All font files are kept in the @dfn{font directories} which constitute
-the @dfn{font path}. The file search functions will always append the
+the @dfn{font path}. The file search functions always append the
directory @address@hidden, where @var{name} is the name of the
output device. Assuming, say, DVI output, and @file{/foo/bar} as a
font directory, the font files for @code{grodvi} must be in
@@ -2203,11 +2203,11 @@
request, in preference to such a @samp{.ll @var{length}} request.
In particular, note that in nroff mode, the request @samp{.ll 65n},
(with any @var{length} expression which evaluates equal to address@hidden,
-i.e., the formatter's default line length in nroff mode), will @emph{not}
-set the line length to address@hidden (it will be adjusted to the @code{man}
+i.e., the formatter's default line length in nroff mode), does @emph{not}
+set the line length to address@hidden (it is adjusted to the @code{man}
macro package's default setting of address@hidden), whereas the use of the
@option{-rLL=65n} option, or the @samp{.nr LL 65n}
-request @emph{will} establish a line length of address@hidden
+request @emph{does} establish a line length of address@hidden
@item address@hidden
Set title length to @var{length}. If not specified, the title length
@@ -2949,7 +2949,7 @@
@endDefmpreg
@Defmpreg {PSINCR, ms}
-Defines an increment in point size, which will be applied to section
+Defines an increment in point size, which is applied to section
headings at nesting levels below the value specified in @code{GROWPS}.
The value of @code{PSINCR} should be specified in points, with the
@dmn{p} scaling factor, and may include a fractional component; for
@@ -2964,9 +2964,9 @@
@Defmpreg {GROWPS, ms}
Defines the heading level below which the point size increment set by
@code{PSINCR} becomes effective. Section headings at and above the
-level specified by @code{GROWPS} will be printed at the point size set
+level specified by @code{GROWPS} are printed at the point size set
by @code{PS}; for each level below the value of @code{GROWPS}, the
-point size will be increased in steps equal to the value of
+point size is increased in steps equal to the value of
@code{PSINCR}. Setting @code{GROWPS} to any value less address@hidden
disables the incremental heading size feature.
@@ -3025,7 +3025,7 @@
should be kept together, to avoid orphan lines at the bottom of a
page. If a new paragraph is started close to the bottom of a page,
and there is insufficient space to accommodate @code{PORPHANS} lines
-before an automatic page break, then the page break will be forced,
+before an automatic page break, then the page break is forced,
before the start of the paragraph.
Effective: next paragraph.
@@ -3040,7 +3040,7 @@
to the bottom of a page, and there is insufficient space to
accommodate both the heading and at least @code{HORPHANS} lines of the
following paragraph, before an automatic page break, then the page
-break will be forced before the heading.
+break is forced before the heading.
Effective: next paragraph.
@@ -4010,7 +4010,7 @@
@cindex @code{ms} macros, multiple columns
@cindex multiple columns address@hidden
-The @file{ms} macros can set text in as many columns as will
+The @file{ms} macros can set text in as many columns as do
reasonably fit on the page. The following macros are available; all
of them force a page break if a multi-column mode is already set.
However, if the current mode is single-column, starting a multi-column
@@ -4848,7 +4848,7 @@
@endExample
@noindent
-will fail if you use the Euro character in the input. Usually, this
+fails if you use the Euro character in the input. Usually, this
limitation is present only for devices which have a limited set of
output glyphs (e.g.@: @option{-Tascii} and @option{-Tlatin1}); for other
devices it is usually sufficient to install proper fonts which contain
@@ -6139,7 +6139,7 @@
Decimal numbers with as many digits as specified. So, @samp{00} would
result in printing numbers as 01, 02, 03,@address@hidden
-In fact, any digit instead of zero will do; @code{gtroff} only counts
+In fact, any digit instead of zero does work; @code{gtroff} only counts
how many digits are specified. As a consequence, @code{af}'s default
format @samp{1} could be specified as @samp{0} also (and exactly this is
returned by the @code{\g} escape, see below).
@@ -6933,7 +6933,7 @@
@file{troffrc} loads hyphenation patterns and exceptions for American
English (in files @file{hyphen.us} and @file{hyphenex.us}).
-A second call to @code{hpf} (for the same language) will replace the
+A second call to @code{hpf} (for the same language) replaces the
hyphenation patterns with the new ones.
Invoking @code{hpf} causes an error if there is no current hyphenation
@@ -7621,7 +7621,7 @@
escape character @samp{\} is restored. It can be also used to
re-enable the escape mechanism after an @code{eo} request.
-Note that changing the escape character globally will likely break
+Note that changing the escape character globally likely breaks
macro packages since @code{gtroff} has no mechanism to `intern' macros,
i.e., to convert a macro definition into an internal form which is
independent of its representation (@TeX{} has this mechanism).
@@ -8220,7 +8220,7 @@
@cindex @code{\R}, after @code{\c}
@code{\c} works on the output level. Anything after this escape on the
same line is ignored, except @code{\R} which works as usual. Anything
-before @code{\c} on the same line will be appended to the current partial
+before @code{\c} on the same line is appended to the current partial
output line. The next non-command line after an interrupted line counts
as a new input line.
@@ -8232,7 +8232,7 @@
@cindex no-fill mode, and @code{\c}
@cindex mode, no-fill, and @code{\c}
If no-fill mode is active (using the @code{nf} request), the next input
-text line after @code{\c} will be handled as a continuation of the same
+text line after @code{\c} is handled as a continuation of the same
input text line.
@Example
@@ -8247,7 +8247,7 @@
@cindex fill mode, and @code{\c}
@cindex mode, fill, and @code{\c}
If fill mode is active (using the @code{fi} request), a word interrupted
-with @code{\c} will be continued with the text on the next input text line,
+with @code{\c} is continued with the text on the next input text line,
without an intervening space.
@Example
@@ -8459,7 +8459,7 @@
text text text
@endExample
address@hidden will then automatically cause a page break if there is space
address@hidden then automatically causes a page break if there is space
for one line only.
@endDefreq
@@ -8477,7 +8477,7 @@
@cindex @code{sv} request, and no-space mode
@cindex @code{os} request, and no-space mode
Both @code{sv} and @code{os} ignore no-space mode. While the @code{sv}
-request allows negative values for @var{space}, @code{os} will ignore
+request allows negative values for @var{space}, @code{os} ignores
them.
@endDefreq
@@ -8735,10 +8735,10 @@
family and the name of the current style. For example, if the current
font address@hidden and font address@hidden is associated with style
@samp{R} and the current font family is @samp{T}, then font
address@hidden will be used. If the current font is not a style, then the
address@hidden is used. If the current font is not a style, then the
current family is ignored. If the requests @code{cs}, @code{bd},
@code{tkf}, @code{uf}, or @code{fspecial} are applied to a style,
-they will instead be applied to the member of the current family
+they are instead applied to the member of the current family
corresponding to that style.
@address@hidden be a non-negative integer value.
@@ -9040,7 +9040,7 @@
@itemize @bullet
@item
A glyph for Unicode character address@hidden@address@hidden which is
-not a composite character will be named
+not a composite character is named
@address@hidden@address@hidden@address@hidden@r{]]}}. @var{X} must be an
uppercase hexadecimal digit. Examples: @code{u1234}, @code{u008E},
@code{u12DB8}. The largest Unicode value is 0x10FFFF. There must be at
@@ -9051,7 +9051,7 @@
are not allowed too.
@item
-A glyph representing more than a single input character will be named
+A glyph representing more than a single input character is named
@display
@samp{u} @var{component1} @samp{_} @var{component2} @samp{_} @var{component3}
@dots{}
@@ -9072,10 +9072,10 @@
@item
groff maintains a table to decompose all algorithmically derived glyph
names which are composites itself. For example, @code{u0100} (@sc{latin
-letter a with macron}) will be automatically decomposed into
+letter a with macron}) is automatically decomposed into
@code{u0041_0304}. Additionally, a glyph name of the GGL is preferred
to an algorithmically derived glyph name; groff also automatically does
-the mapping. Example: The glyph @code{u0045_0302} will be mapped to
+the mapping. Example: The glyph @code{u0045_0302} is mapped to
@code{^E}.
@item
@@ -9108,12 +9108,12 @@
@itemize @bullet
@item
-Any component which is found in the GGL will be converted to the
+Any component which is found in the GGL is converted to the
@address@hidden form.
@item
Any component @address@hidden which is found in the list of
-decomposable glyphs will be decomposed.
+decomposable glyphs is decomposed.
@item
The resulting elements are then concatenated with @samp{_} inbetween,
@@ -9121,7 +9121,7 @@
@end itemize
No check for the existence of any component (similar to @code{tr}
-request) will be done.
+request) is done.
Examples:
@@ -11582,7 +11582,7 @@
right address@hidden@var{n}.
@cindex @address@hidden'f @dots{}'}} and horizontal resolution
-Don't use this command! It has the serious drawback that it will be
+Don't use this command! It has the serious drawback that it is
always rounded to the next integer multiple of the horizontal resolution
(the value of the @code{hor} keyword in the @file{DESC} file). Use
@code{\M} (@pxref{Colors}) or @address@hidden'Fg @dots{}'}} instead.
@@ -11921,7 +11921,7 @@
An important fact to consider while designing macros is that diversions and
traps do not interact normally. For example, if a trap invokes a header
macro (while outputting a diversion) which tries to change the font on the
-current page, the effect will not be visible before the diversion has
+current page, the effect is not visible before the diversion has
completely been printed (except for input protected with @code{\!} or
@code{\?}) since the data in the diversion is already formatted. In most
cases, this is not the expected behaviour.
@@ -12544,7 +12544,7 @@
occurs at the outer nesting level write the @code{filename} to
@code{stderr}. The position of the image, @var{P}, must be specified
and must be one of @code{l}, @code{r}, @code{c}, address@hidden@code{i} (left,
-right, centered, inline). @var{filename} will be associated with the
+right, centered, inline). @var{filename} is associated with the
production of the next inline image.
@end table
@endDefesc
@@ -13470,7 +13470,7 @@
groff -rDB=1 file
@endExample
-If it is known in advance that there will be many errors and no useful
+If it is known in advance that there are many errors and no useful
output, @code{gtroff} can be forced to suppress formatted output with
the @option{-z} flag.
@@ -13581,7 +13581,7 @@
@endExample
@noindent
-will cause a warning if @code{gtroff} must add address@hidden or more for each
+causes a warning if @code{gtroff} must add address@hidden or more for each
interword space in a line.
This request is active only if text is justified to both margins (using
@@ -13943,7 +13943,7 @@
@address@hidden be completely independent of the current
escape character, use @code{\(rs} which represents a reverse solidus
(backslash) glyph.} To store, for some reason, an escape sequence in a
-diversion that will be interpreted when the diversion is reread, either
+diversion that is interpreted when the diversion is reread, either
use the traditional @code{\!} transparent output facility, or, if this
is unsuitable, the new @code{\?} escape sequence.
@@ -14522,7 +14522,7 @@
Note that single characters can have the eighth bit set, as can the
names of fonts and special characters. The names of characters and
fonts can be of arbitrary length. A character that is to be printed
-will always be in the current font.
+is always in the current font.
A string argument is always terminated by the next whitespace
character (space, tab, or newline); an embedded @samp{#} character is
@@ -15581,7 +15581,7 @@
represented as @samp{£} in @acronym{HTML} 4.0.
Anything on the line after the @var{entity-name} field resp.@: after
address@hidden will be ignored.
address@hidden is ignored.
The @var{metrics} field has the form:
Index: groff/doc/pic.ms
diff -u groff/doc/pic.ms:1.29 groff/doc/pic.ms:1.30
--- groff/doc/pic.ms:1.29 Wed Apr 27 20:52:34 2005
+++ groff/doc/pic.ms Sat Jan 21 14:14:09 2006
@@ -10,7 +10,7 @@
.\" This document was written for free use and redistribution by
.\" Eric S. Raymond <address@hidden> in August 1995.
.\"
-.\" $Id: pic.ms,v 1.29 2005/04/27 20:52:34 wl Exp $
+.\" $Id: pic.ms,v 1.30 2006/01/21 14:14:09 wl Exp $
.\"
.\" Set a proper TeX and LaTeX
.ie t \{\
@@ -77,7 +77,7 @@
\[lq]DWB pic\[rq]. Details on the history of the program are given at the
end of this document.
.PP
-In this document, the \fIgpic\/\fP(1) extensions will be marked as such.
+In this document, the \fIgpic\/\fP(1) extensions are marked as such.
.
.
.NH 1
@@ -97,7 +97,7 @@
.NH 2
PIC Error Messages
.PP
-If you make a \fBpic\fP syntax error, \fIgpic\/\fP(1) will issue an
+If you make a \fBpic\fP syntax error, \fIgpic\/\fP(1) issues an
error message in the standard \fIgcc\/\fP(1)-like syntax. A typical
error message looks like this,
.KS
@@ -195,7 +195,7 @@
.PP
The box, ellipse, circle, and block composite objects are \fIclosed\/\fR;
lines, arrows, arcs and splines are \fIopen\fP. This distinction
-will often be important in explaining command modifiers.
+is often important in explaining command modifiers.
.PP
Figure \n[H1]-2 was produced by the following \fBpic\fP program,
which introduces some more basic concepts:
@@ -315,8 +315,8 @@
.PP
Sizes are specified in inches. If you don't like inches, it's
possible to set a global style variable \fBscale\fP that changes the
-unit. Setting \fBscale = 2.54\fP will effectively change the internal
-unit to centimeters (all other size variable values will be scaled
+unit. Setting \fBscale = 2.54\fP effectively changes the internal
+unit to centimeters (all other size variable values are scaled
correspondingly).
.
.NH 2
@@ -373,7 +373,7 @@
.CE "2: Result of \fBbox width 3 \"text far too long\"\fP"
.PP
This modifier takes a dimension in inches. There is also a \[lq]height\[rq]
-modifier that will change a box's height. The \fBwidth\fP keyword may
+modifier that changes a box's height. The \fBwidth\fP keyword may
be abbreviated to \fBwid\fP; the \fBheight\fP keyword to \fBht\fP.
.
.NH 2
@@ -627,9 +627,9 @@
Arrowhead style is controlled by the style variable \fBarrowhead\fP.
The DWB and GNU versions interpret it differently. DWB defaults to
open arrowheads and an \fBarrowhead\fP value of\~2; the Kernighan
-paper says a value of\~7 will make solid arrowheads. GNU \fBgpic\fP
+paper says a value of\~7 makes solid arrowheads. GNU \fBgpic\fP
defaults to solid arrowheads and an \fBarrowhead\fP value of\~1; a
-value of\~0 will produce open arrowheads. Note that solid arrowheads are
+value of\~0 produces open arrowheads. Note that solid arrowheads are
always filled with the current outline color.
.
.NH 2
@@ -685,11 +685,11 @@
.PP
GNU \fBgpic\fP makes some additional guarantees. A fill value greater
than 1 can also be used: this means fill with the shade of gray that
-is currently being used for text and lines. Normally this will be
+is currently being used for text and lines. Normally this is
black, but output devices may provide a mechanism for changing this.
The invisible attribute does not affect the filling of objects. Any
-text associated with a filled object will be added after the object
-has been filled, so that the text will not be obscured by the filling.
+text associated with a filled object is added after the object
+has been filled, so that the text is not obscured by the filling.
.PP
The closed-object modifier \fBsolid\fP is equivalent to \fBfill\fP
with the darkest fill value (DWB \fBpic\fP had this capability but
@@ -752,14 +752,14 @@
In GNU \fBgpic\fR, objects can have an
.B aligned
attribute.
-This will only work when the postprocessor is
+This only works if the postprocessor is
\fBgrops\fP.
Any text associated with an object having the
.B aligned
-attribute will be rotated about the center of the object
+attribute is rotated about the center of the object
so that it is aligned in the direction from the start point
to the end point of the object.
-Note that this attribute will have no effect for objects whose start and
+Note that this attribute has no effect for objects whose start and
end points are coincident.
.
.
@@ -930,13 +930,13 @@
.PE
.CE "1: Example of label use"
The \fBat\fP statement in the fourth line uses the label \fBA\fP (the
-behavior of \fBat\fP will be explained in the next section). We'll
+behavior of \fBat\fP is explained in the next section). We'll
see later on that labels are most useful for referring to block composite
objects.
.PP
Labels are not constants but variables (you can view colon as a sort
of assignment). You can say something like \fBA: A + (1,0);\fP
-and the effect will be to reassign the label \fBA\fR to designate a
+and the effect is to reassign the label \fBA\fR to designate a
position one inch to the right of its old value.
.
.
@@ -1257,7 +1257,7 @@
If you say \fBline .\|.\|.\& chop \fIr1\fP chop \fIr2\fP\fR with \fIr1\fP
and \fIr2\fP both numbers, you can vary the amount of chopping at both
ends. You can use this in combination with trigonometric functions
-to write code that will deal with more complex intersections.
+to write code that deals with more complex intersections.
.
.
.NH 1
@@ -1389,7 +1389,7 @@
.DE
.KE
.LP
-the arrow in the last line will be attached to object \fBP\fP, not
+the arrow in the last line is attached to object \fBP\fP, not
object \fBQ\fP.
.PP
In DWB \fBpic\fP, only references one level deep into enclosed blocks
@@ -1469,7 +1469,7 @@
in GNU \fBgpic\fR, scientific notation in C's `e' format (like
\f(CW5e-2\fP) is accepted.
.PP
-Anywhere a number is expected, the language will also accept a
+Anywhere a number is expected, the language also accepts a
variable. Variables may be the built-in style variable described in
the last section, or new variables created by assignment.
.PP
@@ -1482,7 +1482,7 @@
the block.
.PP
GNU \fBgpic\fP supports an alternate form of assignment using \fB:=\fP.
-The variable must already be defined, and the value will be assigned to
+The variable must already be defined, and the value is assigned to
that variable without creating a variable local to the current block.
For example, this
.KS
@@ -1566,7 +1566,7 @@
.R
.DE
.LP
-The arguments (if any) will be substituted for tokens \fB$1\fP, \fB$2\fP
+The arguments (if any) are substituted for tokens \fB$1\fP, \fB$2\fP
\&.\|.\|.\& \fB$n\fP
appearing in the replacement text.
.PP
@@ -1605,7 +1605,7 @@
box with .nw at 6th last [].nw wid 6*jwidth ht jheight;
# Use {} to avoid changing position from last box draw.
- # This is necessary so move in any direction will work as expected
+ # This is necessary so move in any direction works as expected
{"Jumpers in state $1$2$3$4$5$6" at last box .s + (0,-0.2);}
}
@@ -1651,7 +1651,7 @@
box with .nw at 6th last [].nw wid 6*jwidth ht jheight;
# Use {} to avoid changing position from last box draw.
- # This is necessary so move in any direction will work as expected
+ # This is necessary so move in any direction works as expected
{"Jumpers in state $1$2$3$4$5$6" at last box .s + (0,-0.2);}
}
@@ -1667,7 +1667,7 @@
.PP
One detail the example above does not illustrate is the fact that
macro argument parsing is not token-oriented. If you call
-\fBjumper(\ 1\ )\fP, the value of $1 will be \fB"\ 1\ "\fP. You could
+\fBjumper(\ 1\ )\fP, the value of $1 is \fB"\ 1\ "\fP. You could
even call \fBjumper(big\ string)\fP to give $1 the value
\fB"big\ string"\fP.
.PP
@@ -1699,7 +1699,7 @@
.DE
.LP
inserts the contents of \fIfilename\fR in the \fBpic\fP input stream.
-Any \fB.PS\fP/\fB.PE\fP pair in the file will be ignored. You
+Any \fB.PS\fP/\fB.PE\fP pair in the file is ignored. You
can use this to include pre-generated images.
.PP
A variant of this statement replicates the \fBcopy thru\fP feature of
@@ -1884,7 +1884,7 @@
.B *
then
.I variable
-will instead be multiplied by
+is multiplied instead by
\fIexpr3\fR.
The value of
.I expr3
@@ -1926,7 +1926,7 @@
pairs may instead be balanced pairs of
braces ({ and\~}) as in the \fBsh\fR command. In either case, the
\fIif-true\fR may contain balanced pairs of braces. None of these
-delimiters will be seen inside strings.
+delimiters are seen inside strings.
.PP
All the usual relational operators my be used in conditional expressions;
\fB!\&\fP (logical negation, not factorial), \fB&&\fP, \fB|\||\fP, \fB==\fP,
@@ -1947,16 +1947,16 @@
.NH 2
Scaling Arguments
.PP
-The DWB \fIpic\/\fP(1) program will accept one or two arguments to
+The DWB \fIpic\/\fP(1) program accepts one or two arguments to
\&\fB.PS\fP, which is interpreted as a width and height in inches to
which the results of \fIpic\/\fP(1) should be scaled (width and height
scale independently). If there is only one argument, it is
-interpreted as a width to scale the picture to, and height will be
+interpreted as a width to scale the picture to, and height is
scaled by the same proportion.
.PP
-GNU \fBgpic\fP is less general; it will accept a single width to scale
+GNU \fBgpic\fP is less general; it accepts a single width to scale
to, or a zero width and a maximum height to scale to. With
-two non-zero arguments, it will scale to the maximum height.
+two non-zero arguments, it scales to the maximum height.
.
.NH 2
How Scaling is Handled
@@ -1993,7 +1993,7 @@
.vs
.KE
.LP
-Equivalent definition will be supplied by GNU \fIpic\/\fP(1) if you use
+Equivalent definition is supplied by GNU \fIpic\/\fP(1) if you use
the \-mpic option; this should make it usable with macro pages other
than \fIms\/\fR(1).
.PP
@@ -2015,7 +2015,7 @@
By default, input lines that begin with a period are passed to the
postprocessor, embedded at the corresponding point in the output.
Messing with horizontal or vertical spacing is an obvious recipe for
-bugs, but point size and font changes will usually be safe.
+bugs, but point size and font changes are usually safe.
.PP
Point sizes and font changes are also safe within text strings, as
long as they are undone before the end of string.
@@ -2069,7 +2069,7 @@
\*[tx] mode is enabled by the
.B \-t
option.
-In \*[tx] mode, pic will define a vbox called
+In \*[tx] mode, pic defines a vbox called
.B \egraph
for each picture; the name can be changed with the pseudo-variable
.B figname
@@ -2082,7 +2082,7 @@
.RE
.LP
Actually, since the vbox has a height of zero (it is defined with \evtop)
-this will produce slightly more vertical space above the picture than
+this produces slightly more vertical space above the picture than
below it;
.RS
.LP
@@ -2122,7 +2122,7 @@
Anything else may well produce undesirable results; use at your own risk.
Lines beginning with a period are not given any special treatment.
.PP
-The \*[tx] mode of \fIpic\/\fP(1) will \fInot\fP translate \fBtroff\fP
+The \*[tx] mode of \fIpic\/\fP(1) does \fInot\fP translate \fBtroff\fP
font and size changes included in text strings!
.PP
Here an example how to use \fBfigname\fP.
@@ -2441,7 +2441,7 @@
A string either enclosed by `{' and `}' or with \fIX\fP and \fIX\fP,
where \fIX\fP doesn't occur in the string.
.IP \s[-1]BALANCED-BODY\s[0]
-Delimiters as in \s[-1]BALANCED-TEXT\s[0]; the body will be interpreted as
+Delimiters as in \s[-1]BALANCED-TEXT\s[0]; the body is interpreted as
`\fB\[la]command\[ra].\|.\|.\fP'.
.IP \s[-1]FILENAME\s[0]
The name of a file. This has the same semantics as \s[-1]TEXT\s[0].
@@ -2480,7 +2480,7 @@
.PP
The arguments, if present, represent the width and height of the picture,
causing \fBpic\fR to attempt to scale it to the given dimensions in
-inches. In no case, however, will the X and Y\~dimensions of the
+inches. In no case, however, the X and Y\~dimensions of the
picture exceed the values of the style variables \fBmaxpswid\fP and
\fBmaxpsheight\fP (which default to the normal 8.5\^i by 11\^i page size).
.PP
@@ -2546,7 +2546,7 @@
.R
.DE
.PP
-will fail. You have to use the braces on the same line as the keywords:
+fails. You have to use the braces on the same line as the keywords:
.DS
.CW
if {
@@ -2925,7 +2925,7 @@
.R
.DE
.LP
-The arguments (if any) will be substituted for tokens $1, $2 .\|.\|.\& $n
+The arguments (if any) are substituted for tokens $1, $2 .\|.\|.\& $n
appearing in the replacement text. To undefine a macro, say \fBundef\fP
\fIname\fR, specifying the name to be undefined.
.\"%%POSTLUDE%%
Index: groff/doc/webpage.ms
diff -u groff/doc/webpage.ms:1.22 groff/doc/webpage.ms:1.23
--- groff/doc/webpage.ms:1.22 Tue Jan 3 23:57:03 2006
+++ groff/doc/webpage.ms Sat Jan 21 14:14:09 2006
@@ -122,7 +122,7 @@
.MTO address@hidden:axis.se "J\[:o]rgen H\[:a]gg" .
See the file INSTALL for installation instructions.
-You will require a C++ compiler.
+You require a C++ compiler.
The file NEWS describes recent user-visible changes to groff.
@@ -156,7 +156,7 @@
When asked for a password during the `login' call, simply press Enter.
-This will create a subdirectory, ~/cvswork/groff, with a `checked out'
+This creates a subdirectory, ~/cvswork/groff, with a `checked out'
copy of the CVS repository.
An update of this working copy may be
achieved, at any later time by invoking the commands
@@ -221,9 +221,9 @@
CVS sources (either a checked out working copy, or a daily snapshot).
They are not required for building from a stable release tarball.
Also note that the version numbers stated are the minimum supported.
-No version of texinfo < 4.8 will work, and the original release of bison
+No version of texinfo < 4.8 work, and the original release of bison
1.875 is known not to work; you \fImay\fP find that bison releases < 1.875
-will work, but in case of difficulty, please update to a later version
+do work, but in case of difficulty, please update to a later version
\fIbefore\fP posting a bug report.
For \fIall\fP sources, you need ghostscript for creation of either PDF or
@@ -240,7 +240,7 @@
At the very least, read the BUG-REPORT form and make sure that you supply
all the information that it asks for.
Even if you are not sure that something is a bug, report it using
-BUG-REPORT: this will enable us to determine whether it really is a bug or
+BUG-REPORT: this enables us to determine whether it really is a bug or
not.
.SH
@@ -482,15 +482,15 @@
heading, defined by `NH' or `SH', before any automatic page break.
.IP GROWPS
-Sets the first level of heading (set with `NH') which will keep the
+Sets the first level of heading (set with `NH') which keeps the
same point size as body text.
.IP PSINCR
Sets the point size increment for each level of heading (set with
`NH'), below the threshold level set by `GROWPS'; e.g., if
\en[PS]\~=\~10, \en[GROWPS]\~=\~3 and \en[PSINCR]\~=\~2.0p, then `.NH\~1'
-will produce 14pt headings, `.NH\~2' will produce 12pt, and all other levels
-will remain at 10pt (because \en[PS]\~=\~10).
+produces 14pt headings, `.NH\~2' produces 12pt, and all other levels
+remain at 10pt (because \en[PS]\~=\~10).
.LI
The `SH' macro now accepts a numeric argument, to make heading size
@@ -559,7 +559,7 @@
and \eX'ps:\~import' escapes.
.LI
-If option `\-V' is used more than once, the commands will be both printed
+If option `\-V' is used more than once, the commands are both printed
on standard error and run.
.ULE
.
@@ -802,7 +802,7 @@
.ft R
.in
-will change the mapping while a composite glyph name is constructed.
+changes the mapping while a composite glyph name is constructed.
To make \e[A\~ho] yield the expected result,
.in 2m
@@ -1377,7 +1377,7 @@
.LI
`trin' (translate input) is a new request which is similar to `tr' with
-the exception that the `asciify' request will use the character code (if
+the exception that the `asciify' request uses the character code (if
any) before the character translation.
Example:
@@ -1557,12 +1557,12 @@
`\-R', and `\-C'.
.LI
-New macro `PIMG' for inclusion of a PNG image (it will automatically
-convert it into an EPS file if not \-Thtml is used).
+New macro `PIMG' for inclusion of a PNG image (it automatically
+converts it into an EPS file if not \-Thtml is used).
.LI
New macro `MPIMG' for putting a PNG image into the left or right margin
-(it will automatically convert it into an EPS file if not \-Thtml is used).
+(it automatically converts it into an EPS file if not \-Thtml is used).
.LI
New macros `HnS', `HnE' to start and end a header line block.
@@ -1813,7 +1813,7 @@
A new manual page `ditroff.7' is available.
.LI
-The groff texinfo manual will now be installed, together with a bunch
+The groff texinfo manual is now installed, together with a bunch
of examples.
.LI
Index: groff/man/groff.man
diff -u groff/man/groff.man:1.74 groff/man/groff.man:1.75
--- groff/man/groff.man:1.74 Sat Feb 19 04:23:40 2005
+++ groff/man/groff.man Sat Jan 21 14:14:09 2006
@@ -414,7 +414,7 @@
.
.P
.B Text lines
-represent the parts that will be printed.
+represent the parts that is printed.
They can be modified by escape sequences, which are recognized by a
leading backslash
.squoted_char \[rs] .
@@ -653,7 +653,7 @@
.IP ""
As a second task, it is the most commonly used argument separator in
some functional escape sequences (but any pair of characters not part
-of the argument will work).
+of the argument do work).
.
In all other positions, it denotes the single quote or apostrophe
character.
@@ -671,7 +671,7 @@
.request ds
and
.request as
-requests, a leading double quote in the argument will be stripped off,
+requests, a leading double quote in the argument is stripped off,
making everything else afterwards the string to be defined (enabling
leading whitespace).
.
@@ -1107,13 +1107,13 @@
.I \[+-]N
starts with a
.squoted_char +
-sign the resulting value of the expression will be added to an already
+sign the resulting value of the expression is added to an already
existing value inherent to the related request, e.g.\& adding to a number
register.
.
If the expression starts with a
.squoted_char -
-the value of the expression will be subtracted from the request value.
+the value of the expression is subtracted from the request value.
.
.P
Without a sign,
@@ -1516,7 +1516,7 @@
.REQ .em macro
The
.I macro
-will be run after the end of input.
+is run after the end of input.
.
.REQ .eo
Turn off escape character mechanism.
@@ -1612,7 +1612,7 @@
.IR s1 ,
.IR s2 ,
.I .\|.\|.\&
-will be special.
+are special.
.
.REQ .ft
Return to previous font.
@@ -1921,7 +1921,7 @@
.I string
starts with
.character \[dq]
-(which will be stripped off).
+(which is stripped off).
.
.REQ .pc
Reset page number character to\~\c
@@ -2105,7 +2105,7 @@
Fonts
.IR s1 ,
.IR s2 ,
-etc.\& are special and will be searched for characters not in the
+etc.\& are special and are searched for characters not in the
current font.
.
.REQ .spreadwarn
@@ -2218,7 +2218,7 @@
.I anything
starts with
.character \[dq]
-(which will be stripped off).
+(which is stripped off).
.
.REQ .tmc anything
Similar to
@@ -2244,7 +2244,7 @@
.request tr
request except that the
.B asciify
-request will use the character code (if any) before the character
+request uses the character code (if any) before the character
translation.
.
.REQ .trnt abcd.\|.\|.\&
@@ -2528,7 +2528,7 @@
Transparent line indicator.
.
.ESC? anything
-In a diversion, this will transparently embed
+In a diversion, this transparently embeds
.I anything
in the diversion.
.I anything
@@ -2566,12 +2566,12 @@
.
.ESC /
Increases the width of the preceding character so that the spacing
-between that character and the following character will be correct if
+between that character and the following character is correct if
the following character is a roman character.
.
.ESC ,
Modifies the spacing of the following character so that the spacing
-between that character and the preceding character will correct if the
+between that character and the preceding character is correct if the
preceding character is a roman character.
.
.ESC ~
@@ -3488,7 +3488,7 @@
.SH AUTHORS
.\" --------------------------------------------------------------------
.
-Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005
+Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006
Free Software Foundation, Inc.
.
.P
Index: groff/man/groff_char.man
diff -u groff/man/groff_char.man:1.22 groff/man/groff_char.man:1.23
--- groff/man/groff_char.man:1.22 Mon Dec 6 01:08:10 2004
+++ groff/man/groff_char.man Sat Jan 21 14:14:09 2006
@@ -17,9 +17,10 @@
This file is part of groff (GNU roff).
File position: <groff_src_top>/man/groff_char.man
-Last update: 05 Dec 2004
+Last update: 21 Jan 2006
-Copyright (C) 1989-2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
+Copyright (C) 1989-2000, 2001, 2002, 2003, 2004, 2006
+ Free Software Foundation, Inc.
written by Werner Lemberg <address@hidden>
with additions by Bernd Warken <address@hidden>
@@ -359,7 +360,7 @@
.B groff
glyph names and the default input mapping, \%latin-1.
.
-The glyphs in this document will look different depending
+The glyphs in this document look different depending
on which output device was chosen (with option
.B \-T
for the
@@ -367,7 +368,7 @@
program or the roff formatter).
.
Glyphs not available for the device that
-is being used to print or view this manual page will be marked with
+is being used to print or view this manual page are marked with
.ie \n(.g `(N/A)'; the device currently used is `\*(.T'.
.el `(N/A)'.
.
@@ -404,7 +405,7 @@
.IR \%Latin-2 ;
since
.B groff
-will use Unicode in the next major version, no additional encodings
+uses Unicode in the next major version, no additional encodings
are provided.
.
.
@@ -1279,7 +1280,7 @@
Unfortunately, most font vendors didn't update their fonts to
this (incompatible) change in Unicode.
.
-At the time of this writing (February 2003), it is not clear yet whether
+At the time of this writing (January 2006), it is not clear yet whether
the Adobe Glyph Names `phi' and `phi1' also change its meaning if used for
mathematics, thus compatibility problems are likely to happen \(en being
conservative, groff currently assumes that `phi' in a PostScript symbol
@@ -1358,7 +1359,7 @@
.\" --------------------------------------------------------------------
.
Copyright \(co 1989-2000, 2001, 2002, 2003,
-2004 Free Software Foundation, Inc.
+2004, 2006 Free Software Foundation, Inc.
.
.P
This document is distributed under the terms of the FDL (GNU Free
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Groff-commit] groff ./INSTALL ./NEWS ./PROBLEMS ./README doc/...,
Werner LEMBERG <=