@Pageheading[odd, 
Left "Perfect Format Test Document (odd)", Right "(right) Page @Value(Page)",
Line "(C) 1982 Computer Services Corporation of America, INC."]@pagefooting[
left "by Barry A. Dobyns, Chief Programmer", Right "@version",
line "@title(chapter)"]
@Pageheading[even,
right "Perfect Format Test Document (even)", left "(left) Page @Value(Page)", 
Line "(C) 1982 Computer Services Corporation of America, INC."]
@pagefooting[ 
Right "@version", left "@filename", center "@devicename"
line "by Barry A. Dobyns, Chief Programmer
@title(chapter)"]
@MajorHeading(Preface)
@heading(The Perfect Format  Test Manuscript)@index(Instructions)
@prefacesection(Purpose of this Manuscript)
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)
This Manuscript is meant to exercise most of the features of Perfect
Format to aid you in testing Perfect Formats that you develop.

@prefacesection(Creation Notice)Perfect Format  Test Manuscript by
Barry A. Dobyns @begin(itemize)Created for Amethyst User's Group
August 13, 1981. [BAD]

Modified to remove some bugs in the formatting commands, generally
cleaned up the contents. Added some extra text so that Perfect Format
problems I am aware of will be pointed up. September 5, 1981. [BAD]

Much of the text was rearranged to more closely match the order of
certain sections of the new (1.3) Scribble manual. Several new
commands were added to the text. September 6, 1981. [BAD]

Modified to work correctly as a test vehicle for Perfect Format By
CSCA. More new commands added to the text. January 12, 1982. [BAD]
@end(itemize)

This test manuscript formatted by @message(Who are you <C-Z>)@Include(CON:)
on @message(What date is today?)@include(con:) at
@message(What time is it <C-Z>)@Include(CON:).

With this version of Perfect Format: @version

@message(Do you have any special comments to make? <C-Z>)@include(CON:)
@prefacesection(Usage)Once you get Perfect Format  configured to
work with your printer(s) run this manuscript thru Perfect Format
(once for each printer type you have defined). Undoubtedly there will
be botches. Hopefully all of the botches will be due to improper
specifications in the CONFIG.DAT file. Once you get things working
right with this file, put a copy of each of the CORRECT outputs you
have created in a (safe) and handy place for future reference. This
will constitute the standard of comparison for the new
Perfect Formats you will produce and submit to AUG. Hopefully all
future submissions for Perfect Format extensions will be able to
format this manuscript as flawlessly (?) as the factory version(s).

As you produce new environments, features and facilities, put tests of
them in this manuscript and try running it thru your new system. This
will give you a resonably effective test to see if your new features
work, and if they inadvertently gronk any other ones.
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)

This file is long for a reason: short files are not likely to exercise
Perfect Format too hard. Weird things can often happen on the 25th
page (only if it's the second page of the index) that you would never
catch until you ran that all-important document off (and distributed
100 copies of it, before catching it). If you exercise all of the new
and old features at once (or at least most of them) you are more
likely to spot those bizarre 'interaction type' bugs while you are
still programming, and before you start trying to use the system.

This manuscript can also help you set up the CONFIG.DAT
file properly for your printers. I didn't get the paper size for my
printer just right until after I had been using Perfect Format for
over four months.
@Chapter(Environments)
@section(Address Environments)
Here is an example of an @@Address Environment
@address(The Amethyst Users Group
Post Office Box 8173
Austin, Texas 78712-8173)@index(Address)@index(Four Digit Zip Code)
@section(Center Environments)
Here is an example of @@Center: @center(All of this line should be centered
as this one should be also,
and this one too.)@index(Center)
@section(Closing Environments)@index(Closing)
@closing{This is an @@Closing environment.
it should appear identical
in format to @@Address}
@Section(Comment Environments)@Index(Comment)
This sentence is followed by a comment.@comment(this had better not
show up) This sentence follows the comment.
@section(Description Environments)@index(Description)
The @@Description environment :
@description{
Description@\You may have trouble formatting this Manuscript with your
Perfect Format, since I use a 64K system, and I have made extensive use of
the features of Perfect Format that require lots of memory. It is possible
that you will not be able to use this manuscript if you have 56K, and
almost certain if you only have 48K. In Versions of Perfect Format 1.3 (and
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)
later, I presume) you can specify how much space to reserve for end
stuff. This feature may well save you. This manuscript uses about 4400
bytes for the largest page and 2900 bytes for the end space when
formatted for a vanilla device.

Outdented@\Indented part of the way@\Maybe indented some more, maybe not.
@\In the official Perfect Formats s this sentence is NOT indented
even further than the previous sentence.}
@section(Display Environments)@Index(Display)
Here we have an example of @@Display:
@display(
this is a test line.
this is another.)
which concludes the testing.
@section(Enumerate Environments)@index(Enumerate) Note that most "failures" for
Personal Computers @index(Personal Computers) are either shipping
damage problems (connectors shaking loose), or operator errors. Common
operator malfunctions are
@enumerate{RF Modulator@enumerate[expecting the $39 microverter to
also modulate the sound so your TV set makes noise (it doesn't, and it
won't)@index(RF Modulator)

having dead batteries in the RF modulator (since it is easy to forget
to turn off, it is easy to kill the batteries in it).]

using the sound connector instead of the D/A connector (or vice versa,
or confusing any of the RCA phono connectors)

not having the shift lock key locked down at all times@index(Shifting)

using a trashed diskette (a diskette will nearly always get trashed if
the system is powered down with the disk in the drive)@index(Trashing Disks)

not turning one of the units (Disk, CPU, Monitor) on}
@section(Example Environments)@Index(Example)
Here we have an example of @@Example:
@example(
this is a test line.
this is another.)
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)
which concludes the testing.
@section(FlushLeft Environments)@Index(FlushLeft)
Here we have an example of @@FlushLeft:
@FlushLeft(
this is a test line.
this is another.)
which concludes the testing.
@section(FlushRight Environments)@Index(FlushRight)
Here we have an example of @@FlushRight:
@FlushRight(
this is a test line.
this is another.)
which concludes the testing.
@section(Indent Environments)@index(Indent)
This section exercises indent environments, and nested indent
environments. Indent is new for (TM) Perfect Format.
@begin(indent)The perfect writer system has been designed and created with one
primary aim in mind: to make it easier for writers to concentrate on
the primary task at hand, that of writing, rather than on the details
of the actual arrangement of the material on a printed page.
@begin(indent)We feel that thru the use of the Perfect Format system,
writers of any sort of text can become more productive, simply because
they only have to think about @b(what) they are writing, not about
@b(how) they are getting it written. @end(indent)
We are certain that
if you take the time to learn about Perfect Format, you will
agree. Perfect Format is a tool. Tools (to us anyway) are things that help
people do something in a way that is preferable to doing it without
the tool. @end(indent)
@section(Format Environments)@index(Format)
This is an attempt to exercise the @@Format environment. None of the
telephone numbers are real. Some of the people tell me that they
aren't very real either.
@begin(format)
	Allison's Work		454-2086
	Jerry			859-2921
	Linda			555-5691
	Time & Weather		545-1411
	Andrew's Lab		541-4403
	Andrew's Home		544-5012
	Physics Laboratory	541-5659
	Physics Office		541-8386
	UNIX 			545-5115
	SPRINT			545-4443
@end(format)
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)
@section(Itemize Environments)@index(Itemize)
These are some of the the things you
need for Tomato-Zucchini Quiche@index(Dinner)
@itemize{Spices@itemize[Eye of Bat@index(Extreme Illness)

Leg of brown tree toad@index(Leg of brown tree toad)

Curry Powder@index(Curry Powder)

Rock Salt@index(Rock Salt)

Roach poison concentrate@index(Roach poison concentrate)]

Pie Shell@index(Pie Shell)@itemize[Flour@index(Flour)

Lard@index(Lard)

Water@index(Water)

Naragansett Beer@index(Naragansett Beer)]

Filling@index(filling)@itemize[Tomato@index(Tomato)

Ragu@index(Ragu)

Baby Gouda Cheese@index(Baby Gouda Cheese)

Fresh Zucchini@index(Fresh Zucchini)

Vienna Sausages@index(Vienna Sausages)]}
@Section(Level Environments)
These should be nested to several levels of nesting.@index(Level)
@begin(level)
This line is nested inside @@Level environments.
@begin(level)
This line is nested inside @@Level environments.
@begin(level)
This line is nested inside @@Level environments.
@begin(level)
This line is nested inside @@Level environments.
@end(level)

This line is nested inside @@Level environments.
@begin(level)
This line is nested inside @@Level environments.
@end(level)

This line is nested inside @@Level environments.
@begin(level)
This line is nested inside @@Level environments.
@end(level)

This line is nested inside @@Level environments.
@end(level)

This line is nested inside @@Level environments.
@begin(level)
This line is nested inside @@Level environments.
@begin(level)
This line is nested inside @@Level environments.
@begin(level)
This line is nested inside @@Level environments.
@end(level)

This line is nested inside @@Level environments.
@end(level)

This line is nested inside @@Level environments.
@end(level)

This line is nested inside @@Level environments.
@end(level)

This line is nested inside @@Level environments.
@end(level)

@section(Quotation Environments)@index(Quotation)
This is a quotation from TV Guide:@Index(TV Guide)
@quotation{@B[Special:] The Polish experiment in democracy and its
impact on the Soviet Union@index(Soviet Union) are analyzed in "Why
Poland Makes Moscow Shudder." According to executive producer Bob
Rogers@index(Bob Rogers), the report... ... ...@foot(TV Guide Vol.29
No.33/August 15, 1981 Page A-18)@string(second=page)} which should be
of absolutely no interest to you whatsoever. Ahem. However it
demonstrates this feature effectively.
@section(Undent Environments)@index(Undent)
@begin(undent) Many of us at BRL @index(BRL) have had DEC-10
@index(DEC-10) @index(DEC-20) and -20 experience, and consequently,
many of our fond memories are filled with experience with
@index(EMACS) EMACS, a screen oriented code and text editing system
originated at MIT @index(MIT). As a result of our fondness for EMACS,
we formed a close relationship to Mark of the Unicorn @index(Mark of the Unicorn),
a company in Arlington @index(Arlington), Massachusetts
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)
@index(Massachusetts), who has developed an extensible EMACS
look-alike written entirely in @index(C) C, called Amethyst
@index(Amethyst). My and my associates at BRL's enthusiam for Amethyst
is great, and one of the first tasks we would doubtless undertake is
the porting @index(Porting) of Amethyst to MUMBLE-DOS @index(MUMBLE-DOS).

Mark of the Unicorn has indicated to me that they have successfully
ported Amethyst to @index(Onyx), Xenix @index(Xenix) @index(Unix descendants)
(Unix descendants), a @index(VAX) VAX, and @index(RSX-11) RSX-11.
They claim that
they have the porting process down to where they can come up on a new
machine in a week or less. Indeed, in light of this degree of
portability, it would be silly of us to not try to get it onto any
system we had.
@end(undent)
@Section(Verbatim Environments)
@verbatim{This is a test of the @@verbatim directive:@index(Verbatim)

		this line started with two tabs.@index(Two Tabs)
                this line started with sixteen spaces.@index(Sixteen Spaces)
 		this line started with one space and two tabs.

all of the above lines should be indented the same amount if your
tabstops @index(tabstops) are set at every eight spaces (heh, heh)}
@Section(Verse Environments)@index(Verse)
And this is a piece of poetry:
@verse{@center[Gold in the Mountain]@index[Gold in the Mountain]

Gold in the mountain,
And gold in the glen,
And greed in the heart,
Heaven having no part,
And unsatisfied men.@foot[By Herman Melville @index(Herman Melville)(1819-1891)
@string(third = page)]}
@chapter(Inline Environments)@index(Inline Environments)
@section(Boldface, Underscore, Italics)@index(Boldface)@index(Underscore)@index(Italics)
@b(This is a boldface text with @@B)@foot(Boldface)
@string(first=page)
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)

@i(This text is in italics using @@I)@foot(Italics)

@p(This text is in boldface italics using @@P)@index(Boldface Italics)

@r(This Text is in Roman using @@R)@index(Roman)

@p{@r(This Text is in Roman using @@R inside an @@P)}

@t(This Text is also in Roman using @@T)

@p{@t(This Text is also in Roman using @@T inside an @@P)}

@u(This text is underscored using @@u)

@ux(This text is underscored with @@ux)

@un(this text is underscored with @@un)

@f1(This is done in Font 1. This is done in Font 1. This is done in Font 1.)
@section(Superscripts and Subscripts)@index(Superscripts)@index(Subscripts)
@index(Boldface Superscripted)@index(Boldface Subscripted)@index(Munged)
Sentence 1:This sentence has a @+(Superscripted 1) word in it.
Sentence 2:This sentence has a @+(@B<Boldface 2 Superscripted>) word in it.
Sentence 3:This sentence has a @-(Subscripted 3) word in it.
Sentence 4:This sentence has a @-(@b<Boldface 4 Subscripted>) word in it.
Sentence 5:And @-(@b<Boldface 5 Subscripted>) @+(@B<Boldface 5 Superscripted>) both.

Line 6: This line has a @+(Superscripted 6) word in it.

Line 7:This line has a @+(@B<Boldface 7 Superscripted>) word in it.

Line 8:This line has a @-(Subscripted 8) word in it.

Line 9:This line has a @-(@b<Boldface 9 Subscripted>) word in it.

Line 10:And @-(@b<Boldface 10 Subscripted>) @+(@B<Boldface 10 Superscripted>) both.

I have noted some bizarre problems that may occur if a line has
subscripted in it and the line below has superscripted. In some cases,
it may be possible for Perfect Format to overprint the things. Messy.
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)
Observe that the @@+ and @@- environments above include text which
indicates which line they belong to, so that it easier to determine.
@chapter(Commands for Reports)@index(Commands for Reports)
@section(General Confusion) Commands that have been used already used
in this document follow:@index(Confused?)
@subsection(Footnotes)@index(Footnotes) I have been using the
@@Foot @Foot{On pages @Value(first), @Value(second), @Value(third) and
@Value(page)} directive in this manuscript already.
@subsection(Chapter, Section, Subsection and Paragraph)
@index(Numbered Headings)@index(Chapter)@index(Section)@index(Subsection)
@index(Paragraph)
@paragraph(Usage)
I have also been using these throughout.
@Paragraph(Indications)
This section contains numbered paragraphs, and this paragraph should
have a number of the form N.N.N.N (Four numbers separated by periods).
@section(UnNumbered Environments)@Index(UnNumbered)
Following is an example of an @@UnNumbered environment.
@UnNumbered{This entire sentence appears inside of an @@UnNumbered environment and should appear on a new page.}
@section(Unnumbered Headings)@Index(Unnumbered Headings)
Here is a Major Heading@majorheading(MajorHeading)@index(MajorHeading)
Here is a Heading@Heading(Heading)@index(Heading)
Here is a SubHeading@SubHeading(SubHeading)@index(SubHeading)
@section(Other Stuff)
Indexing, Appendicies, Prefaces, Pageheading and Pagefooting are all used
in this document. They should appear in the proper locations.
@subsection(PageFooting and PageHeading)
@index(PageFooting and PageHeading)
@paragraph(PageHeading)@index(PageHeading Specifics)
The pageheading should be different on odd pages from the heading on
even pages. Specifically, the left and right text should change places
each page. Also the parity of the page  (odd | even) should appear
someplace in the heading.
@paragraph(PageFooting)@index(PageFooting Specifics)
The center field
should contain the chapter title. The left and right fields should say
left and right, respectively.
@chapter(Miscellaneous Commands and General Directives)
@section(Style)@index(Style)
@index(A-1)@index(D-1)@index(H-1)@index(L-1)@index(P-1)@index(T-1)@index(Z-1)
I have not used the @@Style directive in this test manuscript.
@section(Device)@index(Device)
I have not used the @@Device directive in this test manuscript.
@section(Blankspace)@index(Blankspace)
This is an example of the use of the @@Blankspace directive@Blankspace(1 inches)and there should be one inch between this and the previous line.
@section(Set and Ref)@index(Set and Ref)@index(Ref)
I have not used the @@Set directive in this test manuscript.
This occurs on page @ref(page) in section @ref(section) according to @@Ref.
@section(String and Value)@index(String and Value)@index(Value)
I used the @@String and @@Value directives to determine where the footnotes
occured so that references to them could be printed in the section on
footnotes. This Directive was also used in the PageHeading.
@section(Title)@index(Title)
The title of the chapter this section appears in is @title(chapter).
This directive was also used in the PageFooting.
@section(Case)@index(Case)
I have not used the @@Case directive in this test manuscript.
@index(The End)
@pagefooting(right "Page @page of 4")
@comment( persona can be either "individual" or "corporate")
@string(persona "individual")
@string(victim "Queen Elizabeth II")
@string(psi "Perfect Software, Inc.")
@string(pw "Perfect Writer") @string(pf "Perfect Format")
@appendix(General)

This agreement is entered into by @victim at the request of @psi and is
binding both during the association of @victim with @psi and therefter
as applicable under Federal, State and local laws. @victim agrees herein
to take resonable precautions to protect such confidental,
proprietary, trade secret or liscenced materials and information
provided to @victim duing the term of their association with
@psi from disclosure, accidental or intentional.
@appendix(Scope)

@case( persona,

corporate, "This document shall be considered binding on all
employees of @victim during the entire term of @victim's association
with @psi"

individual, "This document shall be considered binding on
@victim during the entire term of @victim's association with @psi")

This document pertains to all classes of software and materials
described herein which may be provided to @victim by @psi during
the course of their association with @psi
@appendixsection(Materials Owned by @psi in Whole or Part)

@pw, @pf and all their constituent parts, subparts, modules,
submodules and associated configuration and utility programs and
subprograms, and any source code, object code or other
representation for same,  whether for end user or developement
use, which are wholly owned by @psi All other software wholly
owned by @psi or to which @psi has excusive liscence, or to which
@psi holds  liscence to distribute or redistribute.
@appendixsection(Materials Not Owned by @psi)

Those programs, subprograms and modules or materials liscenced or sold to
@psi for use by @psi,  which are owned by other parties, and to
which @psi only holds non-exclusive liscence or rights to use,
modify or otherwise utilize same. This shall include, but not be
limited to such operating systems, compilers, interpreters,
utilities and other software installed machines owned or used by
@psi
@appendixsection(Agreements Entered Into by @psi)

This document also binds @victim to the provisons of such
liscences and agreements entered into by @psi for materials
subsequently provided to @victim for use during their  association with @psi.
This shall include agreements by @psi as both liscencee and liscencor.
@victim shall take such precautions as necessary to insure
@psi compliance with the provisions of such liscences or agreements.
@appendixsection(Medium of Representation)

This agreement shall pertain to all covered materials, regardless of
medium of representation. This shall include but not be limited
to all electronic, written, mechanical, audio, visual or machine readable
representations temporal or permanent.
@appendixsection(Terms)

The term 'materials' as used herein shall refer to all properties
of @psi covered by this document.
@appendix(Specfic Precautions)

@victim, in consideration of the nature of the materials provided
him by @psi shall take these precautions:

@enumerate(@victim will not reveal, disclose or display the
materials to any person other than an authorized employee or
consultant of @psi bound by an agreement similar to this one.

@victim shall use and store the materials in such a fasion as to
prevent access by unauthiorized persons.

@victim shall maintain, use and store all machine readable
representations of the materials only on machines which are the
property of @psi, or machines which are used soley by authorized
employees or consultants of @psi bound by agreements similar to
this one.

@victim shall not discuss with others or describe in
published or distributed writings the details of the materials in
a fasion that would disclose the confidential information
contained in them.

@victim will return  or destroy all copies of the materials
upon the request of @psi, and may be required to furnish evidence
of compliance.

@victim will take all reasonable steps and precautions to
protect the confidentiality of the materials.

@victim will treat all materials created by him in the
course of their association with @psi in accordance with the above
provisions. )
@appendix(Failure to Comply)

@victim understands that failure to comply with the above
provisions may result in serious, material harm to @psi, or its
liscencees or liscencors. @victim furthermore understands
that in the event of failure to comply @psi or its liscencees or
liscencors may take action to recover such damages as may result.
@appendix(Agreement by Undersigned)

These provisions are agreed to by me,
@verbatim(




--------------------------------------------
@case(persona,
individual,"@victim"
corporate,"Representative of @victim")



on --------
    Date
)
@pagefooting()
@index(XYZZY)
@string(chaptertitle="")@comment(this is so that we clear it for the
index and table of coNtents)
