wp2x.1l

harvest是一个下载html网页得机器人

End centering
.sp 1
.TP
Align
Begin alignment
.TP
align
End alignment
.TP
AlignChar
Set alignment character
.TP
FlushRight
Begin flush right
.TP
flushright
End flush right
.sp 1
.TP
Math
Begin math mode
.TP
math
End math mode
.TP
MathCalc
Begin math calc mode
.TP
MathCalcColumn
Math calc column
.sp 1
.TP
SubTotal
Do subtotal
.TP
IsSubTotal
Subtotal entry
.TP
Total
Do total
.TP
IsTotal
Total entry
.TP
GrandTotal
Do grand total
.sp 1
.TP
Col
Begin column mode
.TP
col
End column mode
.sp 1
.TP
Fn
Expanded at the beginning of a footnote.
.TP
fn
Expanded at the end of a footnote.
.TP
En
Expanded at the beginning of an endnote.
.TP
en
Expanded at the end of an endnote.
.TP
SetFn#
Set the number for the next footnote to %1.
.TP
FNote#
Footnote number.
.TP
ENote#
Endnote number.
.TP
Figure#
Figure number.
.TP
TableMarker
Insert table of contents here
.sp 1
.TP
Hyph
Enable hyphenation.
.TP
hyph
Disable hyphenation.
.TP
Just
Enable justification.
.TP
just
Disable justification.
.TP
Wid
Enable widow/orphan protection.
.TP
wid
Disable widow/orphan protection.
.TP
HZone
The hyphenation zone.  %1 and %2 are the two magical values
that WordPerfect uses to control hyphenation.
.TP
DAlign
Set the decimal alignment character to that whose ASCII value is %1.
(`%c' is useful here.)
.sp 1
.TP
Header
Begin header text
.TP
header
End header text
.TP
Footer
Begin footer text
.TP
footer
End footer text
.sp 1
.TP
Supp
Suppress page number/header/footer information for one page.
%1 argument is a bit field which describes what sort of
suppression is desired.  Here's what the bits mean:
.nf
          1 = all
          2 = page number
          4 = page numbers moved to bottom
          8 = all headers
         16 = header a
         32 = header b
         64 = footer a
        128 = footer b
.fi
.TP
CtrPg
Center page vertically
.sp 1
.TP
SetFont
Change pitch or font.  %1 is the desired pitch.  (Negative
means proportionally-spaced.)  %2 is the font number.
.TP
SetBin
Select paper bin to %1 = 0, 1, ...
.sp 1
.TP
PN0
No page numbering.
.TP
PN1
Page number in top left.
.TP
PN2
Page number in top center.
.TP
PN3
Page number in top right.
.TP
PN4
Page number on top outside corners (even/odd).
.TP
PN5
Page number in lower left.
.TP
PN6
Page number in bottom center.
.TP
PN7
Page number in lower right.
.TP
PN8
Page number on bottom outside corners (even/odd).
.PD
.PP
If no expansion is supplied for an identifier, then nothing is emitted to
.IR stdout ,
but a warning message is sent to
.IR stderr .
This warning message will appear at most once per identifier, and it
can be suppressed completely by the
.B \-s
option.
.PP
The special identifier
.I typeout
causes its replacement text to be
displayed on the screen every time the configuration file is read.
This is useful for identification messages, or reminders to the user.
.PP
A special identifier is any character enclosed in single quotation
marks, which represent themselves.  For example,
.nf

   '\(*a'="{\e\ealpha}"

.fi
causes the string "{\ealpha}" to be emitted when an \(*a is encountered.
This could also have been written as
.nf

   '\exE0'="{\e\ealpha}"

.fi
if the character \(*a has ASCII value 0xE0.
(Which is true for the IBM PC encoding.)
.PP
If no definition exists for a particular special character,
it is transmitted undisturbed.  If a special character is encountered
from the upper half of the ASCII character set, and if it has no
definition, then a warning message is also emitted.
(Which can be suppressed with the
.B \-s
option.)
.PP
Lines beginning with the # character are comments.
.SH NOTES

This is based on an original WP 4.2 to anything translator. The file
format has changed a lot between 4.2 and 5.0. This translator no
longer reads WP 4.2 files, although it could be extended to do so. 

The 5.0+ format starts with a standard header file. There is a four
byte magic number at the head of the file, followed by various product
and version information. All WordPerfect Corporation utilities use
this standard header. See the WPproducts array in 
.I wp2x.c

Once the contents of the file have been located, there are three kinds
of codes: simple one byte controls (WP 4.2 had only these kinds),
fixed length controls, and variable length controls. There are a large
number of undefined types defined for future use. If 
.B wp2x
detects something it doesn't understand, it can extract the length and
skip that code. There are a number of defined codes that are
unimplemented. Please see the code, specifically 
.I tokens.c
where much of the input processing is done.

.SH FILES
The sample configuration files in
.I /usr/local/lib/wp2x
give you some sort of idea what a `production quality'
configuration file might look like.
They are not intended to be used as-is, but rather are meant to be
modified to suit your particular needs.
.SH "SEE ALSO"
.IR tex (1),
.IR latex (1),
.IR nroff (1),
.IR troff (1),
.IR WordPerfect Developer's Toolkit
.IR getopt(3).
.SH DIAGNOSTICS
.TP
Ignoring byte [XX]
Indicates that an unimplemented single byte code was ignored.
.TP
Ignoring fixed [XX]
Indicates that an unimplemented fixed length code was ignored.
.TP
Ignoring variable [XX] sub [XX] length
Indicates that an unimplemented variable length code was ignored, and
gives its length.
.TP
Warning: Expected XX but received XX at pos: YYYY
something is wrong in the input file at byte YYYY.
.TP
Warning: No expansion for XX (C)
A WP code for which no expansion was defined in the config file was
encountered.
.TP
Internal error: Invalid escape C
An error occured while processing an expansion escape (%x
substitution). Probably it was not a recognized escape, check the
config file.
.TP
Fixed Length block [XX] incorrectly terminated by [YY] as pos Z
Something is wrong with the input file, a fixed length block was
screwed up.
.TP
Reserved code [XX] seen
Something that WPC defined as reserved was seen. Check with WPC for
new meaning.
.TP
Not a recognized file type. The file did not start with the right WPC
magic number. Maybe this is a 4.2 file, or not a WordPerfect file at all?
.TP
Error: Cannot open X (reason)
The file X could not be opened, for the indicated reason.
.TP
Error: Expecting a hex digit
Inside a string, you typed the characters `\ex', but the next character
was not a valid hex digit.
.TP
Error: string pool overflow
The configuration file contained too many strings.  Increase the value
of POOL_SIZE and recompile.
.TP
Error: Unknown identifier X
The word X was encountered in the configuration file when
.I wp2x
expected a token identifier like `HRt'.
Most likely, you either misspelled it, or you got your quotation marks
out of sync.
.TP
Error: Identifier not followed by = sign
After an identifier must come an equals-sign.
.TP
Error: Quotation mark expected
After the equals-sign must come a quotation mark.
.TP
Error: X: `%\en' not at start of expansion
The expansion for the identifier X contained the indicated sequence
of characters somewhere other than the beginning of the string.
The `%\en' interpolation code is meaningful only at the beginning
of a string.
.TP
Error: X: invalid escape `%x'
The expansion for the identifier X contained an invalid escape.
Either you used `%1', `%2' or `%c' when the identifier X does not
supply that parameter, or you meant for a genuine percent sign
to be output, in which case you should put `%%' in the expansion.
.TP
Error: Invalid character identifier
Character identifiers can only be one character long (after backslash
interpretation).
.TP
Warning: Expected XX but received YY.
The program expected the next byte from the WP file to be XX, but
the byte YY was encountered instead.  This means either that your WP
file is damaged, or that the program is seriously confused.  (Or both.)
The program
will pretend that the byte in the file was indeed XX, which may
lead to synchronization errors later on.
.TP
Warning: No expansion for X
The WP file contained the token X, but the configuration file did not
contain any expansion text for it.  A null expansion was assumed.
.TP
Warning: No expansion for XX (c)
The WP file contained the character c (hex code XX),
but the configuration file
did not contain any expansion text for it.
The character was emitted unaltered.
Beware that this may give your text formatter indigestion if it does
not handle eight-bit characters.
.TP
Warning: X code not supported
The file being converted uses a code which
.I wp2x
does not know how to convert.
A comment is placed in the output file in its place.
If you ever encounter a `WPCorp reserved' or a `WPCorp undefined' code,
the author would appreciate hearing from you.
.TP
Internal error:  Invalid escape, %x
While processing text,
.I wp2x
noticed that you used an invalid escape.
Nothing is emitted as the escape text.
(The internal-ness is that this error is supposed to be caught at
the time the configuration file is read.)
.SH BUGS
Naive configuration files will fail if your WP file
doesn't nest its tags properly.  A typical case is
.nf

     [Center][B]Hello[center]
     [Center]There[b][center]
.fi
to produce a centered boldface `Hello'.  If you use the naive encoding
of
.nf

     Center="\e\ecenterline{"
     center="}\en"
     Bold="{\e\ebf "
     bold="}"

.fi
then this will expand to
.nf

     \ecenterline{{\ebf Hello}
     \ecenterline{There}}

.fi
WordPerfect has no clean concept of grouping; it lets you change fonts
at any time and let those changes propagate outside the current
environment.
(With the exception of headers, footers, footnotes, and endnotes.)
.PP
Now sure, you could write complicated configuration strings to try
to handle this `properly', but it'd probably not be worth the trouble.
After all, the purpose is not to perform a perfect conversion, but
rather to produce a
.I readable
conversion, which can then be massaged by hand to produce a perfect
manuscript.
.PP
Another potential problem is combined attributes, like boldface underline.
Under a naive configuration,
.nf

     [B]Boldface [U]Underlined boldface[b] Underlined[u] normal.

.fi
comes out as
.nf

 {\ebf Boldface {\eit Underlined boldface} Underlined\e/} normal.

.fi
which is wrong for two reasons.  One is the nesting problem discussed
above.  The other is that
.Tx
font attributes do not combine.
.PP
Similar problems exist for other document preparation systems.
So be careful.
.SH AUTHOR
Original author: Raymond Chen <[e-mail]>

Current maintainer: Michael Richardson <[e-mail]>