BLUEANDWHITE TITLE for Cedar.Style (Mark property value: centerHeader)
BLUEANDWHITE TITLE for BlueAndWhite.Style (Mark property value: centerRectoHeader)
BLUEANDWHITE TITLE for BlueAndWhite.Style (Mark property value: centerVersoHeader)
XEROX PARC, CSL-83-xx, MAY, 1983 for Cedar.Style (Mark property value: centerFooter)
XEROX PARC, CSL-83-xx, MAY, 1983 for BlueAndWhite.Style (Mark property value: centerRectoFooter)
XEROX PARC, CSL-83-xx, MAY, 1983 for BlueAndWhite.Style (Mark property value: centerVersoFooter)
BlueAndWhite Title
Subtitle, if any
Author1, Author2, and Author3
and institutions if not Xerox
CSL-83-xx Month 1983 [P83-xxxxx]
© Copyright 1983 Xerox Corporation. All rights reserved.
© Copyright 1983 Association of Computing Machinery. Printed with permission.
© Copyright 1983 John Q. Author. All rights reserved.
Abstract: The abstract goes here, unless it is very long. In that case, you should omit the Abstract and CR catergories from the title page, and instead put them on a page by themselves.
The second and succeeding paragraphs, if any, should have the same format Abstract. Unfortunately, if do not copy a form for these nodes, you will have to manually assign Look-b to the Abstract and CR Categories headings.
A version of this paper will appear/appeared in Publication, vol xx, no xx, Month, Year.
CR Categories and Subject Descriptors: Class No [Major Classification]: Classification Topic — Descriptors, Descriptors, ... Computing Reviews categories from January 1982 CACM go here;
Additional Keywords and Phrases: keywords, keywords
XEROX   Xerox Corporation
    Palo Alto Research Center
    3333 Coyote Hill Road
    Palo Alto, California 94304

DRAFT — For Internal Xerox Use Only — DRAFT
1. Chapter One Heading
1. CHAPTER ONE HEADING for BlueAndWhite.Style (Mark property value: centerRectoHeader)
All paragraphs in a blue-and-white have the format body. All headings have the format head with the nesting level determining the effective style. Chapters in blue-and-whites should begin an odd-numbered page, so place a pageBreak format node prior to the chapter. Rather than spend any time in manually overcoming the shortcomings of the Tioga TSetter pagination, leave the job of pagination to the publication czar.
A node which defines the running head can be inserted nested under the chapter heading. It has the node property Mark with value centerRectoHeader. The TSetter understands this to be a header definition and diverts the text for later assembly during page layout. All paragraphs in a blue-and-white have the format body.
All paragraphs in a blue-and-white have the format body.
1.1 Major section heading
Major sections are nested under the introductory paragraphs of the chapter. Each heading is numbered and has the format head, with its nesting level determining the effective style. All paragraphs in a blue-and-white have the format body.
1.1.1 Minor section heading
Minor sections are nested under the introductory paragraphs of the section. Each heading is numbered and has the format head, with its nesting level determining the effective style. All paragraphs in a blue-and-white have the format body.
Run-in section heading. A section begun with a run-in heading has the format head yet also contains paragraph text. Run-in section headings are usually not numbered. To get the formatting right, they must be nested beneath minor section headings. This node has format head.
All paragraphs in a blue-and-white have the format body.
1.2 Major section heading
Major sections are nested under the introductory paragraphs of the chapter. Each heading is numbered and has the format head, with its nesting level determining the effective style. All paragraphs in a blue-and-white have the format body.
1.2.1 Minor section heading
Minor sections are nested under the introductory paragraphs of the section. Each heading is numbered and has the format head, with its nesting level determining the effective style. All paragraphs in a blue-and-white have the format body.
Run-in section heading. A section begun with a run-in heading has the format head yet also contains paragraph text. Run-in section headings are usually not numbered. To get the formatting right, they must be nested beneath minor section headings. This node has format head.
All paragraphs in a blue-and-white have the format body.
2. Chapter Two Heading
2. CHAPTER TWO HEADING for BlueAndWhite.Style (Mark property value: centerRectoHeader)
All paragraphs in a blue-and-white have the format body. All headings have the format head with the nesting level determining the effective style. Chapters in blue-and-whites should begin an odd-numbered page, so place a pageBreak format node prior to the chapter. Rather than spend any time in manually overcoming the shortcomings of the Tioga TSetter pagination, leave the job of pagination to the publication czar.
A node which defines the running head can be inserted nested under the chapter heading. It has the node property Mark with value centerRectoHeader. The TSetter understands this to be a header definition and diverts the text for later assembly during page layout. All paragraphs in a blue-and-white have the format body.
All paragraphs in a blue-and-white have the format body.
2.1 Major section heading
Major sections are nested under the introductory paragraphs of the chapter. Each heading is numbered and has the format head, with its nesting level determining the effective style. All paragraphs in a blue-and-white have the format body.
2.1.1 Minor section heading
Minor sections are nested under the introductory paragraphs of the section. Each heading is numbered and has the format head, with its nesting level determining the effective style. All paragraphs in a blue-and-white have the format body.
Run-in section heading. A section begun with a run-in heading has the format head yet also contains paragraph text. Run-in section headings are usually not numbered. To get the formatting right, they must be nested beneath minor section headings. This node has format head.
All paragraphs in a blue-and-white have the format body.
2.2 Major section heading
Major sections are nested under the introductory paragraphs of the chapter. Each heading is numbered and has the format head, with its nesting level determining the effective style. All paragraphs in a blue-and-white have the format body.
2.2.1 Minor section heading
Minor sections are nested under the introductory paragraphs of the section. Each heading is numbered and has the format head, with its nesting level determining the effective style. All paragraphs in a blue-and-white have the format body.
Run-in section heading. A section begun with a run-in heading has the format head yet also contains paragraph text. Run-in section headings are usually not numbered. To get the formatting right, they must be nested beneath minor section headings. This node has format head.
All paragraphs in a blue-and-white have the format body.
3. Sample Styles
SAMPLE STYLES for BlueAndWhite.Style (Mark property value: centerRectoHeader)
The following are samples of all the styles provided in Cedar.Style, and therefore by induction are available in BlueAndWhite.Style. This indented paragraph has the format body.
Block style paragraphs have the format block. Unfortunately its difficult to see block paragraphs because there is no additional interparagraph leading.
This node has format center. Lines of text in this node are centered on the page. When there is more text than fits on only one centered line, subsequent lines are also centered.
This node has format continuation. It is essentially a block style paragraph with a greater page break penalty to tend to attach it to what was displayed immediately preceding this node. However, the current implementation of the Tioga TSetter ignores page break penalties.
This node has format display. It is an indented block paragraph with extra white space above and below to set it off from surrounding material.
This node has format continuation. It is essentially a block style paragraph with a greater page break penalty to tend to attach it to what was displayed immediately preceding this node.
This node has format example. It is intended for fragments of Cedar programs or other code which is best represented in the Tioga typeface.
This node has format continuation. It is essentially a block style paragraph with a greater page break penalty to tend to attach it to what was displayed immediately preceding this node.
This node has format indent. It provides an indented block paragraph. Note that there is another format for quotes.
This node has format item, which is an adaptation of the format indent. It would normally be used for definitions, labelled paragraphs, etc. where there is some text hanging out to the left. Often looks are given to the hung text.
This node has format lead1, which provides more space to lead out superscripts, larger type, etc. It is an adaptation of the block paragraph. The leading between lines is larger as is the interparagraph leading.
This node has format lead2, which has even more leading between lines than format lead1. It is an adaptation of the block paragraph. The leading between lines is larger as is the interparagraph leading.
This node has format lead3, which has even more leading between lines than format lead2. It is an adaptation of the block paragraph. The leading between lines is larger as is the interparagraph leading.
This node has format note for writing fine points, footnotes, inline references, etc. It use will be common practice in documents until there is a facility for footnotes.
This node has format quote for quotations and other displays. It is essentially an indented block paragraph.
This node and its nested children have format table. At present only fixed tab stops are supported by four formats:
 table 40 spaces per column
 table0 35
 table1 30
 table2 25
 table3 20
If you wish to design a custom table, you should create a style definition and affix it to the node or branch by the StyleDef property. See the TiogaDoc manual for details on StyleDef. In fact, TiogaDoc has a StyleDef on its root node to define the Nest print rule. Proofing tables is much simpler if you use ShowPress to view the formatted table which you edit in a separate file for compactness.
References
REFERENCES (Mark property value: centerRectoHeader)
1. Author, Book title, Publisher, date. Each reference is a node with format reference, with a one- or two-digit reference number.
2. Author, Article title'', Publication title, vol. xx, no. xx, date.
3. Donald E Knuth, The Art of Computer Programming, vol. 1, Addison-Wesley, 1968.
4. Robert M. Metcalfe and David R. Boggs, Ethernet: Distributed Packet Switching for Local Computer Networks'', Communications of the ACM, vol. 19 no. 7, July 1976.
Alternative Reference style
[Author, Year]
Author, Book title, Publisher, date. Each citation has format reference, with a carriage return after the citation.
[Knuth, 1968]
Donald E Knuth, The Art of Computer Programming, vol. 1, Addison-Wesley, 1968.
[Metcalfe & Boggs, 1976]
Robert M. Metcalfe and David R. Boggs, Ethernet: Distributed Packet Switching for Local Computer Networks'', Communications of the ACM, vol. 19 no. 7, July 1976.