+++ /dev/null
-<!-- ORA entity set for v 3 motif -->
-
-<!ENTITY amtfA "<CITESECT>Appendix A, Managing Your Environment</CITESECT>" >
-<!ENTITY amtfB "<CITESECT>Appendix B, Release 5 Standard Fonts</CITESECT>" >
-<!ENTITY amtfC "<CITESECT>Appendix C, Standard Bitmaps</CITESECT>" >
-<!ENTITY amtfD "<CITESECT>Appendix D, Standard Cursors</CITESECT>" >
-<!ENTITY amtfE "<CITESECT>Appendix E, xterm Control Sequences</CITESECT>" >
-<!ENTITY amtfF "<CITESECT>Appendix F, Translation Table Syntax</CITESECT>" >
-<!ENTITY amtfG "<CITESECT>Appendix G, Widget Resources</CITESECT>" >
-<!ENTITY amtfH "<CITESECT>Appendix H, Obtaining Example Programs</CITESECT>" >
-<!ENTITY bmtf00 "<CITEBOOK>Volume Zero, X Protocol Reference Manual</CITEBOOK>" >
-<!ENTITY bmtf01 "<CITEBOOK>Volume One, Xlib Programming Manual</CITEBOOK>" >
-<!ENTITY bmtf02 "<CITEBOOK>Volume Two, Xlib Reference Manual</CITEBOOK>" >
-<!ENTITY bmtf04 "<CITEBOOK>Volume Four, X Toolkit Intrinsics Programming Manual</CITEBOOK>" >
-<!ENTITY bmtf05 "<CITEBOOK>Volume Five, X Toolkit Intrinsics Reference Manual</CITEBOOK>" >
-<!ENTITY bmtf06 "<CITEBOOK>Volume Six, Motif Programming Manual</CITEBOOK>" >
-<!ENTITY bmtf08 "<CITEBOOK>Volume Eight, X Window System Administrator's Guide</CITEBOOK>" >
-<!ENTITY cmtf0 "<CITESECT>Preface</CITESECT>" >
-<!ENTITY cmtf01 "<CITESECT>Chapter 1, An Introduction to the X Window System</CITESECT>" >
-<!ENTITY cmtf02 "<CITESECT>Chapter 2, Getting Started</CITESECT>" >
-<!ENTITY cmtf03 "<CITESECT>Chapter 3, Working in the X Environment</CITESECT>" >
-<!ENTITY cmtf04 "<CITESECT>Chapter 4, More about the mwm Window Manage</CITESECT>" >
-<!ENTITY cmtf05 "<CITESECT>Chapter 5, The xterm Terminal Emulator</CITESECT>" >
-<!ENTITY cmtf06 "<CITESECT>Chapter 6, Font Specification</CITESECT>" >
-<!ENTITY cmtf07 "<CITESECT>Chapter 7, Graphics Utilities</CITESECT>" >
-<!ENTITY cmtf08 "<CITESECT>Chapter 8, Other Clients</CITESECT>" >
-<!ENTITY cmtf09 "<CITESECT>Chapter 9, Working with Motif Applications</CITESECT>" >
-<!ENTITY cmtf10 "<CITESECT>Chapter 10, Command-line Options</CITESECT>" >
-<!ENTITY cmtf11 "<CITESECT>Chapter 11, Setting Resources</CITESECT>" >
-<!ENTITY cmtf12 "<CITESECT>Chapter 12, Specifying Color</CITESECT>" >
-<!ENTITY cmtf13 "<CITESECT>Chapter 13, Customizing mwm</CITESECT>" >
-<!ENTITY cmtf14 "<CITESECT>Chapter 14, Setup Clients</CITESECT>" >
-
+++ /dev/null
-<CHAPTER><TITLE>The Elements Alphabetized</TITLE>
-<PARA>Emphasized entries indicate
-block-oriented elements.
-“Dropped” elements appeared in version 1.2.2 but do not
-appear in the current version; many have been shifted
-to attribute values in cptrphrase.gp.
-</PARA>
-<SECT1><TITLE>Common Attributes</TITLE>
-<PARA>Common attributes now include ID, Lang (language), Remap
-(to store the former GI of an element in a document filtered
-to Docbook), Role (to type Docbook elements when
-need be), and XRefLabel (text to be displayed as the
-label of cross references to a block-oriented element).
-</PARA>
-<PARA>ID is an identifier, which must be a
-string that is unique at least within the document and
-which must begin with a letter. Lang should be a
-language code drawn from ISO 639 (perhaps extended with
-a country code drawn from ISO 3166, as en_US). Use
-it when you need to signal your application to change
-hyphenation and other display characteristics.
-Remap is a device for
-preserving a previous tag name when fitting a document
-to the DocBook DTD.
-Think of <SGMLTAG>CHAPTER Remap=“Fascicle”</SGMLTAG>
-as saying, “I'm a Chapter now, but in a previous life
-I was a Fascicle.” Role allows you to clone DocBook
-elements without creating new ones: if you have lists
-of vegetables and lists of fruit (perhaps displayed
-differently), give them
-<SGMLTAG>Role=vegetables</SGMLTAG> and <SGMLTAG>Role=fruit</SGMLTAG> attributes.
-</PARA></SECT1>
-<SECT1><TITLE>Other Attributes</TITLE>
-<PARA>Certain other attributes occur regularly. PageNum is
-the number of the page on which a given element begins
-or occurs in a printed book. Label holds some text
-associated with its element that is to be output when
-the document is rendered. XRefLabel holds some text
-that is to be used when a cross reference (XRef)
-is made to its element. Type is used with links,
-as it is clear that different types of links may be
-required; it duplicates the function of Role.
-</PARA>
-<PARA>The Class attribute has been introduced in an attempt to
-control the number of computer-specific in-line elements.
-The elements that bear the Class attribute, such as
-Interface, have general
-meanings that can be made more specific
-by providing a value for Class from the delimited list
-for that element. For example, for the Interface element
-one may specify Menu, or Button; for the MediaLabel
-element one may specify CDRom or Tape. Each element
-has its own list of permissible values for Class, and
-no default is set, so you can ignore this attribute
-if you wish.
-</PARA>
-<PARA>Some attributes are defined with the keyword %yesorno;,
-which resolves to NUMBER. To supply the required number,
-which must be either 1 or 0, you can use the
-parameter entities %yes; (1); or %no; (0).
-</PARA>
-<PARA>An attributes that has the keyword IMPLIED bears no
-processing expections if it is absent or its
-value is null. Application designers might wish to
-supply plausible defaults, but none is specified here.
-However, it would be plausible to imply that the
-language of a DocBook instance is U.S. English
-unless specified otherwise. (This matter may be clarified
-when character set specification is added to the DTD;
-for now, the character set must be inferred from the
-Lang attribute value, if present.)
-</PARA></SECT1>
-<SECT1><TITLE>cptrphrase.gp</TITLE>
-<PARA>This parameter entity has been introduced to provide
-some structure for in-line elements related to computers.
-Its contents are: plain text,
-Anchor, BeginPage, all the index
-terms, Comment, Subscript, Superscript,
-all the kinds of links, Action, Application, ClassName,
-Command,
-ComputerOutput,
-Database, ErrorName, ErrorType,
-EventStructure, EventType,
-Filename, Function, Hardware, Interface,
-InterfaceDefinition, KeyCap, KeyCode, KeySym, LineAnnotation,
-Literal, Mask, MediaLabel, MsgText, Option,
-Optional, Parameter, Property, ProtocolRequest,
-Replaceable, ReturnValue, StructField, StructName, Symbol,
-SystemDialog, SystemItem, Token, Type, and UserInput.
-</PARA>
-<PARA>Many of these elements now have attributes
-with delimited value lists; some former in-line elements now appear as
-values for those attributes.
-</PARA></SECT1>
-<SECT1><TITLE>“In-line” vs. “In flow”</TITLE>
-<PARA>In this document, “in-line” means ”occuring within a line
-of text, like a character or character string, not causing
-a line break.” This term is sometimes used to
-refer to objects such as an illustration around which
-something like a paragraph is wrapped; here that circumstance
-will be called “in flow.” There is no provision yet
-for indicating that an object is in flow, but one could
-make creative use of the Role attribute to do so.
-</PARA>
-<PARA>A related point: formal objects have titles; informal
-objects do not. That an object is informal does not mean
-that it is in-line: these are two different
-characteristics.
-</PARA></SECT1>
-<SECT1><TITLE>CALS Tables</TITLE>
-<PARA>In this revision, the former Table models have been
-replaced by one derived from MIL-M-28001B, dated
-26 July 1993 (supersedes MIL-M-28001A of 20 July
-1990.)
-The documentation of Table and its subelements,
-below, has been taken from that document,
-with some editing and attempts at clarification.
-</PARA></SECT1>
-<SECT1>
-<TITLE>List of Elements</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY><TERM><EMPHASIS>Abstract</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A document summary.
-Abstract contains an optional Title followed by
-paragraphs, and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Abbrev</TERM>
-<LISTITEM>
-<PARA>An abbreviation, especially one
-followed by a period. It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Ackno</TERM>
-<LISTITEM>
-<PARA>Acknowledgements in an Article.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Acronym</TERM>
-<LISTITEM>
-<PARA>A pronounceable contraction of
-initials, usually printed in all caps or small caps.
-It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Action</TERM>
-<LISTITEM>
-<PARA>A function invoked in response to a user event. It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Address</TERM>
-<LISTITEM>
-<PARA>A real-world address. It contains
-any number, in any order, of: Street, POB, Postcode,
-City, State, Country, Phone, Fax, and Email.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Affiliation</TERM>
-<LISTITEM>
-<PARA>Author's institutional affiliation.
-It contains, in order, an optional ShortAffil, any number
-of JobTitles, optional OrgName, any number of
-Orgdivs, and any number of Addresses.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Anchor</TERM>
-<LISTITEM>
-<PARA>Marks a target for a Link.
-Anchor may appear almost anywhere, and has no content.
-Anchor has ID, Pagenum, Remap, Role, and XRefLabel attributes;
-the ID is required.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Appendix</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>May occur only after Chapters
-or References, in a Book.
-Appendix begins with an optional DocInfo, followed by
-a required Title, optional TitleAbbrev, and anything
-found in the body of a Chapter.
-It has common and Label attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Application</TERM>
-<LISTITEM>
-<PARA> The name of a software program.
-It may contain members of cptrphrase.gp,
-and has common, Class, and MoreInfo attributes.
-Class may be Hardware or Software (no default). MoreInfo
-may have the value RefEntry, indicating that a
-RefEntry exists containing additional information
-about this term. The default value for MoreInfo is None.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Arg</TERM>
-<LISTITEM>
-<PARA>Argument in a CmdSynopsis. Arg may contain
-any number of Args, Groups, Options, SynopFragmentRefs, Replaceables,
-in any order, mixed with plain text. Arg is defined in
-the DTD as having common attributes and the attributes
-defined by the parameter entities argchcatt and repatt.
-</PARA>
-<PARA><EMPHASIS>argchcatt</EMPHASIS> or “argument choice attribute”
-resolves to the attribute
-Choice, with allowed values Opt (the Arg is
-optional; the default), Req (it is required),
-and Plain (neither optional nor required).
-</PARA>
-<PARA><EMPHASIS>repatt</EMPHASIS> or “repetition attribute”
-resolves to the attribute Rep, with allowed
-values Repeat (the Arg may be repeated; the default)
-and Norepeat (the Arg does not repeat).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ArtHeader</EMPHASIS></TERM>
-<LISTITEM>
-<PARA> Metainformation for an Article.
-ArtHeader has, in order, a required Title, optional
-TitleAbbrev, optional Subtitle, one or more AuthorGroups,
-optional BookBiblio, a required ArtPageNums,
-any number of
-Abstracts, any number of ConfGroups, and finally any number
-ContractNums and ContractSponsors, in any order.
-ArtHeader has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Article</EMPHASIS></TERM>
-<LISTITEM>
-<PARA> An article in a journal. Book may
-be used to hold Articles. An Article has, in order,
-a required ArtHeader, main contents as for Chapter,
-then any number of Indexes, Glossaries, Bibliographies,
-Appendixes and Acknos, in any order. Article has
-common and ParentBook attributes, the latter pointing
-to the ID of the enclosing Book.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ArtPageNums</TERM>
-<LISTITEM>
-<PARA> Page numbers of an Article
-as published. It contains plain text (e.g., 23-147).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Author</TERM>
-<LISTITEM>
-<PARA>Author of a document, occuring in
-AuthorGroup. It consists of
-one or more of the following, in any order:
-Honorific, Firstname, Surname, Lineage, OtherName,
-Affiliation, and AuthorBlurb. It has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>AuthorBlurb</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Short description of
-author.
-AuthorBlurb contains an optional Title followed by
-paragraphs, and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>AuthorGroup</TERM>
-<LISTITEM>
-<PARA>Wrapper for Author information.
-It contains one or more CorpAuthors, Collabs, and
-Authors, in any order.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>AuthorInitials</TERM>
-<LISTITEM>
-<PARA>Indicates the author of
-a Revision or Comment. It contains plain text
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>BeginPage</TERM>
-<LISTITEM>
-<PARA>Marks a page break in a print
-version of a work that may be displayed online.
-It is without content, but has ID, PageNum, Remap, Role, and
-XRefLabel attributes. The ID is required.
-The value of PageNum, which is
-not required, should be
-the folio (page number) of the page beginning at that
-point. <EMPHASIS>Usage Note:</EMPHASIS> Once you give
-a PageNum to a BeginPage, subsequent BeginPages should
-be assumed to indicate that value incremented by one per
-BeginPage. You can indicate a change or reset in page
-numbering by providing a PageNum value for a later
-BeginPage.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>BiblioDiv</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A section of a
-Bibliography. It may have, in order, an
-optional Title, optional TitleAbbrev,
-any number of block-oriented elements,
-followed by one or more BiblioEntries.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>BiblioEntry</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An entry in a Bibliography.
-It may begin and end with BiblioMiscs,
-between which must be an ArtHeader, BookBiblio,
-or SeriesInfo. That is, the main content of a
-BiblioEntry may be identical to a section of
-metainformation. BiblioEntry has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Bibliography</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A bibliography. It may be a
-book component on its own, or may appear within a Preface, Chapter, or Appendix, or at
-the end of a Glossary. It may have a DocInfo,
-a Title and a TitleAbbrev, then optional
-block-oriented elements, and then
-one or more BiblioEntries or one or more BiblioDivs.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>BiblioMisc</TERM>
-<LISTITEM>
-<PARA>Untyped information required in a
-BiblioEntry or BookInfo, in addition to the elements
-required there. It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>BlockQuote</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A quotation set off from the main text,
-rather than occurring in-line. It may have a Title, followed
-by block-oriented elements. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Book</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A collection of book components.
-The Book content model has been drawn
-more tightly since version 1.2.2, but is loose enough
-to accomodate English, French, and Japanese books.
-A Book may have
-a Title and TitleAbbrev, followed in order by an optional
-BookInfo, an optional ToC,
-any number of LoTs, any number of Prefaces,
-main contents, and back matter. The main contents are
-required, and must be one or more Parts;
-one or more Chapters followed by any
-number of References;
-one or more Articles; or one or more References.
-All back matter is optional, but must appear in order:
-any number of Appendices,
-a Glossary, a Bibliography, and any number of Indexes
-and SetIndexes,
-followed by any number of LoTs followed by an optional
-ToC. Book has common, FPI, and Label
-attributes. The FPI attribute is intended to hold an
-SGML Formal Public Identifier for the Book;
-the Label attribute can be used to supply the
-number of a Book, or you can use the content of the VolumeNum element in BookInfo.
-in constructing Formal Public Identifiers you use
-your ISBN publisher's prefix. In the ISBN
-1–565692–043–0, for example, the publisher's
-prefix is 565692.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>BookAcronym</TERM>
-<LISTITEM>
-<PARA>Dropped.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>BookBiblio</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>All the information about a book
-that may be relevant
-to a bibliographical citation; occurs in BookInfo and
-may be used in BiblioEntry.
-Only Title and AuthorGroup
-are required. BookBiblio may contain, in order:
-the required Title, optional TitleAbbrev,
-Subtitle, and Edition, followed one or more required
-AuthorGroups; then, optionally, either an ISBN followed
-by an
-optional VolumeNum or an ISSN followed by
-optional VolumeNum, optional IssueNum, and an
-optional PageNums. After these elements there may
-occur, again optionally and in order,
-InvPartNumber, ProductNumber, ProductName,
-PubsNumber, and ReleaseInfo; then there may be any number
-of Pubdates followed by any number of Publishers,
-followed by optional
-Copyright, then optional SeriesInfo; then any number of
-Abstracts, any number of ConfGroups, any number
-of ContractNums mixed with any number of ContractSponsors,
-and an optional
-PrintHistory followed by an optional RevHistory.
-BookBiblio has common attributes.
-is the numbers of the pages contained in a given issue
-or volume
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>BookInfo</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Metainformation for a Book,
-in which it may appear. BookInfo must contain
-a BookBiblio, followed by any number of LegalNotices,
-followed by any number of ModeSpecs (which
-are pointed to by the LinkMode attribute of OLink,
-and are collected here for convenience).
-BookInfo has common attributes
-and a Contents attribute, the
-values of which are the IDs of the ToC, LoTs,
-Prefaces, Parts, Chapters, Appendixes, References,
-Glossary, Bibliography, and indexes
-comprising the Book, in the order of their appearance.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>BookTitle</TERM>
-<LISTITEM>
-<PARA>Dropped.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>BridgeHead</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A free-floating heading not
-tied to the Sect hierarchy. It may contain
-in-line elements and has common and Renderas
-attributes. Use the Renderas attribute to indicate
-the format in which the BridgeHead should appear (Sect1,
-Sect2, Sect3, Sect4, Sect5, or Other, the default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Button</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Interface.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Caution</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An admonition set off from the text;
-Tip, Warning, Important, and Note all share its model.
-Its contents may include paragraphs, lists, and so forth,
-but not another admonition.
-Caution and its sisters have common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Chapter</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A part of a Book.
-Chapter contain anything except
-higher-level elements
-such as Part, Book, and Set, or peers such as
-Appendix and Preface. A Chapter
-may begin with a DocInfo, followed by
-a required Title, optional TitleAbbrev, and body.
-The body may be
-either paragraphs and block-oriented elements or Sects containing
-them. At the beginning and end of the body of
-a Chapter, or the beginning and end of any Sect,
-there may be any number of ToCs, LoTs, Indexes, Glossaries,
-and Bibliographies, not that such an organization is
-recommended for ordinary use.
-Chapter has common and Label attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Character</TERM>
-<LISTITEM>
-<PARA>An element of a writing
-system. Characters may belong to Charsets, and in some contexts
-fonts represent characters.
-(See <EMPHASIS>Glyph,</EMPHASIS> <EMPHASIS>Font</EMPHASIS>.) It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Charset</TERM>
-<LISTITEM>
-<PARA>A conventionally defined
-set of characters, (not a font).
-It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Citation</TERM>
-<LISTITEM>
-<PARA>Any in-line bibliographic
-reference to another published work that uses a reference
-string, such as an abbreviation in a Bibliography.
-Compare CiteTitle.
-Citation contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CiteTitle</TERM>
-<LISTITEM>
-<PARA>A citation for some published
-work. Compare Citation.
-It may contain members of cptrphrase.gp,
-and has common and Pubwork attributes.
-The value of Pubwork should indicate the type
-of work cited; it may be Article, Book, Chapter,
-RefEntry, or Section (no default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CiteBook</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>CiteTitle.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CiteChap</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>CiteTitle.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CiteRefEntry</TERM>
-<LISTITEM>
-<PARA> A citation of a reference
-entry. It must have a RefEntryTitle, followed
-by an optional ManVolNum. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CiteSect</TERM>
-<LISTITEM>
-<PARA> Dropped. See <EMPHASIS>CiteTitle.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>City</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Classname</TERM>
-<LISTITEM>
-<PARA>The name of the class to which a
-program component belongs.
-It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CmdSynopsis</TERM>
-<LISTITEM>
-<PARA>Synopsis for a Command. A
-CmdSynopsis contains any number of
-Args and Groups, in any order, followed by a
-single required
-Command, another set of any number of Args and
-Groups, in any order, and ending with any number of
-optional SynopFragments. CmdSynopsis has common,
-Label, and Sepchar attributes. Label has no
-default; Sepchar has the default “ ”.
-The following is courtesy Eve Maler (see also
-the entries for the subelements elsewhere in
-this list:
-</PARA>
-<PARA>An argument at the command level (Arg)
-is a parameter passed to a
-command to specify or modify the command's behavior; it
-often consists of a variable value
-(Replaceable)
-such as a filename field, or an option
-(Option) and its own nested
-argument (Arg). If the contents of an
-argument are not marked up further, they are assumed to be
-something the user must type as shown (probably an option,
-but this is implicit). The Choice attribute on the two
-argument elements indicates whether the argument must be
-present (“Req”, the default), whether it
-is optional (“Opt”), or whether no indication of presence
-is given (“Plain”, the default).
-</PARA>
-<PARA>A group (Group) as a peer
-or child of an argument is a
-collection of arguments, options, or other constructs that must appear in some
-relation to each other. For example, three options that are
-exclusive of each other and are optional would be in a group
-with a choice of “Opt” (the default).
-The “Optmult” choice allows zero or more of the
-children of the group to be supplied, and the “Reqmult”
-choice requires one or more of the children of the group to
-be supplied.
-</PARA>
-<PARA>An option (Option) is a literal string or name of a
-parameter-keyword controlling the behavior of the command; a
-variable value (Replaceable) is a
-mnemonic name for a value that the user must supply, such as
-an input file name. The Option and Replaceable
-elements are available in text as
-well as in synopses. Stacks of options (for example,
-“-aefstuv”) should
-be put into a single Option element for simplicity.
-</PARA>
-<PARA>Depressingly complex constructs may
-appear anywhere within a
-synopsis. A SynopFragment reference (SynopFragmentRef) is a
-special kind of variable value assigned in place of this
-construct, which is
-then broken out into its own synopsis subset (SynopFragment) for
-clarity. A SynopFragment must have an ID, and any
-SynopFragmentRefs supplied
-must point to some SynopFragment.
-</PARA>
-<PARA>Plain text within a CmdSynopsis
-is allowed only inside Cmd, Arg,
-Option, Replaceable, and SynopFragmentRef. The
-top-level separator character attribute
-value (“ ” by default) should
-be used to separate arguments and groups
-from their repeat indicators (“. . .”) and
-to separate Commands and their arguments and groups at the top level.
-</PARA>
-<PARA>The CmdSynopsis structure does
-not meet the needs of DCL
-and other VMS-related command languages that have command
-parameters such
-as /[NO]WRITE, positional versus nonpositional parameters, and so on.
-Probably additional low-level elements would have to be
-added to the mix and the top-level structure enhanced
-slightly to account for
-these. However, CmdSynopsis
-appears to meet most UNIX-related needs.
-</PARA>
-<PARA><EMPHASIS>Processing expectations:</EMPHASIS>
-The “Opt” settings on arguments and groups (and probably
-“Optmult” as
-well for now) should produce square brackets.
-The “Req”
-settings (and probably “Reqmult” as well for now)
-should produce curly braces. The children of Group (if
-there is more than one child) should be either separated by vertical bars or formatted as a stacked list.
-Spacing at the Command and Group levels
-is controlled by formatter defaults and/or the
-sepchar setting.
-</PARA>
-<SCREEN>
-Example command synopsis in typical UNIX(tm) format:
-
- rm [-f] [-r] [-i] [-] {filename|dirname} . . .
- | | | | | | | | |
- | optional args | | | repeat indicator
- | (contain options)| | |
- | | | second child of group
- command name | |
- | first child of group
- |
- required repeatable group
-
- SGML source for this example:
-<SGMLTAG>CMDSYNOPSIS</SGMLTAG>
-<SGMLTAG>COMMAND</SGMLTAG>rm<SGMLTAG>/COMMAND</SGMLTAG>
-<SGMLTAG>ARG Choice=“opt”</SGMLTAG>-f<SGMLTAG>/ARG</SGMLTAG> (<SGMLTAG>OPTION</SGMLTAG> not required for arg contents
-<SGMLTAG>ARG Choice=“opt”</SGMLTAG>-r<SGMLTAG>/ARG</SGMLTAG> unless doing extra-special processing)
-<SGMLTAG>ARG Choice=“opt”</SGMLTAG>-i<SGMLTAG>/ARG</SGMLTAG>
-<SGMLTAG>ARG Choice=“opt”</SGMLTAG>-<SGMLTAG>/ARG</SGMLTAG> (various synopsis formats
-<SGMLTAG>GROUP Choice=“req” Rep=“repeat”</SGMLTAG> can be generated)
-<SGMLTAG>REPLACEABLE</SGMLTAG>filename<SGMLTAG>/REPLACEABLE</SGMLTAG>
-<SGMLTAG>REPLACEABLE</SGMLTAG>dirname<SGMLTAG>/REPLACEABLE</SGMLTAG>
-<SGMLTAG>/GROUP</SGMLTAG>
-<SGMLTAG>/CMDSYNOPSIS</SGMLTAG>
-</SCREEN>
-</LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Collab</TERM>
-<LISTITEM>
-<PARA>A collaborative group
-of authors. It contains a required CollabName
-followed by any number of Affiliations.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CollabName</TERM>
-<LISTITEM>
-<PARA>Name of a collaborative group
-of authors. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ColSpec</TERM>
-<LISTITEM>
-<PARA>Column specifier,
-that is, formatting information for a
-column in a Table, part of TGroup, THead, or TGroup.
-ColSpec is an empty element, bearing common
-and Align, Char, Charoff,
-Colname, Colnum, Colsep, Colwidth, and Rowsep
-attributes. The default values come from the TGroup,
-THead, or TFoot that starts the current enclosing group.
-Each ColSpec is for a single column, so it properly has a
-column number, Colnum, implicitly in order starting
-from 1, and an optional Colname by which it is known when
-used in any SpanSpec or in Entry.
-A ColSpec set on THead or TFoot should be complete for
-all columns. It overrides those on the containing TGroup
-and applies to just the THead or
-TFoot. If there is no ColSpec used within THead or
-TFoot, then the ColSpec of the containing TGroup (or the
-prior TGroup) is used. ColSpecs from the containing
-TGroup apply to TBody.
-</PARA>
-<PARA>For <EMPHASIS>TGroupStyle</EMPHASIS>, see <EMPHASIS>TGroup.</EMPHASIS>
-</PARA>
-<PARA><EMPHASIS>Align</EMPHASIS> controls the horizontal position
-of text within the column.
-The value of Align may be Left (quad flush left),
-Center (centered), Right (quad flush right),
-Justify (both quad left and right), or Char (align to
-the left of Char, positioned by Charoff). There is
-no default.
-</PARA>
-<PARA><EMPHASIS>Char</EMPHASIS> contributes to Align. If the
-value of Align is “char”, the value of Char
-should be a character on the first occurrance
-of which the entry is to be aligned. If that
-character does not occur in the entry, the entry
-is aligned to the left of the position determined
-by Charoff. (Think of using the decimal point to
-align decimal numbers: Char=“. ”and
-Charoff says how far over in the column the decimals
-should be; if no decimal occurs, the number is an
-integer and is aligned to the left of the decimals.)
-No value implies there
-is no character to align on.
-The default is implied, from the enclosing TGroup.
-(That is, you normally declare that an entire TGroup
-shall be decimal-aligned, but if you need to align
-a specific column differently, you can do it by
-specifying another Char at the ColSpec level.)
-</PARA>
-<PARA><EMPHASIS>Charoff</EMPHASIS> contributes with Char to Align.
-Charoff is the proportion
-of the current column width, expressed in percentage,
-to be allowed before the left edge of the first occurrence
-of the character given as the value of Char.
-The default is inherited from the enclosing TGroup.
-That is, if columns in a TGroup are to be decimal-aligned,
-and the decimal point is to fall three-quarters of the
-way across each cell (most of your numbers are of the
-form 123.4), you could set Charoff to 75 in
-TGroup; that value would be inherited by ColSpec, where
-you could modify it for a specific column (for
-example, by setting it to
-50 for a column of numbers of the form 12.34).
-</PARA>
-<PARA><EMPHASIS>Colname</EMPHASIS> gives the name of the column, which
-is used
-to specify the position in a row, or the start or end of a
-horizontal span of columns (SpanSpec). There is no default.
-</PARA>
-<PARA><EMPHASIS>Colnum</EMPHASIS> gives the number of the column,
-counting from 1 at left of the table.
-There is no default.
-</PARA>
-<PARA><EMPHASIS>Colsep</EMPHASIS>
-determines column separators. If its value
-is Yes, display the internal column rulings to
-the right of each item; if No, do not
-display it. It is ignored for the last column, where the
-Frame setting applies. There is no default. The
-value is inherited from TGroupStyle if used.
-</PARA>
-<PARA><EMPHASIS>Colwidth</EMPHASIS> is either a proportional
-measure of the form <EMPHASIS>number*</EMPHASIS>, such as “5*” for
-5 times the proportion, or “*” (=“1*”); or a
-fixed measure, such as 2pt for 2
-points, 3pc for 3 picas; or a mixed measure, such as 2*+3pt.
-Coefficients are positive numbers with up to
-two decimal places. There is no default.
-If no value is given, the value should
-be obtained from the FOSI, or, if there is no FOSI value,
-the value 1 should be used. (Perhaps this means that
-you can vary the width of columns by stating their relative
-proportions, or you can give fixed widths. If you use
-a decimal number less than zero, express it in the form
-0.2, not .2.)
-</PARA>
-<PARA><EMPHASIS>Rowsep</EMPHASIS>
-determines row separators. If its content is
-Yes, display the internal vertical row ruling
-below each item; if No, do not display it. It is
-ignored for the last row of the table, where
-the value of Frame applies to the entire Table.
-There is no default.
-The value is inherited from TGroupStyle, if used.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Command</TERM>
-<LISTITEM>
-<PARA>An executable program, or
-the entry a user makes to execute a command.
-It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Comment</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A remark made within the document file that
-is intended for use during interim stages of production.
-A Comment should not be displayed to the reader of the
-finished, published work. It may appear almost anywhere,
-and may contain almost anything
-below the Section level. Note that,
-unlike an SGML comment, unless you take steps
-to suppress it, the Comment element
-will be output by an SGML parser
-or application. You may wish to do this to display Comments
-along with text during the editorial process.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ComputerOutput</TERM>
-<LISTITEM>
-<PARA>Data presented to the user by
-a computer.
-It may contain elements from cptrphrase.gp,
-and has common and
-MoreInfo attributes For the MoreInfo attribute
-see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ConfGroup</TERM>
-<LISTITEM>
-<PARA>A wrapper for information about
-a conference. It contains any number of ConfDates,
-ConfTitles, ConfNums, Addresses, and ConfSponsors,
-in any order.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ConfNum</TERM>
-<LISTITEM>
-<PARA>The number of a conference. It
-contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ConfSponsor</TERM>
-<LISTITEM>
-<PARA>Sponsor of a conference in connection
-with which a document was written. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ConfDates</TERM>
-<LISTITEM>
-<PARA>Dates of a conference in connection
-with which a document was written. It contains plain text
-(e.g., 21-24 May 1927).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ConfTitle</TERM>
-<LISTITEM>
-<PARA>Title of a conference in connection
-with which a document was written. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Constant</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>SystemItem.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ContractNum</TERM>
-<LISTITEM>
-<PARA>Number of a contract under which
-a document was written. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ContractSponsor</TERM>
-<LISTITEM>
-<PARA>Sponsor of a contract under which
-a document was written. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Copyright</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Copyright information about
-a document. It consists of one or
-more Years followed by any number of Holders.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CorpAuthor</TERM>
-<LISTITEM>
-<PARA>Corporate author of a book, for use
-in BookInfo or BiblioEntry. It contains plain text
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>CorpName</TERM>
-<LISTITEM>
-<PARA>Name of a corporation. It contains
-plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Country</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Data</TERM>
-<LISTITEM>
-<PARA>Optional component of FuncParam and
-ParamDef. It wraps plain text, Replaceable, more Data,
-Emphasis, and may contain links and indexing information.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Date</TERM>
-<LISTITEM>
-<PARA>Date of publication or revision.
-It contains plain text. (No provision
-has been made for representing eras; you could include this
-information along with the date data.)
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Database</TERM>
-<LISTITEM>
-<PARA>An organized set of data.
-It may contain members of cptrphrase.gp,
-and has common, Class, and MoreInfo attributes.
-Class may have the value
-Name, Table, Field, Key1, Key2, or Record
-(no default). For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>DbField</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Database.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>DbName</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Database.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>DbRecord</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Database.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>DbTable</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Database.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>DocBook</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Dropped. Use the book component's
-name
-(<EMPHASIS>e.g.,</EMPHASIS> Chapter) as the Doctype, or construct
-a shell Book in which you can insert individual
-book components as entities.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>DocInfo</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Metainformation for a book
-component, in which it may appear. Only Title and AuthorGroup
-are required. DocInfo may contain, in order:
-the required Title, optional TitleAbbrev and
-Subtitle, followed by one or more
-AuthorGroups, any number of
-Abstracts, an optional RevHistory, and any number of
-LegalNotices.
-DocInfo has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Edition</TERM>
-<LISTITEM>
-<PARA>The edition of a document. It contains
-plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Editor</TERM>
-<LISTITEM>
-<PARA>The editor of a document.
-Contents are the same as for <EMPHASIS>Author.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Email</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Emphasis</TERM>
-<LISTITEM>
-<PARA>Provided for use where you would
-traditionally use italics
-or bold type to emphasize a word or phrase.
-It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Entry</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A euphemism for a cell in a table—you'd
-rather be in an Entry than in a Cell, wouldn't you?
-An Entry occurs in
-a Row, and must have either some assortment
-of paragraphs, admonitions, lists,
-and Graphics, or in-line elements.
-Entry has common
-and Align, Char, Charoff, Colname, Colsep,
-Morerows, Nameend, Namest,
-Rotate, Rowsep, Spanname, and VAlign attributes.
-Attribute values may be inherited
-from enclosing elements that share the same
-attribute.
-“An Entry not specified by a SpanSpec gets its
-defaults from its starting column.”
-</PARA>
-<PARA><EMPHASIS>Align</EMPHASIS> controls the horizontal position
-of text within the column.
-The value of Align may be Left (quad flush left),
-Center (centered), Right (quad flush right),
-Justify (both quad left and right), or Char (align on
-leftmost of Char, positioned by Charoff). There is
-no default; the value may be inherited from
-ColSpec or SpanSpec.
-</PARA>
-<PARA><EMPHASIS>Char</EMPHASIS> contributes to Align. If the
-value of Align is “char”, the value of Char
-should be a character on the first occurrance
-of which the entry is to be aligned. If that
-character does not occur in the entry, the entry
-is aligned to the left (the original doc incorrectly
-specifies “right”)
-of the position determined
-by Charoff.
-The default is inherited; no value implies there
-is no character to align on.
-</PARA>
-<PARA><EMPHASIS>Charoff</EMPHASIS> contributes with Char to Align.
-Charoff is the proportion
-of the current column width, expressed in percentage,
-to be allowed before the left edge of the first occurrence
-of the character given as the value of Char, if any.
-The default is inherited from ColSpec or SpanSpec.
-</PARA>
-<PARA><EMPHASIS>Colname</EMPHASIS> gives the name of the column,
-which is used
-to specify the position in a row, or the start or end of a
-horizontal span of columns (SpanSpec). There is no default;
-omit if SpanName is present. The implied value is either
-the first column of the Row, or, if already in a Row,
-the next column after the end of the prior Entry or
-EntryTbl.
-</PARA>
-<PARA><EMPHASIS>Colsep</EMPHASIS> determines column separators.
-If its value
-is Yes, display the internal column rulings to
-the right of each Entry; if No, do not
-display it. It is ignored for the last column, where the
-Frame setting applies. (In CALS,
-Yes is expressed as 1 and No as 0.)
-There is no default; if no value is given the
-value is inherited from ColSpec or SpanSpec.
-</PARA>
-<PARA><EMPHASIS>Morerows</EMPHASIS> is the number of
-additional rows in a
-vertical straddle. The default is 0.
-</PARA>
-<PARA><EMPHASIS>Nameend</EMPHASIS> is the name of the rightmost
-column of a span. Names are identified in the
-ColSpec of the current TGroup. There is no default.
-</PARA>
-<PARA><EMPHASIS>Namest</EMPHASIS> or Name Start,
-is the name of the leftmost column
-of a span. Names are identified in the
-ColSpec of the current TGroup.
-</PARA>
-<PARA><EMPHASIS>Rotate</EMPHASIS>
-governs rotations, which are not additive to
-those specified in the FOSI.
-Values may be Yes or No (1 or 0).
-No specifies no rotation; Yes specifies
-90 degrees rotation counterclockwise
-to table orientation. No other values are
-supported!
-</PARA>
-<PARA><EMPHASIS>Rowsep</EMPHASIS>
-determines row separators. If its content is
-Yes, display the internal vertical row ruling
-below each item; if No, do not display it. It is
-ignored for the last row of the table, where
-the frame value applies. There is no default.
-The value is inherited from Row, if used there.
-</PARA>
-<PARA><EMPHASIS>Spanname</EMPHASIS> is the name of a horizontal span.
-No default.
-</PARA>
-<PARA><EMPHASIS>VAlign</EMPHASIS> governs the vertical
-positioning of text within an Entry.
-Allowed values are Top, Middle, and Bottom
-(no default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>EntryTbl</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A form of subtable. It
-may occur in Row, along with Entry.
-Several EntryTbls of differing formats
-may occur in the same Row of a
-TBody, but EntryTbl may not contain itself. Aside
-from that restriction, EntryTbl contains one or
-more sets of these elements, in order:
-any number of ColSpecs, any number of SpanSpecs,
-an optional THead, and a required TBody.
-There is no implication
-of alignment of subrows in different EntryTbls.
-Default attribute values come instead from those
-of like-named attributes on enclosing
-elements: Table, TGroup,
-ColSpec, SpanSpec, THead, TFoot, TBody, or
-Row. EntryTbl has common, Align,
-Char, Charoff, ColName, Cols, Colsep, Nameend, Namest,
-Rowsep, Spanname, and TGroupStyle attributes.
-</PARA>
-<PARA><EMPHASIS>Align</EMPHASIS> controls the horizontal position
-of text within the column.
-The value of Align may be Left (quad flush left),
-Center (centered), Right (quad flush right),
-Justify (both quad left and right), or Char (align to
-the
-left of Char, positioned by Charoff). There is
-no default; the value may be inherited from ColSpec
-or SpanSpec.
-</PARA>
-<PARA><EMPHASIS>Char</EMPHASIS> contributes to Align. If the
-value of Align is “char”, the value of Char
-should be a character on the first occurrance
-of which the entry is to be aligned. If that
-character does not occur in the entry, the entry
-is aligned to the left (the original doc incorrectly
-specifies “right”) of the position determined
-by Charoff. There is no default.
-</PARA>
-<PARA><EMPHASIS>Charoff</EMPHASIS> contributes with Char to Align.
-Charoff is the proportion
-of the current column width, expressed in percentage,
-to be allowed before the left edge of the first occurrence
-of the character given as the value of Char, if any.
-The default is inherited from the enclosing TGroup.
-</PARA>
-<PARA><EMPHASIS>Colname</EMPHASIS> gives the name of the
-leftmost column of EntryTbl. There is no default.
-</PARA>
-<PARA><EMPHASIS>Cols</EMPHASIS> is the number of columns in the
-EntryTbl. There is no default.
-</PARA>
-<PARA><EMPHASIS>Colsep</EMPHASIS>
-determines column separators. If its value
-is Yes, display the internal column rulings to
-the right of the EntryTbl,
-except if the EntryTbl falls in the the last column, where the siderule (<EMPHASIS>sic</EMPHASIS>)
-setting applies; if No, do not display it.
-There is no default. The
-value is inherited from the enclosing TGroup.
-</PARA>
-<PARA><EMPHASIS>Nameend</EMPHASIS> is the name of the rightmost
-column of a span. Names are identified in the
-ColSpec of the current TGroup. There is no default.
-</PARA>
-<PARA><EMPHASIS>Namest</EMPHASIS> or Name Start,
-is the name of the leftmost column
-of a span. Names are identified in the
-ColSpec of the current TGroup. There is no default.
-</PARA>
-<PARA><EMPHASIS>Rowsep</EMPHASIS>
-determines row separators. If its content is
-Yes, display the internal vertical row ruling
-below the EntryTbl; if No, do not display it. It is
-ignored for the last row of the table, where
-the frame value applies. There is no default.
-The value is inherited from the enclosing
-TGroup.
-</PARA>
-<PARA><EMPHASIS>Spanname</EMPHASIS> is the name of a horizontal span.
-</PARA>
-<PARA><EMPHASIS>TGroupStyle</EMPHASIS> is the name of
-a table group style
-defined in the FOSI. There is no default.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Epigraph</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A brief section of poetry or prose
-at the start of a chapter. It contains paragraphs and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Equation</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A titled mathematical equation displayed
-on a line by itself, rather than in-line. It has an optional
-Title and TitleAbbrev, followed by either
-an InformalEquation or a Graphic (see <EMPHASIS>Graphic</EMPHASIS>).
-Equation has common and Label attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ErrorName</TERM>
-<LISTITEM>
-<PARA>An error message reported by a computer.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ErrorType</TERM>
-<LISTITEM>
-<PARA>A classification of an error message
-reported by a computer.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>EventStructure</TERM>
-<LISTITEM>
-<PARA>The code that defines an Event.
-It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>EventType</TERM>
-<LISTITEM>
-<PARA>A classification of an event.
-It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Example</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Intended for sections of program source code
-that are provided as examples in the text.
-It contains a required Title and an
-optional TitleAbbrev, followed by one or more block-oriented
-elements in any combination. It has common and Label
-attributes. A simple Example might contain a Title
-and a ProgramListing.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ExternalLink</TERM>
-<LISTITEM>
-<PARA> Dropped.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Fax</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Figure</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An illustration.
-It must have a Title, and may have a
-TitleAbbrev, followed by one or more of
-BlockQuote,
-InformalEquation, Graphic,
-InformalTable, Link, LiteralLayout,
-OLink, ProgramListing, Screen, Synopsis, and ULink,
-in any order. Figure has common,
-Label, and Float attributes; Float indicates
-whether the Figure is supposed to be rendered
-where convenient (yes) or at
-the place it occurs in the text (no, the default). To
-reference an external file containing graphical
-content use the Graphic element within Figure.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Filename</TERM>
-<LISTITEM>
-<PARA> The
-name of a file, including pathname if this
-information is present. It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>FirstName</TERM>
-<LISTITEM>
-<PARA> (Western-style) given name
-of Author,
-Editor, or OtherCredit. It contains
-plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>FirstTerm</TERM>
-<LISTITEM>
-<PARA>First occurrence
-of a word in a given context.
-It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Font</TERM>
-<LISTITEM>
-<PARA>A collection of Glyphs (see <EMPHASIS>Glyph</EMPHASIS>).
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Footnote</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The contents of a footnote, when
-the note occurs outside the block-oriented element in
-which the FootnoteRef occurs.
-(Compare <EMPHASIS>InlineNote.</EMPHASIS>)
-The point in the text where the mark for a specific
-footnote goes is indicated by FootnoteRef.
-Footnote may contain Para, SimPara, BlockQuote, InformalEquation, InformalTable,
-Graphic, Synopsis, LiteralLayout, ProgramListing,
-Screen, and any kind of list.
-It has ID, Label, Lang, Remap, Role, and XRefLabel
-attributes; the ID attribute is required, as
-a FootnoteRef must point to it.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>FootnoteRef</TERM>
-<LISTITEM>
-<PARA>Identifies the location for a footnote mark.
-It may contain plain text, which is the mark to be displayed, or it may be empty, in which case the Mark
-attribute provides
-another way of indicating the contents of the mark (such as an asterisk,~*, a number, 84, or a dingbat specified by
-a name that is to be interpreted by the application).
-FootnoteRef has ID, Linkend, and Mark
-attributes. The Linkend attribute,
-which is required, has as its value the ID of
-the associated Footnote, and the Mark.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ForeignPhrase</TERM>
-<LISTITEM>
-<PARA>Any word or words
-from a language other than
-that of the document which you want to mark off
-in some way. In English, <EMPHASIS>inter alia</EMPHASIS> and
-<EMPHASIS>c'est la vie</EMPHASIS> are ForeignPhrases.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>FormalPara</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A paragraph with a Title.
-FormalPara contains a required Title followed
-by a required Para, and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>FuncDef</TERM>
-<LISTITEM>
-<PARA> Part of a FuncSynopsis.
-Like Paramdef, it provides
-data type information and the name of the
-Function (or Parameter, in the case of ParamDef)
-this information applies
-to. A FuncDef may contain any combination of
-plain text, Replaceable, Data, or Function, in any order.
-It has common attributes.
-</PARA>
-<PARA>Separating this information from the rest of
-the synopsis avoids messing with data type
-information that appears before <EMPHASIS>or after</EMPHASIS>
-the item it applies to, such as array
-information (“[]”). It also avoids the issue of
-placing the pointer (“*”) indicator (next to the rest of
-the left-hand data type or next to the Parameter or Function
-name?). Any spaces that surround the
-Parameter or Function must be inserted by the writer.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>FuncParams</TERM>
-<LISTITEM>
-<PARA>Optional component of ParamDef.
-It supplies “inner parameters” for Paramters that
-are pointers to Functions. FuncParams
- contains elements from ctprphrase.gp and has
-common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>FuncSynopsis</TERM>
-<LISTITEM>
-<PARA>(contributed Eve Maler, along
-with remarks on its subelements.)
-A C synopsis that shows a prototype or
-definition indicating a function's name. A FuncSynopsis
-also indicates the data type of its return value, and
-the positions, purposes, and data types of its
-parameters. A FuncSynopsis begins with an
-optional FuncSynopsisInfo, which contains additional
-information about the synopsis that follows; line breaks
-and leading white space are significant within a
-FuncSynopsisInfo. This is followed by
-one or more blocks defining a function (you might
-use more than one for connecting related sets of functions).
-Each of these blocks consists of a required FuncDef,
-followed by a Void, a VarArgs, or one or more ParamDefs.
-Void, Varargs, and and ParamDef
-are mutually exclusive. <EMPHASIS>Usage Note:</EMPHASIS>
-You should supply no specific information on the arguments before the ellipsis that VarArgs should output when
-rendered, but if it is necessary
-to represent the ellipsis in the source it may
-ben enclosed within a final ParamDef.
-FuncSynopsis has common and Label attributes.
-</PARA>
-<PARA>The processing application is expected to
-provide all parentheses, semicolons, and the like. The
-exceptions are any spaces surrounding function and parameter
-names, any parentheses or commas or spacing
-inside lists of data types of parameters that are pointers
-to functions, and the parentheses around those parameter
-names themselves. These exceptions are a bit confusing in
-the unusual case (pointers to functions), but they
-<EMPHASIS>greatly</EMPHASIS> simplify tagging and still
-allow either K&R style or ANSI C style to be produced
-(assuming writers have cooperated in supplying enough
-information for ANSI).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>FuncSynopsisInfo</TERM>
-<LISTITEM>
-<PARA>Information supplementing
-the FuncDefs of a FuncSynopsis. It contains elements
-of ctprphrase.gp, and within it line breaks
-and leading white space are significant.
-See <EMPHASIS>FuncSynopsis.</EMPHASIS> It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Function</TERM>
-<LISTITEM>
-<PARA> A subroutine in a program or external
-library. It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>FunctionParam</TERM>
-<LISTITEM>
-<PARA>Dropped.
-See <EMPHASIS>Parameter.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Glossary</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A glossary of terms. Glossary
-may occur within a Chapter, Appendix, or Preface,
-or may be a book component in its own right.
-It contains in order an optional DocInfo, optional
-Title, and optional TitleAbbrev, followed by
-any number of
-block-oriented elements, followed by
-one or more GlossEntries or one or more GlossDivs.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>GlossDef</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The definition attached to a GlossTerm
-in a GlossEntry. It may
-contain Comments, GlossSeeAlsos,
-paragraphs, and other block-oriented
-elements, in
-any order; it has common and Subject attributes. The Subject
-attribute may hold a list of subject areas (e.g., DCE RPC
-General) as keywords.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>GlossDiv</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A division of a Glossary.
-It may have a Title and TitleAbbrev, followed by
-block-oriented elements, followed by
-one or more GlossEntries. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>GlossEntry</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An entry in a Glossary.
-It contains, in order, a required
-GlossTerm, an optional Acronym,
-an optional Abbrev, and any number of
-GlossSees and GlossDefs, in any order.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>GlossSee</TERM>
-<LISTITEM>
-<PARA>A cross-reference from one
-GlossEntry to another. It may contain plain
-text or no content, and has common and OtherTerm
-attributes. OtherTerm is a reference to the
-GlossTerm within the cross-referenced GlossEntry; that
-GlossTerm should be displayed at the point of the GlossSee.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>GlossSeeAlso</TERM>
-<LISTITEM>
-<PARA>A cross-reference from one
-GlossDef to another GlossEntry. It may contain plain
-text or no content, and has common and OtherTerm
-attributes. OtherTerm is a reference to the
-GlossTerm within the cross-referenced GlossEntry; that
-GlossTerm should be displayed at the point of the GlossSee.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>GlossTerm</TERM>
-<LISTITEM>
-<PARA>A term in the
-text of a Chapter (for example) that is glossed in a Glossary; also used for those terms in GlossEntries, in the
-Glossary itself. As you may not want to tag all occurrences
-of these words outside of Glossaries, you might consider
-GlossTerm, when used outside of Glossaries, to be similar
-to FirstTerm, except that GlossTerm may contain other
-in-line elements. GlossTerm contains in-line elements
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Glyph</TERM>
-<LISTITEM>
-<PARA>A mark, a component of a font. A character
-or ligature might be made up of one, two, or more Glyphs.
-<EMPHASIS>Cf.</EMPHASIS> Character.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Graphic</TERM>
-<LISTITEM>
-<PARA>Encloses graphical data or
-points via an attribute to an external file containing such data,
-and is to be rendered as an object, not in-line.
-It has Format,
-Fileref, Entityref, and ID attributes.
-The format attribute may have the value of
-any of the formats defined at the head of the DTD,
-including CGM-CHAR, CGM-CLEAR, DITROFF, DVI, EPS,
-EQN, FAX, FAXTILE, GIF, IGES, PIC, PS, TBL, TEX,
-TIFF.
-</PARA>
-<PARA>The value of
-Fileref should be a filename, qualified by a pathname
-if desired; the value of Entityref should be that of an
-external data entity. If data is given as the
-content of Graphic, both Entityref and Fileref,
-if present at all, should
-be ignored, but a Format value should be supplied.
-if no data is given as the content of
-Graphic and a value for Entityref
-is given, Fileref, if present, should be ignored
-but no Format value should be supplied.
-Finally, if there is no content for Graphic and
-Entityref is absent or null, Fileref must be
-given the appropriate value, and again no
-Format value should be supplied.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Group</TERM>
-<LISTITEM>
-<PARA>A group of constituent parts of a
-CmdSynopsis. A Group consists of one or more Args, Groups,
-SynopFragmentrefs,
-and Replaceables, in any order. See <EMPHASIS>CmdSynopsis.</EMPHASIS>
-Group has common, grpchcatt, and repatt attributes.
-</PARA>
-<PARA><EMPHASIS>argchcatt</EMPHASIS> or “argument choice attribute”
-resolves to the attribute
-Choice, with allowed values Opt (the Arg is
-optional; the default), Req (it is required), and Plain (neither
-optional nor required).
-</PARA>
-<PARA><EMPHASIS>repatt</EMPHASIS> or “repetition attribute”
-resolves to the attribute Rep, with allowed
-values Norepeat (the Arg may be repeated; the default)
-and Repeat (the Arg does not repeat).
-</PARA>
-<PARA><EMPHASIS>grpchcatt</EMPHASIS> or “group choice attribute”
-is a parameter entity that
-resolves to the the Choice attribute for the element Group.
-The allowed values are Opt (the Arg is
-optional; the
-default), Req (it is required), Plain (neither
-optional nor required), OptMult (optional and
-repeatable), and ReqMult (required
-multiple times).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Hardware</TERM>
-<LISTITEM>
-<PARA> A physical part of a computer system.
-It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Highlights</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A list of main points discussed
-in a book component such as a Chapter. It may contain
-paragraphs,
-lists, and admonitions, and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Holder</TERM>
-<LISTITEM>
-<PARA>Part of Copyright; the
-holder of the copyright of the document. It contains
-plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Honorific</TERM>
-<LISTITEM>
-<PARA>A person's title, to be used as part of
-Author, Editor, or OtherCredit. It contains
-plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>HWapplic</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Icon</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Interface.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Important</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An admonition set off from the text.
-See <EMPHASIS>Caution.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Index</EMPHASIS></TERM>
-<LISTITEM>
-<PARA> An index to a Chapter,
-Appendix, Preface, or Book.
-It contains an optional DocInfo, Title, and TitleAbbrev,
-followed by
-any number of block-oriented elements,
-and then one or more IndexEntries or one or more IndexDivs.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>IndexAs</TERM>
-<LISTITEM>
-<PARA>Dropped.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>IndexDiv</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A division of an Index.
-It may have a Title and TitleAbbrev,
-some optional introductory matter (block-oriented elements,
-Anchors, Comments), and must then
-contain one or more IndexEntries or a SegmentedList (use
-a SegmentedList for a permuted index).
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>IndexEntry</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Part of Index. It contains a
-PrimaryIE, which may be accompanied by SecondaryIE,
-TertiaryIE, SeeIE, and SeeAlsoIE. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>IndexTerm</TERM>
-<LISTITEM>
-<PARA>A character string to be indexed,
-occurring in the text flow but not in the text itself.
-(And remember, IndexTerm appears in the text,
-not in the Index!)
-Primary, Secondary, and Tertiary
-index items are nested within this tag, as are See and
-SeeAlso items. It has common, SpanEnd, PageNum, and
-Significance attributes.
-The SpanEnd attribute may not be used if IndexTerm
-has content; it should be used only
-to mark the end of a span
-of text that begins earlier
-at an IndexTerm that does have
-content.
-The value of SpanEnd must be the
-ID of that earlier IndexTerm.
-The PageNum attribute may be used to
-indicate the page on which the indexed term is found in print. Significance
-may have the value Preferred, indicating that the
-entry is the most pertinent of the series, or Normal (the
-default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>InformalEquation</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An untitled mathematical equation
-displayed on a line by itself, rather than in-line.
-It contains a Graphic, and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>InformalTable</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>
-An array of text that has no Title.
-Otherwise, it is just like Table except that it lacks the
-ShortEntry and ToCEntry attributes. See <EMPHASIS>Table.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>InlineEquation</TERM>
-<LISTITEM>
-<PARA>An untitled mathematical equation
-occurring in-line or as the content of an Equation.
-It contains a Graphic, and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>InlineFootnote</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The contents of a footnote, when
-the note occurs within the block-oriented element in
-which the FootnoteRef occurs.
-(Compare <EMPHASIS>Footnote.</EMPHASIS>)
-The point in the text where the mark for a specific
-footnote goes is indicated by FootnoteRef.
-InlineFootnote, like Footnote,
- may contain paragraphs, BlockQuote, InformalEquation, InformalTable,
-Graphic, Synopsis, LiteralLayout, ProgramListing,
-Screen, and any kind of list.
-It has ID, Label, Lang, Remap, Role, and XRefLabel
-attributes; the ID attribute is required, as
-a FootnoteRef must point to it.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>InlineGraphic</TERM>
-<LISTITEM>
-<PARA>Encloses graphical data or
-points via an attribute to an external file containing such data,
-and is to be rendered in-line.
-InlineGraphic has Format, Fileref, Entityref, and
-ID attributes.
-The format attribute may have the value of
-any of the formats defined at the head of the DTD,
-under “Notations.”
-If it is desired to point to an external file, a filename may
-be supplied as the value of the Fileref attribute, or an
-external entity name may be supplied as the value of the
-Entityref attribute.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>InlineNote</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The contents of a footnote, when
-the note occurs within the block-oriented element in
-which the FootnoteRef occurs. For usage and
-attributes see <EMPHASIS>Footnote.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Interface</TERM>
-<LISTITEM>
-<PARA>Any part of a graphical user
-interface.
-It may contain members of cptrphrase.gp,
-and has common, Class, and MoreInfo attributes.
-Class may have the value Button, Icon, Menu, or MenuItem
-(no default). For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>InterfaceDefinition</TERM>
-<LISTITEM>
-<PARA>A specification for a graphical user
-interface. It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>InvPartNumber</TERM>
-<LISTITEM>
-<PARA>An inventory part number. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ISBN</TERM>
-<LISTITEM>
-<PARA>International
-Standard Book Number of a document. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ISSN</TERM>
-<LISTITEM>
-<PARA>International
-Standard Serial Number of a journal. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>IssueNum</TERM>
-<LISTITEM>
-<PARA>The number of an issue of a journal.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ItemizedList</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A list in which each item is marked with
-a bullet, dash, or other dingbat (or no mark at all).
-It consists of one or more ListItems. A ListItem in an
-ItemizedList contains paragraphs and other
-block-oriented elements, which
-may in turn contain other lists; an ItemizedList may be
-nested within other lists, too.
-It has common attributes and
-a Mark attribute. Your application might supply the mark to be used
-for an ItemizedList, but you can use this attribute to
-indicate the mark you desire to be used; there
-is no fixed list of these.
-<EMPHASIS>Usage Note:</EMPHASIS>
-You might want to use one of the ISO text entities
-that designates an appropriate dingbat.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>JobTitle</TERM>
-<LISTITEM>
-<PARA>Part of Affiliation. It contains
-plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>JournalInfo</TERM>
-<LISTITEM>
-<PARA>Information about the journal in
-which an Article appears, in that Article's ArtHeader.
-It contains, in order, a required Title, optional
-TitleAbbrev, Subtitle, ISSN, VolumeNum, IssueNum,
-PageNums, PubDate, Publisher, and Copyright.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>KeyCap</TERM>
-<LISTITEM>
-<PARA>The text printed on a physical key on a
-computer keyboard, not necessarily the same thing as a
-KeyCode. It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Keycode</TERM>
-<LISTITEM>
-<PARA>The computer's numeric designation of a key on
-a computer keyboard. Keycode contains plain text and has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Keysym</TERM>
-<LISTITEM>
-<PARA>A key symbol name, which is not
-necessarily the same thing
-as a Keycap. For example, the Keysym for
-the H key (Keycap H) might be <EMPHASIS>h.</EMPHASIS>
-It contains plain text, and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>LegalNotice</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An
-acknowledgement of trademarks, etc. It
-may have a Title, followed by paragraphs,
-and BlockQuotes in any order.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Lineage</TERM>
-<LISTITEM>
-<PARA>Part of an author's name, such
-as “Jr.” It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>LineAnnotation</TERM>
-<LISTITEM>
-<PARA>A writer's or editor's comment on
-a line of program code within an Example, ProgramListing,
-or Screen. LineAnnotations are a document author's
-comments on the code, not the comments written
-into the code itself by the code's author.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Link</TERM>
-<LISTITEM>
-<PARA>A hypertext link. At present, all
-the link types represented in the DTD are
-provisional. Link is less provisional than the
-others, however. In HyTime parlance, Link is a
-clink. It may contain in-line elements
-and has Endterm, Linkend, and Type attributes. The required
-Linkend attribute specifies the target of the link,
-and the optional Endterm attribute specifies
-text that is to be fetched from elsewhere in the document
-to appear in the Link. You can also supply this text directly as
-the content of the Link, <EMPHASIS>in which case the
-Endterm attribute is to be ignored (new and tentative
-rule for this version, comments invited)</EMPHASIS>.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ListItem</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A wrapper for the elements of
-items in an ItemizedList or OrderedList; it also
-occurs within VarListEntry in VariableList.
-It may contain just about anything except Sects and book
-components.
-It has common attributes and an Override attribute, which
-may have any of the values of ItemizedList's
-Mark attribute; use Override to override the mark
-set at the ItemizedList level, when you desire to create
-ItemizedLists with varying marks.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Literal</TERM>
-<LISTITEM>
-<PARA>Any literal string, used in-line, that is part of
-data in a computer. This may be as precise as
-the value of an argument, but Literal may also be used
-as a catch-all element.
-It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>LiteralLayout</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The wrapper for lines set off from
-the main text that are not tagged as Screens, Examples,
-or ProgramListing, in which line breaks and leading
-white space are to be regarded as significant.
-It contains in-line elements, and has common
-and Width attributes, for
-specifying a number representing the maximum width of
-the contents.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>LoT</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The generic tag for such things as a List
-of Figures or List of Tables. An LoT may occur within a Chapter, or Appendix, or may be a book
-component on its own.
-It contains, in order, an optional DocInfo, Title, and TitleAbbrev,
-followed by one or more LoTentries. It has
-common and Label attributes; in this case the values of
-Label may be Equation, Examples, Figures, or Tables,
-with no default.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>LoTentry</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An element of LoT. It contains
-the text of the thing to be listed,
-including, if desired, in-line elements. It has
-common and PageNum attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Macro</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>SystemItem.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ManVolNum</TERM>
-<LISTITEM>
-<PARA>Specific to UNIX man pages, it
-designates the section of a complete set of
-reference pages that a reference page belongs to. It appears
-within RefMeta, contains plain text, and has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Markup</TERM>
-<LISTITEM>
-<PARA>A string of formatting markup in text,
-which it is desired to represent literally. See also
-<EMPHASIS>SGMLTag.</EMPHASIS>
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Mask</TERM>
-<LISTITEM>
-<PARA>Values in a specified structure that should
-be read when updating resource values.
-Mask contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>MediaLabel</TERM>
-<LISTITEM>
-<PARA>The physical medium on or in which
-some information is contained.
-MediaLabel may contain plain text,
-and has common, Class, and MoreInfo attributes.
-Class may have the value Cartridge, CDRom, Disk, or Tape
-(no default). For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Member</TERM>
-<LISTITEM>
-<PARA>Part of a SimpleList. It contains
-in-line elements and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Menu</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Interface.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>MenuItem</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Interface.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ModeSpec</TERM>
-<LISTITEM>
-<PARA>Contains application-specific
-information necessary for
-the completion of an OLink; see <EMPHASIS>
-OLink.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Msg</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The part of a MsgEntry that contains
-the error message and its subparts, along with
-explanatory text. A Msg has a required MsgMain,
-followed by any number of MsgSubs and MsgRels, in any
-order. It has common and Label attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>MsgAud</TERM>
-<LISTITEM>
-<PARA>Describes the audience
-to which a Msg is
-relevant. It contains plain text only, and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>MsgEntry</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A wrapper for an entry in a MsgSet.
-A MsgEntry
-must contain one or more Msgs, followed by an optional
-MsgInfo, then any number of MsgExplans.
-MsgEntry has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>MsgExplan</TERM>
-<LISTITEM>
-<PARA> Holder for any kind of explanatory
-material relating to the
-Msg. MsgExplan begins with an optional Title
-(typically something such as
-“Explanation:” or “Action:”)
-and may contain block-oriented elements.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>MsgInfo</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Information about the Msg
-containing it. It may have any number of MsgLevels,
-MsgOrigs, and MsgAuds, in any order, and has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>MsgLevel</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The level of importance or severity
-of a Msg. It contains only plain text, and has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>MsgMain</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The main error message of a
-Msg. MsgMain begins with an optional Title and contains
-MsgText, which is the text of the message. It
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>MsgOrig</TERM>
-<LISTITEM>
-<PARA>The origin of a Msg.
-It contains only plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>MsgRel</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An optional subpart of a Msg, containing
-a message that is related to the main message
-(MsgMain) but which appears in a
-different place. For example, MsgMain
-might be a message that appears on a
-network client, and MsgRel a related message
-that appears at the
-server console in response to the same condition or event.
-MsgRel begins with an optional Title and contains
-MsgText. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>MsgSet</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A list of error messages produced
-by a system, with various additional information.
-MsgSet contains one or more MsgEntries, and has
-common attributes.
-<EMPHASIS>Usage Note:</EMPHASIS>
-The entire Msg* construction is new and complicated;
-it may be simplified in the future.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>MsgSub</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An optional subpart of a Msg, which
-might contain messages that appear in various contexts. It
-contains a an optional Title followed by
-MsgText. MsgSub has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>MsgText</TERM>
-<LISTITEM>
-<PARA>Contents of the parts of Msg.
-It may contain block-oriented elements,
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Note</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A message to the user, set off from the text.
-See <EMPHASIS>Caution.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>OLink</TERM>
-<LISTITEM>
-<PARA>A link that may perform some operation to
-find its target. In contrast to Link, OLink has no
-Linkend attribute, but rather a TargetDocEnt, the value of
-which is the name of a text or data entity already
-defined by the user. The LinkMode attribute points by
-ID to a ModeSpec; for convenience, ModeSpecs
-located in the BookInfo. ModeSpec contains
-instructions (probably application-specific) for operating
-on the entity named by TargetDocEnt, <EMPHASIS>e.g.,</EMPHASIS> the
-TargetDocEnt is another Book, and the ModeSpec specifies
-that all the second-level headings should be searched
-for a phrase. The LocalInfo attribute may be used to
-hold such a phrase, which may be thought of as a
-replacement for some variable in ModeSpec. Finally,
-OLink has a Type attribute, also.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Option</TERM>
-<LISTITEM>
-<PARA>An option for a computer program command.
-It may have members of cptrphrase.gp, and has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Optional</TERM>
-<LISTITEM>
-<PARA>For use in Synopsis, as in a
-RefEntry, where optional parameters
-conventionally are shown in square
-brackets. Optional should replace those brackets. It may contain
-elements from cptrphrase.gp, and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>OrderedList</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A numbered or lettered list, consisting of
-ListItems. A ListItem in an
-OrderedList contains paragraphs and other
-block-oriented elements, which
-may in turn contain other lists; an OrderedList may be
-nested within other lists, too.
-OrderedList has common attributes, along with
-a Numeration attribute, which
-may have the value Arabic, Upperalpha, Loweralpha,
-Upperroman, or Lowerroman. If no value is supplied,
-the processing expectation should be that Arabic
-numbering (1, 2, 3, . . .) is to be used.
-It has an InheritNum attribute, for which the
-value Inherit specifies for a
-nested list that the numbering of ListItems should include the
-number of the item within which they are nested (2a, 2b, etc.,
-rather than a, b, etc.); the default value is Ignore.
-It has a Continuation attribute, with values
-Continues or Restarts (the default),
-which may be used to
-indicate whether the numbering of a list begins afresh (default)
-or continues that of the immediately preceding list (Continues).
-You need supply the Continuation attribute only
-if your list continues the numbering of the preceding list.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>OrgName</TERM>
-<LISTITEM>
-<PARA>An organization that is not
-a corporation (<EMPHASIS>cf.</EMPHASIS> CorpName)
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>OrgDiv</TERM>
-<LISTITEM>
-<PARA>Part of an organization.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>OSname</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>SystemItem.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>OtherCredit</TERM>
-<LISTITEM>
-<PARA>Supplements
-Author and Editor; you could use it to credit a contributor,
-a contributing editor, or some deserving production person.
-Contents are as for <EMPHASIS>Author.</EMPHASIS> It has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>OtherName</TERM>
-<LISTITEM>
-<PARA>An alternative to Firstname and
-Surname, for use in Author, Editor, or OtherCredit.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>PageNums</TERM>
-<LISTITEM>
-<PARA>The numbers of the pages contained
-in a Book, for use in its BookBiblio.
-It contains plain text (e.g., ix, 292).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Para</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A paragraph. A Para may not
-have a Title: to attach a Title to a Para use
-FormalPara. Para
-may contain any in-line element and almost
-any block-oriented element. Abstract, AuthorBlurb, Caution,
-Important, Note, and
-Warning are excluded, as are Sects and higher-level
-elements. Para has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Paragraphs</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>See <EMPHASIS>Para.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ParamDef</TERM>
-<LISTITEM>
-<PARA> Part of a FuncSynopsis, providing
-data type information and the name of the
-Parameter this information applies
-to. A ParamDef may contain any combination of
-plain text, Replaceable, Data, or Parameter, in any order.
-It has common attributes. See <EMPHASIS>FuncDef,</EMPHASIS> <EMPHASIS>
-FuncSynopsis.</EMPHASIS> It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Parameter</TERM>
-<LISTITEM>
-<PARA>Part of an instruction to a computer.
-It may contain members of cptrphrase.gp,
-and has common, Class, and MoreInfo attributes.
-Class may have the value Command, Function, or Option
-(no default). For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Part</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A section of a Book containing
-book components.
-Part contains an optional DocInfo, a required Title, an optional TitleAbbrev,
-an optional PartIntro,
-followed by one or more book components.
-It has common and Label attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>PartIntro</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Introduction to the contents
-of a Part;
-may also appear in
-Reference. It has optional Title and TitleAbbrev,
-and then may contain anything that can appear in a Chapter.
-PartIntro has common and Label attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Phone</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>POB</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Postcode</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Preface</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Any introductory matter in a Book.
-Preface may occur more than once in Book, before
-any Chapter, Part, or Reference: for example,
-you might have two Prefaces, one titled “Preface”
-and the other “Introduction.”
-Preface may begin with a DocInfo, followed by
-a required Title, optional TitleAbbrev, and anything
-found in the body of a Chapter.
-Preface has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Primary</TERM>
-<LISTITEM>
-<PARA>A word or phrase occurring in
-the text that is to
-appear in the index under as a primary entry. It must be
-nested within IndexTerm tags. Primary may contain in-line
-elements. It has SortAs and common attributes.
-SortAs can be used to provide
-an alternate string for alphabetizing the index: if Primary
-has the content “14”
-one might give Primary the attribute
-Sortas=“fourteen”.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>PrimaryIE</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A primary entry in an Index, not in the
-text. It may contain only plain text. It has common
-attributes and a Linkends attribute, which has the
-value of some list of element IDs.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>PrintHistory</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The printing history of
-a Book. It contains paragraphs.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Procedure</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A list of operations to
-be performed. Procedure may have a Title and
-TitleAbbrev, followed by block-oriented elements,
-such as paragraphs, followed by one or more Steps.
-A Step may have a SubSteps wrapper for Steps nested
-within it, and this nesting may continue indefinitely
-(contrast the methods of nesting lists and Sects).
-This construction is intended to maximize the reusability
-of subsections of Procedures.
-Procedure has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ProductName</TERM>
-<LISTITEM>
-<PARA>Formal name for any product.
-It contains in-line elements, and has common and
-Class attributes. The Class attribute may have the
-values Service, Trade (the default), Registered, Copyright,
-or Logo. Thus a trademark is a Productname with the
-default Class attribute value.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ProductNumber</TERM>
-<LISTITEM>
-<PARA>A number assigned to a product.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ProgramListing</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A listing of a program.
-Line breaks and leading
-white space are significant in a ProgramListing, which
-may contain in-line elements, including LineAnnotations.
-(LineAnnotations are a document author's
-comments on the code, not the comments written
-into the code itself by the code's author.)
-ProgramListing has common and Width attributes, the
-latter for specifying a number representing the maximum
-width of the contents.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Prompt</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>SystemItem.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Property</TERM>
-<LISTITEM>
-<PARA>A defined set of data
-associated with a window. It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ProtocolRequest</TERM>
-<LISTITEM>
-<PARA>Message sent from a program to a
-server. It may contain members of cptrphrase.gp,
-and has common and MoreInfo attributes.
-For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>PubDate</TERM>
-<LISTITEM>
-<PARA>The date of publication of a document.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Publisher</TERM>
-<LISTITEM>
-<PARA>The publisher of a document. It contains a PublisherName and any number of Addresses.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>PublisherName</TERM>
-<LISTITEM>
-<PARA>The name of a publisher of a document. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>PubsNumber</TERM>
-<LISTITEM>
-<PARA>A number assigned to a publication,
-other than an ISBN or ISSN or InvPartNumber.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Quote</TERM>
-<LISTITEM>
-<PARA>An in-line quotation. For block quotes
-use BlockQuote. Quote may contain members of cptrphrase.gp,
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RefClass</TERM>
-<LISTITEM>
-<PARA>An element of RefNameDiv, in which the
-applicability or scope of the topic of a RefEntry may be
-indicated. It may contain
-plain text or Application.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RefDescriptor</TERM>
-<LISTITEM>
-<PARA>A substitute for RefName to be used
-when a
-RefEntry covers more than one topic and none of the topic names
-is to be used as the sort name. It contains plain
-text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>RefEntry</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A reference page. It contains,
-in order, an optional DocInfo and optional RefMeta;
-any number of Comments and members of links.gp, in any order;
-a required RefNameDiv, an optional RefSynopsisDiv,
-and one or more RefSect1s.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Reference</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A collection of RefEntries,
-formin a book component.
-Reference has an optional DocInfo,
-a required Title,
-an optional TitleAbbrev, an optional PartIntro, and
-one or more RefEntries.
-It has common and Label attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RefEntryTitle</TERM>
-<LISTITEM>
-<PARA>Primary name given to a
-reference page for
-sorting and indexing. It may be the same as the first of
-the RefNames, or it may be the same as the RefDescriptor.
-It may contain in-line elements, and has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RefFileName</TERM>
-<LISTITEM>
-<PARA>Dropped. It is now called
-RefEntryTitle.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>RefMeta</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The first major division of a reference page,
-in which metainformation about the reference page is supplied.
-RefMeta contains, in order, a required RefEntryTitle,
-an optional ManVolNum, and any number of
-RefMiscInfos. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RefMiscInfo</TERM>
-<LISTITEM>
-<PARA>Marks information in
-RefMeta that may be
-supplied by vendors, such as copyright, release date, revision
-date, print status, operating system, hardware architecture,
-or a descriptive phrase for use in a print header.
-It contains plain text, and has common and Class attributes.
-The Class attribute can be used to distinguish categories of
-RefMiscInfos.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RefName</TERM>
-<LISTITEM>
-<PARA>The subject or subjects of a
-reference page. It appears within RefNameDiv.
-It may contain plain text and in-line elements, and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>RefNameDiv</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The second major division of a reference page.
-It contains, in order, an optional RefDescriptor, one or more
-RefNames, a required RefPurpose, and an optional RefClass,
-followed by any number of Comments and links, in any order.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RefPurpose</TERM>
-<LISTITEM>
-<PARA>A short phrase describing the
-subject of
-the reference page. It may contain in-line elements
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>RefSect1</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Equivalent to a Sect1 in the DocBook DTD.
-It contains a Title, followed by any of the allowable contents
-of a Sect, except that only two levels of subsection
-are allowed, RefSect2 and RefSect3. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>RefSect2</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Equivalent to a Sect2 in the DocBook DTD, and may
-occur within RefSect1 or RefSynopsisDiv. It may contain any of the
-allowable contents of a Sect, except that only RefSect3
-is allowed as a further subsections. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>RefSect3</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Subdivision of RefSect2. No further
-subdivisions allowed; contents otherwise as for RefSect2.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>RefSynopsisDiv</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The third major division of a reference page,
-in which the syntax of the subject of the reference page is
-indicated. It contains, in order,
-an optional Title and TitleAbbrev, followed by either one or more
-synopses (Synopsis, CmdSynopsis, or FuncSynopsis) succeeded
-by any number of RefSect2s, or simply one or more RefSect2s.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ReleaseInfo</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Information about a particular version of a
-document. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Replaceable</TERM>
-<LISTITEM>
-<PARA>Part of a synopsis or command line,
-indicating that its contents may be replaced.
-It may contain basic in-line elements (not cptrphrase.gp)
-and has common and Class attributes.
-Class may have the value
-Command, Function, Option, or Parameter
-(no default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Resource</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>SystemItem.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ReturnValue</TERM>
-<LISTITEM>
-<PARA>A value returned by a function.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>RevHistory</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A section of BookInfo or DocInfo
-recording revisions to the document. It
-consists of any number of Revisions, and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Revision</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An entry in RevHistory,
-describing some
-revision made to the text. It contains, in order,
-a required RevNumber, required Date,
-one or more sets of AuthorInitials, and
-a required RevRemark.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RevNumber</TERM>
-<LISTITEM>
-<PARA>The number of a Revision.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>RevRemark</TERM>
-<LISTITEM>
-<PARA>An element
-of Revision, describing the Revision.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Row</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A row in a TBody, THead, or TFoot.
-It contains one or more Entries or
-EntryTbls, in any order.
-It has common, Rowsep, and VAlign attributes.
-</PARA>
-<PARA><EMPHASIS>Rowsep</EMPHASIS> determines Row separators. If its content is
-Yes, display the internal vertical row ruling
-below each Row; if No, do not display it. It is
-ignored for the last Row of the TGroup, THead,
-or TFoot, where
-the frame value applies. There is no default.
-The value is inherited from TGroupStyle, if used.
-</PARA>
-<PARA><EMPHASIS>Valign</EMPHASIS> governs the vertical
-positioning of text within a Row.
-Allowed values are Top, Middle, and Bottom
-(no default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Screen</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Intended to represent what the user sees or
-might see on a computer screen. It
-consists of in-line elements, in which line breaks
-and leading white space are considered
-significant. It has common attributes and a Width
-attribute for specifying a number representing the maximum width of
-the contents.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ScreenInfo</TERM>
-<LISTITEM>
-<PARA>Part of ScreenShot
-(see <EMPHASIS>ScreenShot</EMPHASIS>). A ScreenInfo
-indicates how the Graphic with which it is paired was created,
-as a guide for future revisions. It may contain only plain
-text, and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ScreenShot</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Like Screen,
-intended to represent what the user sees or
-might see on a computer screen. It
-consists of an optional ScreenInfo
-and a required Graphic.
-It has common attributes and a Width
-attribute for specifying a number representing the maximum width of
-the contents.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Secondary</TERM>
-<LISTITEM>
-<PARA>A word or phrase in the text that is to
-appear in the index beneath a Primary entry. It must be
-nested within IndexTerm tags and must follow a Primary element.
-It may contain in-line elements, and has
-SortAs and common attributes. See <EMPHASIS>Primary.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SecondaryIE</TERM>
-<LISTITEM>
-<PARA>Part of IndexEntry,
-like PrimaryIE (see <EMPHASIS>PrimaryIE</EMPHASIS>).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Sect1</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A top-level section of a book component,
-including the Title of that section. Sect2–5 nest
-in order within Sect1. Anything may occur
-within a Sect1 except a DocInfo, Preface,
-Chapter, Appendix, or
-another Sect1, including a Glossary, Bibliography, RefEntry, ToC, Index,
-or LoT. A Sect must have a Title, which is the text
-of the heading itself, and may have a TitleAbbrev; it must
-include some content, whether paragraphs or other block-oriented elements, including
-a Sect2. Sect1–5 have common,
-Label, and Renderas attributes. The Renderas attribute may
-have the value Sect1 through Sect5, and may be used to
-specify that the Sect (particularly its heading) is to be
-presented in the format defined for a Sect of some other level.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Sect2</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A section beginning with a second-level
-heading; must be nested within a Sect1.
-Allowable and required contents
-for Sect2, and its attributes, are like those for Sect1.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Sect3</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>See <EMPHASIS>Sect1, Sect2</EMPHASIS>.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Sect4</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>See <EMPHASIS>Sect1, Sect2</EMPHASIS>.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Sect5</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>See <EMPHASIS>Sect1, Sect2</EMPHASIS>. Sect5 may
-not contain Sects of any level, and
-no further subdivisions are supplied in the DocBook DTD.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>See</TERM>
-<LISTITEM>
-<PARA>Part of IndexTerm, indicating, for
-a word or phrase in the text, the index entry to
-which the reader is to be directed when he consults
-the stub index entry for another element within
-the IndexTerm.
-See must be nested within IndexTerm tags and must
-follow a Primary or Secondary element.
-It may contain in-line
-elements, and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SeeAlso</TERM>
-<LISTITEM>
-<PARA>Like See, but indicates
-the index entries to which the reader is <EMPHASIS>also</EMPHASIS>
-to be directed when he consults a full index entry.
-SeeAlso must be nested within IndexTerm tags and must
-follow a Primary or Secondary element.
-It may contain in-line
-elements, and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SeeAlsoIE</TERM>
-<LISTITEM>
-<PARA>A “see also” entry in an Index, not
-in the text, occurring
-unnested within IndexEntry at the PrimaryIE or
-SecondaryIE level.
-It may contain plain text only. It has common
-attributes and a Linkends attribute, which has the
-value of some list of IndexEntry IDs.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>SeeIE</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A “see” entry in an Index, not in the
-text, occurring
-unnested within IndexEntry at the PrimaryIE or
-SecondaryIE level.
-It may contain plain text only. It has common
-attributes and a Linkend attribute, which has the
-value of some IndexEntry ID.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Seg</TERM>
-<LISTITEM>
-<PARA>A component of a SegmentedList. Segs are the
-only content of a SegmentedList's
-SegListItems. Seg may contain in-line
-elements. It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>SegListItem</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A list item in a SegmentedList.
-It consists
-of two or more Segs, and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>SegmentedList</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A list of sets of units.
-It may be used to represent
-sets of information often presented as simple tables.
-SegmentedList may have a Title and TitleAbbrev, followed by any number
-of SegTitles, and one or more SegListItems.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SegTitle</TERM>
-<LISTITEM>
-<PARA>A title that pertains to one Seg in each
-SegListItem: the first SegTitle to the first Seg, the second SegTitle
-to the second Seg, and so on. It may contain in-line elements.
-SegTitles
-are grouped at the beginning of a SegmentedList, before the SegListItems.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Series</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Dropped.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SeriesInfo</TERM>
-<LISTITEM>
-<PARA>Part of BookInfo or BiblioEntry,
-containing information about the publication series of
-which the book is a part. SeriesInfo contains,
-in order, a
-required Title, optional TitleAbbrev and Subtitle;
-any number of AuthorGroups, optional ISBN,
-VolumeNum, and IssueNum; a required SeriesVolNums,
-any number of PubDates and Publishers, and finally
-an optional Copyright.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SeriesVolNums</TERM>
-<LISTITEM>
-<PARA>The numbers of all the volumes
-in a Series, for use in SeriesInfo. It contains plain text
-(e.g., 1-5).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Set</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Two or more Books. Set may have,
-in order, a
-Title, TitleAbbrev, SetInfo, and ToC, followed by
-the Books, followed by an optional SetIndex. Note that
-a SetIndex may appear in a Book, too.
-Set has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>SetIndex</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Index to a Set. It may
-occur within a Set or one of the Books in a Set.
-It contains an optional DocInfo, Title, and TitleAbbrev,
-followed by any number of block-oriented elements
-and then one or more IndexEntries or one
-or more IndexDivs.
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>SetInfo</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Metainformation for a Set,
-in which it may appear. It may contain, in any order,
-any number of: Author, AuthorInitials,
-Copyright, CorpAuthor, CorpName, Date,
-Editor, Edition, InvPartNumber, ISBN, LegalNotice,
-OrgName, OtherCredit,
-PrintHistory, ProductName, ProductNumber,
-Publisher, PubsNumber, ReleaseInfo, RevHistory,
-Title, Subtitle, and VolumeNum.
-SetInfo has common attributes and a Contents attribute.
-Contents is partly a stub for future development; at the
-moment its values should be the IDs of the ToC, Books,
-and SetIndex that comprise the Set, in the order of
-their appearance.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SGMLTag</TERM>
-<LISTITEM>
-<PARA>An element tag in SGML. This
-element contains plain text, and should not include
-delimiting angle brackets, ampersands,
-percent signs, or semicolons: those should be
-supplied by the renderer if appropriate. It has common and Class
-attributes. Class may be Attribute, Element,
-GenEntity, or ParamEntity; there is no default.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ShortAffil</TERM>
-<LISTITEM>
-<PARA>Brief version of of Affiliation, in
-which it may appear. It contains
-plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Sidebar</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Segment of a book component
-that is isolated from the narrative flow
-of the main text, typically boxed and floating.
-Sidebar may have
-a Title and a TitleAbbrev, followed by
-paragraphs, lists, and other block-oriented
-elements. No Sects allowed.
-Sidebar has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>SimPara</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A paragraph that is only a text block,
-without included block-oriented elements. It
-may contain InlineGraphic, InlineEquation, and synopses.
-SimPara has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>SimpleList</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Intended for long lists of single words
-or short phrases. It consists of one or more Members, and
-has common, Columns, and Type attributes. The value of
-the Type attribute may be Inline, Horiz, or Vert (the
-default), indicating that the list should be formatted
-as part of a regular paragraph, as an array reading L to R
-then top to bottom, or
-as an array reading top to bottom then L to R.
-The Columns attribute value must be a number, the number
-of columns the array should contain. Further details
-on rendering may be found in the comment in the DTD,
-but these details may required some revision in the
-future.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SpanSpec</TERM>
-<LISTITEM>
-<PARA>Formatting information for a
-spanned column in a TGroup (part of Table).
-SpanSpec is an empty element, bearing common, Align,
-Char, Charoff, Colsep, Nameend (required),
-Namest (required), Rowsep, and Spanname,
-(required) attributes.
-SpanSpec identifies a horizontal span of
-columns and associated attributes that can
-subsequently be referenced by its SpanName to
-provide attributes repeatedly used in the Entries or
-EntryTbls in the Rows of the TGroup that is
-nested within the THead, TFoot, or TBody in which the
-SpanSpec occurs.
-</PARA>
-<PARA>The reason Colname is used rather than Colnum
-in identifying
-SpanSpec is that the names are independent of revisions that
-may change the number of inserted/deleted columns, as
-long as Namest remains to the left of (has a smaller colnum
-than) Nameend. SpanSpecs set on THead or TFoot override
-those on the containing TGroup and apply to just the THead
-or TFoot. SpanSpecs from the containing TGroup apply to
-TBody.
-</PARA>
-<PARA><EMPHASIS>Align</EMPHASIS> controls the horizontal position
-of text within the column.
-The value of Align may be Left (quad flush left),
-Center (centered), Right (quad flush right),
-Justify (both quad left and right), or Char (align to the
-left of Char, positioned by Charoff). The default
-is Center.
-</PARA>
-<PARA><EMPHASIS>Char</EMPHASIS> contributes to Align. If the
-value of Align is “char”, the value of Char
-should be a character on the first occurrance
-of which the entry is to be aligned. If that
-character does not occur in the entry, the entry
-is aligned to the left of the position determined
-by Charoff. The default is inherited
-from the ColSpec of the column named by Namest.
-</PARA>
-<PARA><EMPHASIS>Charoff</EMPHASIS> contributes with Char to Align.
-Charoff is the proportion
-of the current column width, expressed in percentage,
-to be allowed before the left edge of the first occurrence
-of the character given as the value of Char, if any.
-The default is inherited from the ColSpec of
-the column named by Namest.
-</PARA>
-<PARA><EMPHASIS>Colsep</EMPHASIS> determines column separators. If its value
-is Yes, display the internal column rulings to
-the right of each item; if No, do not
-display it. It is ignored for the last column, where the
-Frame setting applies. (In CALS,
-Yes is expressed as 1 and No as 0.)
-The default is inherited from the ColSpec of
-the column named by Namest.
-</PARA>
-<PARA><EMPHASIS>Nameend</EMPHASIS> is the name of the rightmost
-column of the span. Names are identified in the
-Colspec of the current TGroup.
-</PARA>
-<PARA><EMPHASIS>Namest</EMPHASIS> or Name Start,
-is the name of the leftmost column
-of the span. Names are identified in the
-Colspec of the current TGroup.
-</PARA>
-<PARA><EMPHASIS>Rowsep</EMPHASIS> determines Row separators. If its content is
-Yes, display the internal vertical Row ruling
-below each item; if No, do not display it. It is
-ignored for the last Row of the table, where
-the frame value applies. There is no default.
-The value is inherited from the ColSpec of
-the column named by Namest.
-</PARA>
-<PARA><EMPHASIS>Spanname</EMPHASIS> is the name of the
-horizontal span.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>State</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Step</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Part of a Procedure. After its
-optional Title, Step must consist either
-of block-oriented elements such as
-paragraphs followed optionally by a SubSteps element,
-or simply a
-SubSteps element. SubSteps then contains one or more
-Steps—it is a wrapper.
-Step has common attributes
-and a Performance attribute, which indicates whether
-the step must be performed: the values are Optional
-and Required (the default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Street</TERM>
-<LISTITEM>
-<PARA>Part of Address. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>StructField</TERM>
-<LISTITEM>
-<PARA>A field in a Structure.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>StructName</TERM>
-<LISTITEM>
-<PARA> The name of a Structure. It contains
-plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SubSteps</TERM>
-<LISTITEM>
-<PARA>A wrapper for Steps within Steps.
-See <EMPHASIS>Procedure, Step.</EMPHASIS> Note that SubSteps, like
-Step, has a Performance attribute, the values of which
-may be Optional or Required (the default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Subscript</TERM>
-<LISTITEM>
-<PARA>A subscript.
-It may contain basic in-line elements and Replaceable,
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Subtitle</TERM>
-<LISTITEM>
-<PARA>Subtitle of a document.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Superscript</TERM>
-<LISTITEM>
-<PARA>A superscript.
-It may contain basic in-line elements and Replaceable,
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Surname</TERM>
-<LISTITEM>
-<PARA>(Western-style) family name
-of an author. It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SWapplic</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Symbol</TERM>
-<LISTITEM>
-<PARA>A name that is replaced by a value before
-processing. It contains plain text and has common
-attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Synopsis</TERM>
-<LISTITEM>
-<PARA>The
-syntax of a command or function. It appears
-within RefSynopsisDiv, and may occur elsewhere in
-a document, too.
-Synopsis has an optional title, followed by one or more
-in-line elements and Graphics; within it,
-line breaks and white space are significant.
-It has common attributes. CmdSynopsis and FuncSynopsis
-are alternates to Synopsis, but they may not contain
-Graphics and within them line breaks and white space are
-not significant. Synopsis should be displayed as
-a block-oriented element, not in-line.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SynopFragment</TERM>
-<LISTITEM>
-<PARA>Part of CmdSynopsis. It contains
-one or more Args or Groups, in any order, and has
-the attributes ID (the only required attribute),
-Lang, Remap, Role, and XRefLabel.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SynopFragmentRef</TERM>
-<LISTITEM>
-<PARA>Part of a CmdSynopsis. It
-contains RCDATA (characters, in which entity
-references and character references are
-recognized in parsing) rather than elements.
-It has common and Linkend (required) attributes.
-Linkend should point to SynopFragment.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SystemItem</TERM>
-<LISTITEM>
-<PARA>Any system-related item.
-It may contain members of cptrphrase.gp,
-and has common, Class, and MoreInfo attributes.
-Class may have
-the value Constant, EnvironVar, Macro, OSname, Prompt,
-Resource, or SystemName
-(no default). For the MoreInfo
-attribute see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>SystemName</TERM>
-<LISTITEM>
-<PARA>Dropped. See <EMPHASIS>SystemItem.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Table</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An array of text.
-The Table models available in version 1.2.2 have been
-dropped in favor of a CALS-compliant Table model.
-The present Table element has a required Title,
-an optional TitleAbbrev, and either one or more Graphics
-or one or more TGroups. Tables may not contain
-either Tables or InformalTables.
-Table has common, Colsep, Frame, Label, Orient, Pgwide, Rowsep, Shortentry,
-Tabstyle, and Tocentry attributes.
-elements that may be contained within
-TGroup are specified as having omissible
-end tags, except for EntryTbl. Who said the military
-isn't thoughtful?
-</PARA>
-<PARA><EMPHASIS>Colsep</EMPHASIS> determines column separators. If its value
-is Yes, display the internal column rulings to
-the right of each item; if No, do not
-display it. It is ignored for the last column, where the
-value of Frame applies. There is no default; the
-value may be inherited from Tabstyle in the FOSI.
-</PARA>
-<PARA><EMPHASIS>Frame</EMPHASIS> describes the positioning of
-framing rules around the Table. The allowed values are
-Sides (left and right), Top (below title),
-Bottom (after last Row, possibly the last Row of
-TFoot), Topbot (both top and bottom), All
-(all of the aforementioned), and None.
-There is no default. The value may be
-inherited from Tabstyle in the FOSI.
-</PARA>
-<PARA><EMPHASIS>Label</EMPHASIS> is just the same as DocBook's
-Label attribute: a reference string, such as a
-number, to be prefixed to the Title.
-</PARA>
-<PARA><EMPHASIS>Orient</EMPHASIS> determines the orientation of the
-Table. The allowed values are Port (the orientation
-of the rest of the text of the Book, that is, upright)
-and Land (90 degrees counterclockwise from the
-orientation of the rest of the text of the Book).
-If you assume that the page is taller than
-it is wide, tables that take up a whole page and
-are wider than they are tall should be given the Land value.
-There is no default, the value may be
-inherited from the FOSI.
-</PARA>
-<PARA><EMPHASIS>Pgwide</EMPHASIS> constrains the table to
-or liberates it from the boundaries of its
-column. If the value is
-Yes, the table runs
-across the entire page; if No, the table “runs
-across just the (galley) width of the
-current column of the page, regardless
-of the value of Orient. If the
-value is No, it has no meaning for the case when
-Orient is set to Land.
-The value may be inherited from Tabstyle in
-the FOSI, if available.
-</PARA>
-<PARA><EMPHASIS>Rowsep</EMPHASIS> determines row separators. If its content is
-Yes, display the internal vertical row ruling
-below each item; if No, do not display it. It is
-ignored for the last row of the table, where
-the value of Frame applies. There is no default.
-The value may be inherited from TabStyle.
-</PARA>
-<PARA><EMPHASIS>Shortentry</EMPHASIS> determines whether value of ShortEntry is be used
-in the an Index or ToC or LoT. If the value is No,
-the TitleAbbrev is not used; if Yes, the ShortEntry
-is used.
-<EMPHASIS>Usage Note:</EMPHASIS> Be aware that
-this mechanism duplicates the DocBook element
-TitleAbbrev. It would be better, for any given
-work, to choose one mechanism
-or the other, rather than mix them.
-</PARA>
-<PARA><EMPHASIS>Tabstyle</EMPHASIS> is the name of
-a table style defined in the FOSI. There is no default.
-</PARA>
-<PARA><EMPHASIS>Tocentry</EMPHASIS> determines whether the
-Table's Title should be included in an LoT.
-The value may be Yes (include) or No (exclude).
-The default is Yes (include).
-should be ignored if the optional Title is
-omitted; that would be the case if you were using Table,
-instead of InformalTable, for a Table that has no
-Title; presumably only a reference string could then
-appear in an LoT.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Term</TERM>
-<LISTITEM>
-<PARA>The hanging term attached to a ListItem
-within a VarListEntry in a
-VariableList; visually, a VariableList
-is a set of Terms with attached items such as paragraphs. Each
-ListItem may be associated with a set of Terms. Term may contain
-in-line elements or synopses. It has
-common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Tertiary</TERM>
-<LISTITEM>
-<PARA>A word or phrase that is to
-appear in the index under a Secondary entry. It must be
-nested within IndexTerm tags and must follow a Secondary
-element. It may contain in-line elements, and has SortAs
-and common attributes. See <EMPHASIS>Primary.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>TertiaryIE</TERM>
-<LISTITEM>
-<PARA>Part of IndexEntry, like PrimaryIE
-see <EMPHASIS>PrimaryIE</EMPHASIS>).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>TBody</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Wrapper for the Rows of a Table or
-InformalTable. It contains simply one or more Rows,
-and has common and VAlign attributes.
-VAlign governs the vertical
-positioning of text within a Row.
-Allowed values are Top (the default), Middle, and Bottom.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>TFoot</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>TFoot is a optional part of TGroup
-(part of Table), identifying the footer information in a
-Table, which is displayed after the TBody and also at the
-bottom of any TBody Rows before a page break.
-TFoot must have one or
-more Rows. It has common and VAlign attributes, the latter
-with the allowed values of Top (the default), Middle
-(approximately centered vertically), and Bottom.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>TGroup</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The part of a Table that is
-contains an array along with its formatting information.
-In order, a TGroup has any number of ColSpecs,
-any number of SpanSpecs, an optional THead, and optional
-TFoot, and a required TBody.
-Each TGroup effectively identifies a new
-portion of a Table. If a new ColSpec is provided, it
-replaces a previous one. If both ColSpec and SpanSpec
-are new, that SpanSpec should refer to columns in the most
-recent ColSpec. If only a new SpanSpec is provided, it
-should refer to columns defined by the most immediately
-prior ColSpecs in a TGroup of the
-Table. On the other hand, a new ColSpec to
-either a THead or TFoot replaces all prior column
-definitions. TGroup has common, Align, Char, Charoff, Cols,
-Colsep, Rowsep, and TGroupStyle attributes.
-</PARA>
-<PARA><EMPHASIS>Align</EMPHASIS> controls the horizontal position
-of text within the column.
-The value of Align may be Left (quad flush left),
-Center (centered), Right (quad flush right),
-Justify (both quad left and right), or Char (align to the
-left of Char, positioned by Charoff). The default
-is Left, unless overridden by TGroupStyle.
-</PARA>
-<PARA><EMPHASIS>Char</EMPHASIS> contributes to Align. If the
-value of Align is “char”, the value of Char
-should be a character on the first occurrance
-of which the entry is to be aligned. If that
-character does not occur in the entry, the entry
-is is aligned to the left (the original doc incorrectly
-specifies “right”) of that character.
-The default is “”, unless inherited
-from TGroupStyle.
-</PARA>
-<PARA><EMPHASIS>Charoff</EMPHASIS> contributes with Char to Align.
-Charoff is the proportion
-of the current column width, expressed in percentage,
-to be allowed before the left edge of the first occurrence
-of the character given as the value of Char, if any.
-The default is 50 unless overridden by TGroupStyle.
-</PARA>
-<PARA><EMPHASIS>Cols</EMPHASIS> is the number of columns in the table
-(required).
-</PARA>
-<PARA><EMPHASIS>Colsep</EMPHASIS>
-determines column separators. If its value
-is Yes, display the internal column rulings to
-the right of each item; if No, do not
-display it. It is ignored for the last column, where the
-value of Frame applies. There is no default. The
-value is inherited from TGroupStyle, if used.
-</PARA>
-<PARA><EMPHASIS>Rowsep</EMPHASIS>
-determines row separators. If its content is
-Yes, display the internal vertical row ruling
-below each item; if No, do not display it. It is
-ignored for the last row of the table, where
-the value of Frame applies. There is no default.
-The value is inherited from TGroupStyle, if used.
-</PARA>
-<PARA><EMPHASIS>TGroupStyle</EMPHASIS> is a unique table group
-style defined in a FOSI (no default).
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>THead</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>THead is a optional part of TGroup
-(part of Table). THead may have any
-number of ColSpecs, followed by one or more required
-Rows. It has common and VAlign attributes, the latter
-with the allowed values of Top, Middle, and Bottom
-(the default).
-THead identifies the heading information in a Table,
-which is displayed at the top of
-the Table and again at the top of any continuation after a
-page break between Rows in TBody.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Tip</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A suggestion to the user, set off from
-the text. See <EMPHASIS>Caution.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Title</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The text of a heading or the title of a
-block-oriented element. Title may contain
-in-line elements, and has common and PageNum attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>TitleAbbrev</TERM>
-<LISTITEM>
-<PARA>An optional, abbreviated
-version of any Title.
-You may want to use this element when a
-title is so long that it might be truncated in
-some part of an online display, such as a title bar.
-TitleAbbrev may contain
-in-line elements and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ToC</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A Table of Contents, which may be
-a book component on its own or may
-occur within other book components. It may
-have a DocInfo, Title, and TitleAbbrev. Formerly,
-ToC contained only ToCentry1s, but in this revision
-it has been subdivided to follow the divisions of a book:
-following the optional Title and
-TitleAbbrev, a ToC may have any number of ToCFronts, which
-are the entries for the front matter. Following the
-ToCFronts, if any, ToC
-must have either
-one or more ToCParts (entries for Parts)
-or ToCChaps (entries for Chapters and Appendices),
-and may have any number of ToCBacks
-(entries for back matter).
-A ToCPart may begin with in-line elements (in all
-cases, this is the
-actual entry, which was formerly ToCEntry), then contains
-any number of ToCChaps. A ToCChap may begin with
-in-line elements, then may have any number of ToCLevel1s,
-which are entries for Sect1s.
-ToCLevel1s may begin with in-line elements, then may have
-any number of ToCLevel2s, and so on down to ToCLevel5,
-which may have only in-line elements. Thus if you have a
-Table of Contents that shows section headings, the second-level entries
-are nested within the first-level entries, and so on.
-ToC has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ToCBack</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Entry for back matter in a ToC.
-See <EMPHASIS>ToC.</EMPHASIS>
-It has common, Linkend, Pagenum, and Label attributes.
-The Label attribute may take the value of Bib, Gloss, or
-Index,
-depending on the identity of the
-piece of front matter concerned.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ToCChap</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>See <EMPHASIS>ToC.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ToCFront</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>Entry for introductory matter in a ToC.
-See <EMPHASIS>ToC.</EMPHASIS>
-It has common, Linkend, Pagenum, and Label attributes.
-The Label attribute may take the value of Equations, Examples,
-Figures, Preface, or Tables, depending on the identity of the
-piece of front matter concerned.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ToCLevel1</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>The top-level tag for entries in a ToC.
-See <EMPHASIS>ToC.</EMPHASIS>
-ToCLevel2–5 may be nested within it, in order. All
-have common attributes and Linkend and
-PageNum attributes. PageNum is for indicating the page numbers on which
-the Table of Contents entries appear in a printed book. Linkend,
-should you choose to use it,
-should have the value of the ID of the relevant book part.
-ToCLevel1–5 may contain
-in-line elements.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>ToCPart</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>See <EMPHASIS>ToC.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Token</TERM>
-<LISTITEM>
-<PARA>A unit of information in the context of
-lexical analysis. It contains plain text and
-has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Trademark</TERM>
-<LISTITEM>
-<PARA>A trademark.
-It may contain members of cptrphrase.gp,
-and has common and Class attributes.
-Class may have the values Service, Trade, Registered,
-or Copyright; the default is Trade.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Type</TERM>
-<LISTITEM>
-<PARA>Indicates the classification of a value.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>ULink</TERM>
-<LISTITEM>
-<PARA>A link containing a URL.
-A URL is a Uniform Resource Locator, as used with the
-World Wide Web. Very generally,
-a URL is a string specifying, according to a defined
-protocol, a method,
-a path to a target, and possibly some additional information.
-The URL should be given as the value
-of the URL attribute; there is also a Type attribute.
-While ULink is powerful,
-it is experimental and may be dropped in future
-revisions. Users should not expect
-it to be supported by SGML browsers.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>UserInput</TERM>
-<LISTITEM>
-<PARA>Data entered by the user.
-It may contain elements from cptrphrase.gp,
-and has common and
-MoreInfo attributes. For the MoreInfo attribute
-see <EMPHASIS>Application.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>VarArgs</TERM>
-<LISTITEM>
-<PARA>An empty element, part of FuncSynopsis,
-indicating that the Function in question
-has a variable number of arguments. The string
-“(...)” should be output.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>VariableList</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An optionally
-titled list of VarListEntries, which are
-composed of sets of one or more Terms with associated
-ListItems; ListItems contain paragraphs and other block-oriented
-elements in any order. Inclusions
-are as for OrderedList (see <EMPHASIS>OrderedList</EMPHASIS>).
-VariableList has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>VarListEntry</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>A component of VariableList (see <EMPHASIS>VariableList</EMPHASIS>). It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>VarParam</TERM>
-<LISTITEM>
-<PARA>Dropped.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Void</TERM>
-<LISTITEM>
-<PARA>An empty element, part of FuncSynopsis,
-that indicates that the Function in question
-takes no arguments. The string “(void)”
-should be output. See <EMPHASIS>VarArgs.</EMPHASIS>
-It has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>VolumeNum</TERM>
-<LISTITEM>
-<PARA>The number of a Book in
-relation to Set, or of a journal, when Book
-is used to represent a journal by containing
-Articles. It contains plain text
-and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM><EMPHASIS>Warning</EMPHASIS></TERM>
-<LISTITEM>
-<PARA>An admonition set off from the text.
-See <EMPHASIS>Caution.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>WordAsWord</TERM>
-<LISTITEM>
-<PARA>A word (or letter or
-number) used not to represent the thing or idea it usually
-represents, but merely as the word itself. For example,
-“The term <SGMLTAG>WORDASWORD</SGMLTAG>Gothic<SGMLTAG>/WORDASWORD</SGMLTAG> means different
-things to art historians and typographers,” or for a single
-character, “the
-letter <SGMLTAG>WORDASWORD</SGMLTAG>X<SGMLTAG>/WORDASWORD</SGMLTAG>”.
-It contains plain text and has common attributes.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>XRef</TERM>
-<LISTITEM>
-<PARA>Cross reference link to another part of the
-document.
-It has Linkend and Endterm attributes, just like Link,
-but like Anchor, it may have no content.
-XRef must have a Linkend, but the Endterm is optional.
-If it is used, the content of the element it points
-to is displayed as the text of the cross reference;
-if it is absent, the XRefLabel of the cross-referenced
-object is displayed.
-See <EMPHASIS>Link.</EMPHASIS>
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY><TERM>Year</TERM>
-<LISTITEM>
-<PARA>Year of publication, for use in Copyright.
-It contains plain text.
-</PARA></LISTITEM></VARLISTENTRY>
-</VARIABLELIST>
-</SECT1>
-</CHAPTER>
-
+++ /dev/null
-<!DOCTYPE DOCBOOK SYSTEM "/work/dmg/dtds/docbook.dtd">
-<DOCBOOK>
-<CHAPTER ID="CH-1015-3-1" NUMBER="3"><TITLE>Working in the X Environment</TITLE>
-<TITLEABBREV>Working in the X Environment</TITLEABBREV>
-<HIGHLIGHTS>
-<PARA>This chapter shows you how to begin working productively in the X
-environment. It describes how to:
-</PARA>
-<ITEMIZEDLIST MARK="BULLET">
-<LISTITEM>
-<PARA>Open a second <COMMAND>xterm</COMMAND> window.
-</PARA>
-</LISTITEM>
-<LISTITEM>
-<PARA>Move windows; raise windows to the front of the display; convert
-windows to icons.
-</PARA>
-</LISTITEM>
-<LISTITEM>
-<PARA>Close an <COMMAND>xterm</COMMAND> window.
-</PARA>
-</LISTITEM>
-<LISTITEM>
-<PARA>Start other clients in convenient places on the display.
-</PARA>
-</LISTITEM>
-<LISTITEM>
-<PARA>Run clients on remote machines.
-</PARA>
-</LISTITEM>
-<LISTITEM>
-<PARA>Customize a single client process using command-line options.
-</PARA>
-</LISTITEM>
-<LISTITEM>
-<PARA>Specify alternate default characteristics for a client using resource variables.
-</PARA></LISTITEM>
-</ITEMIZEDLIST>
-</HIGHLIGHTS>
-<PARA>At the end of the last chapter, you should've had the X server, the
-first <COMMAND>xterm</COMMAND> window, and the <COMMAND>mwm</COMMAND> window manager running.
-The current chapter
-illustrates some of the system's basic capabilities
-so you can begin working more productively. This chapter shows you how to:
-</PARA>
-<ITEMIZEDLIST MARK="BULLET">
-<LISTITEM>
-<PARA>Open a second <COMMAND>xterm</COMMAND> window.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Use the pointer to affect windows on the display.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Iconify, deiconify, maximize, raise, move, resize, and close windows
-using the pointer on the <COMMAND>mwm</COMMAND> frame.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Close an <COMMAND>xterm</COMMAND> window from the command line.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Start additional client programs, on both local and remote machines.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Organize the display.
-</PARA></LISTITEM>
-</ITEMIZEDLIST>
-<PARA>This chapter also introduces some basic ways
-to customize X clients to better suit your needs.
-</PARA>
-<SECT1 ID="S1-1015-3-1"><TITLE>Creating Other Windows</TITLE>
-<INDEXTERM ID="IX-1015-3-1" SPAN="START"><PRIMARY>windows</PRIMARY><SECONDARY>creating</SECONDARY></INDEXTERM>
-<PARA>Once you focus input on the first <COMMAND>xterm</COMMAND> window, as described in
-Chapter 2, you can enter
-commands to open other client windows. For example,
-you can open a second <COMMAND>xterm</COMMAND> window by typing this
-command at the prompt in the first <COMMAND>xterm</COMMAND> window:
-<INDEXTERM ID="IX-1015-3-2"><PRIMARY>xterm (terminal emulator)</PRIMARY><SECONDARY>multiple xterms</SECONDARY></INDEXTERM>
-</PARA>
-<SCREEN ID="SC-1015-3-1"><PROMPT>%</PROMPT> <USERINPUT>xterm </USERINPUT>
-</SCREEN>
-<PARA>After a few moments, a second <COMMAND>xterm</COMMAND> window will be displayed on the
-screen. As we'll see later in this chapter, you can specify the
-location for a new window using a command-line option (or in many cases using a resource variable
-stored in a file in your home directory).
-If you don't specify
-position on the command line (or in a resource
-file), by default <COMMAND>mwm</COMMAND>
-automatically places
-new windows offset from the upper-left corner of
-the screen, as shown in
-<XREF LINKEND="FG-1015-3-1">Figure 3-1</XREF>.<FOOTNOTEREF LINKEND="FN-1015-3-1"></FOOTNOTEREF>
-<FOOTNOTE ID="FN-1015-3-1">
-<PARA>If you start multiple processes in a row, the windows will be placed
-progressively further from the upper-left corner (towards the opposite
-corner), so that no window completely overlaps another.
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-3"><PRIMARY>windows</PRIMARY><SECONDARY>place using pointer</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-4"><PRIMARY>interactivePlacement</PRIMARY></INDEXTERM>
-You can customize <COMMAND>mwm</COMMAND> to allow you to place new windows
-interactively using the pointer. This modification is performed
-by setting a resource variable called <RESOURCE>interactivePlacement</RESOURCE>
-to a value of true.
-See Chapter 13 for instructions on modifying <COMMAND>mwm</COMMAND>.
-See the <COMMAND>mwm</COMMAND> reference page in Part Three of this guide for
-more information about <RESOURCE>interactivePlacement</RESOURCE>.
-</PARA>
-</FOOTNOTE>
-</PARA>
-<FIGURE ID="FG-1015-3-1">
-<TITLE>mwm automatically places the second xterm window</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.01.eps" ID="GC-1015-3-1"></GRAPHIC>
-</FIGURE>
-<PARA>The new <COMMAND>xterm</COMMAND> window displays a
-prompt from whatever shell you are using. In this case, the new window is
-running the UNIX C shell.
-</PARA>
-<PARA>Notice that the second window's frame is a dark gray, indicating that input
-is focused on it.
-The first window's frame has changed from dark to light gray; it no longer
-has the input focus.
-It's important to be aware that when
-you start a new window (and click-to-type focus is being used), the
-new window automatically takes over the input focus.
-(Note that the colors may vary according to system defaults.)
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-5"><PRIMARY>windows</PRIMARY><SECONDARY>switching between</SECONDARY></INDEXTERM>
-In the default <COMMAND>mwm</COMMAND> configuration,
-to switch back and forth between windows you must move the pointer
-from one window to the other and click the first button.
-Notice that if you are working with a stack of windows that overlap,
-selecting a window as the active window automatically raises that window
-to the top of the stack (in effect, the front of the display).
-</PARA>
-<PARA>Whatever you type will appear in the window with the highlighted frame.
-Try starting a command in both windows. For example, start up
-<COMMAND>vi</COMMAND> or another text editor in the second <COMMAND>xterm</COMMAND> window.
-Notice how you can switch back to the first window to type a new
-command, by moving the pointer and clicking--even if you
-leave <COMMAND>vi</COMMAND> in
-insert mode or some other command in the process of sending output to
-the screen. Whatever process was running in the window you left will
-continue to run. If it needs input from you to continue, it will wait.
-<INDEXTERM ID="IX-1015-3-6"><PRIMARY>windows</PRIMARY><SECONDARY>multiple</SECONDARY></INDEXTERM>
-</PARA>
-<PARA>You must always switch focus to work with multiple windows. However,
-<COMMAND>mwm</COMMAND> has complicated matters by placing the second <COMMAND>xterm</COMMAND>
-window in <XREF LINKEND="FG-1015-3-1">Figure 3-1</XREF>
- in a very inconvenient place. The second
-window overlies the first window and almost completely obscures it.
-</PARA>
-<PARA>Windows commonly overlap on
-the display. The window manager allows you to change the position and
-size of windows so that you can work effectively in such situations.
-</PARA>
-<PARA>The primary window management tool <COMMAND>mwm</COMMAND> provides is the window frame.
-The section “Managing Windows Using the mwm Frame,” later in this
-chapter,
-shows you how to perform these functions simply by using the pointer on
-various parts of the frame. But before we can learn to perform these window
-management functions, we need to learn more about pointer actions.
-</PARA>
-<SECT2 ID="S2-1015-3-1"><TITLE>Using the Pointer</TITLE>
-<INDEXTERM ID="IX-1015-3-7" SPAN="START"><PRIMARY>pointer</PRIMARY><SECONDARY>using</SECONDARY></INDEXTERM>
-<PARA>As explained in Chapter 1, the cursor on the screen follows the
-pointer's movement on the desktop. Move your pointer
-around on the desk to get used to this. Keep in mind that
-different pointers respond differently. If you move to another
-display, the screen cursor may move more quickly or slowly than the
-one you're used to. The <COMMAND>xset</COMMAND> client (described
-in &cmtf14;) lets you modify pointer behavior.
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-8"><PRIMARY>button</PRIMARY><SECONDARY>pointer</SECONDARY></INDEXTERM>
-You use the pointer to indicate a graphical element on the screen,
-such as a window, icon, or command button. Most pointers have
-three buttons. For our purposes, we'll refer to these buttons
-as first, second, and third, where the first button is the leftmost
-on the pointer, the second is in the middle, and third is the
-rightmost.<FOOTNOTEREF LINKEND="FN-1015-3-2"></FOOTNOTEREF>
-<FOOTNOTE ID="FN-1015-3-2">
-<PARA>Keep in mind that “first” is a logical distinction
-made by X, not a physical one. The first logical pointer button generally
-corresponds to the leftmost button on the pointer.
-(Thus, in some contexts you may find the buttons referred to as left, middle,
-and right.)
-However, X allows you to
-change the correspondence of logical and physical buttons. For
-example, you can reassign
-the first logical button to be the rightmost button on the pointer.
-A lefthanded person might opt to reverse the order of the buttons.
-You remap pointer buttons using a client called <COMMAND>xmodmap</COMMAND>, which
-is described in detail in &cmtf14;.
-</PARA>
-</FOOTNOTE>
-By placing the pointer on a particular element and then
-performing some button action (and possibly a pointer motion), you can
-invoke a variety of
-commands. The types of button actions and pointer motions you can perform are:
-</PARA>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>Click</TERM>
-<LISTITEM>
-<PARA><INDEXTERM ID="IX-1015-3-9"><PRIMARY>clicking buttons</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-10"><PRIMARY>button</PRIMARY><SECONDARY>clicking</SECONDARY></INDEXTERM>
-To click a button, you press the pointer button down and release it.
-A click is a rapid action; there is no pause between the press and
-release. A double click is two full clicks in succession, with no
-pause between clicks. A triple click is three clicks in
-succession.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>Press</TERM>
-<LISTITEM>
-<PARA><INDEXTERM ID="IX-1015-3-11"><PRIMARY>button</PRIMARY><SECONDARY>pressing</SECONDARY></INDEXTERM>
-To press a button, you push the button down and hold it down.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>Release</TERM>
-<LISTITEM>
-<PARA><INDEXTERM ID="IX-1015-3-12"><PRIMARY>button</PRIMARY><SECONDARY>releasing</SECONDARY></INDEXTERM>
-After pressing a button down, you release it by letting up on the button.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>Drag</TERM>
-<LISTITEM>
-<PARA><INDEXTERM ID="IX-1015-3-13"><PRIMARY>pointer</PRIMARY><SECONDARY>dragging item with</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-14"><PRIMARY>dragging items</PRIMARY></INDEXTERM>
-To drag a graphical object (such as a window or icon) from one
-location on the screen to another: place the pointer on the object;
-press one or more pointer buttons; move the pointer to another
-location (dragging the object); and release the button(s).
-</PARA></LISTITEM>
-</VARLISTENTRY></VARIABLELIST>
-<PARA>Keep in mind that
-some commands or actions are invoked by a simple click on
-a particular graphic element, as illustrated by <COMMAND>mwm</COMMAND>'s
-click-to-type focus. Alternatively, some actions require a button
-press and pointer motion (i.e., dragging).
-</PARA>
-<PARA>When dragging is used to move an object,
-the actual object does not appear in the new location until you
-complete the movement and release the pointer button. Instead, you
-appear to drag an outline representing the object.
-When you release the pointer button, the actual object appears in the
-new location. This effect is illustrated in the section “Moving a Window,”
-later in this chapter.
-</PARA>
-<PARA>Dragging is also commonly used to change the size of a window.
-Again, an outline indicates that the window's size is changing. When
-the outline approximates the size you want, you release the pointer
-button and the actual window is redrawn using the selected dimensions.
-</PARA>
-<PARA>The following sections describe how to perform the most basic window
-management functions, which require you to use the pointer in the ways
-we've discussed.
-<INDEXTERM ID="IX-1015-3-15" SPAN="END"><PRIMARY>pointer</PRIMARY><SECONDARY>using</SECONDARY></INDEXTERM>
-</PARA>
-</SECT2>
-<SECT2 ID="S2-1015-3-2"><TITLE>Managing Windows Using the mwm Frame</TITLE>
-<INDEXTERM ID="IX-1015-3-16" SPAN="START"><PRIMARY>mwm (Motif window manager)</PRIMARY></INDEXTERM>
-<PARA><XREF LINKEND="FG-1015-3-2">Figure 3-2</XREF>
-shows an <COMMAND>xterm</COMMAND> window “framed” by <COMMAND>mwm</COMMAND>.
-The window frame itself and several features of it
-are tools that allow you to manage the window using the pointer.
-</PARA>
-<FIGURE ID="FG-1015-3-2">
-<TITLE>An xterm window framed by mwm</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.02.eps" ID="GC-1015-3-2"></GRAPHIC>
-</FIGURE>
-<INDEXTERM ID="IX-1015-3-17"><PRIMARY>command buttons</PRIMARY><SECONDARY>Minimize</SECONDARY></INDEXTERM>
-<PARA>The wider top edge
-of the frame is the titlebar. The titlebar is
-composed of several parts including a title area (displaying the
-name of the application) and three command buttons (Minimize, Maximize,
-and Window Menu). Notice that whenever you move the pointer into the
-titlebar, the pointer changes to the arrow cursor.
-</PARA>
-<PARA>Though it's not apparent from <XREF LINKEND="FG-1015-3-2">Figure 3-2</XREF>,
- you can perform most window
-management functions by using the pointer on various parts of the frame.
-<INDEXTERM ID="IX-1015-3-18"><PRIMARY>titlebar</PRIMARY></INDEXTERM>
-The following sections explain how to
-iconify, maximize, move, raise, resize, and close windows using the frame.
-Chapter 4 describes menu items and keyboard shortcuts
-that can be used as alternatives to the frame.
-These are important when a window's frame is obscured by other
-features of the display. Chapter 4 also describes additional
-functions provided by <COMMAND>mwm</COMMAND> menus.
-</PARA>
-<SECT3 ID="S3-1015-3-1"><TITLE>Converting a Window to an Icon</TITLE>
-<INDEXTERM ID="IX-1015-3-19"><PRIMARY>windows</PRIMARY><SECONDARY>iconifying</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-20" SPAN="START"><PRIMARY>Minimize command button</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-21" SPAN="START"><PRIMARY>command buttons</PRIMARY><SECONDARY>Minimize</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-22"><PRIMARY>iconifying windows</PRIMARY></INDEXTERM>
-<PARA>As discussed in Chapter 1, an icon is a symbol that represents a
-window in an inactive state. There are many circumstances in which
-it might be desirable to iconify a window:
-</PARA>
-<ITEMIZEDLIST MARK="BULLET">
-<LISTITEM>
-<PARA>To prevent yourself from inadvertently terminating a window, as in
-the case of the login <COMMAND>xterm</COMMAND>.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>While running a program whose progress you don't need to
-monitor; if a window is tied up running a process and you don't have
-to see it, the window is just taking up space.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>If you are only using an application occasionally.
-For example, you might be
-running the <COMMAND>xcalc</COMMAND> calculator program, but
-only using it every so often.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>If you want to use several application windows, but only display a few at a
-time; this arrangement can be somewhat less confusing than a display crowded
-with windows. Having some windows iconified also frees you from
-constantly shuffling the stacking order.
-</PARA></LISTITEM>
-</ITEMIZEDLIST>
-<PARA>The Minimize command button on the <COMMAND>mwm</COMMAND> frame allows you to
-convert a window to an icon (iconify it).
-The Minimize button appears immediately to the right of the title area
-and is identified by a tiny square in its center.
-To iconify a window, use the following steps:
-</PARA>
-<ORDEREDLIST NUMERATION="ARABIC">
-<LISTITEM>
-<PARA>Place the pointer within the Minimize command button. The pointer simply
-has to rest within the button's outer border, not within the tiny square
-identifying it.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Click the first pointer button. The window is iconified.
-<XREF LINKEND="FG-1015-3-3">Figure 3-3</XREF>
-shows a window being converted to an icon in this way.
-</PARA></LISTITEM>
-</ORDEREDLIST>
-<PARA>By default, icons are displayed in the bottom left corner of the root
-window. <COMMAND>mwm</COMMAND> can also be set up to place icons in another location,
-to allow you to place them interactively using the pointer, or
-to organize icons within a window
-known as an <FIRSTTERM>icon box</FIRSTTERM>. In &cmtf13;, we'll discuss the
-specifications necessary to set up an icon box.
-</PARA>
-<FIGURE ID="FG-1015-3-3">
-<TITLE>Converting a window to an icon with the Minimize button</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.03.eps" ID="GC-1015-3-3"></GRAPHIC>
-</FIGURE>
-<INDEXTERM ID="IX-1015-3-23" SPAN="END"><PRIMARY>Minimize command button</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-24" SPAN="END"><PRIMARY>command buttons</PRIMARY><SECONDARY>Minimize</SECONDARY></INDEXTERM>
-</SECT3>
-<SECT3 ID="S3-1015-3-2"><TITLE>Converting an Icon to a Window</TITLE>
-<INDEXTERM ID="IX-1015-3-25"><PRIMARY>windows</PRIMARY><SECONDARY>deiconifying</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-26"><PRIMARY>deiconifying windows</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-27"><PRIMARY>icons</PRIMARY><SECONDARY>converting to windows</SECONDARY></INDEXTERM>
-<PARA>To convert an icon back to a window (deiconify it), place the pointer
-on the icon and double click, using the first pointer button.
-The window is redisplayed in the position it appeared before it was
-iconfied (and is also raised to the top of the stack).
-</PARA>
-<PARA>Between the first and second clicks, you'll probably notice
-that another small window is displayed for an instant above the icon.
-This window is actually a menu, called the <INTERFACE>Window Menu</INTERFACE>.
-(This menu can be displayed from a window or from an icon and can be
-used to invoke several window management functions on the window or
-icon. We'll discuss the <INTERFACE>Window Menu</INTERFACE> in more
-detail in &cmtf04;.)
-</PARA>
-<PARA>Be aware, however, that if you pause too long between the two clicks
-in deiconifying a window, the second click will not be interpreted
-and the icon will not be converted back to a window.
-Instead the <INTERFACE>Window Menu</INTERFACE> will remain on the screen, as in
-<XREF LINKEND="FG-1015-3-4">Figure 3-4</XREF>.
-</PARA>
-<PARA>Notice that in addition to displaying the menu,
-clicking has caused the icon image to change in appearance.
-The icon label is wider and the
-label and the frame surrounding the icon are highlighted.
-These changes indicate that the icon has the input focus; thus the
-icon will interpret subsequent
-keystrokes as window manager commands.
-</PARA>
-<PARA>Notice also that the first item on the
-menu, <INTERFACE>Restore</INTERFACE>, is surrounded by a box, indicating that
-it is available for selection. <INTERFACE>Restore</INTERFACE> means to
-restore an icon to a window (or, as we'll see, a maximum size window to
-its original size). When the <INTERFACE>Window
-Menu</INTERFACE>0 is displayed above an icon, you can convert the icon to a
-window by placing the pointer on the <INTERFACE>Restore</INTERFACE> menu item
-and clicking the first pointer button.
-(Whenever a <INTERFACE>Window Menu</INTERFACE> item is boxed, you can also
-select it by pressing either the Return key or the space bar.)
-</PARA>
-<FIGURE ID="FG-1015-3-4">
-<TITLE>Window Menu being displayed over an icon</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.04.eps" ID="GC-1015-3-4"></GRAPHIC>
-</FIGURE>
-<PARA>If you want to remove the
-menu without invoking a command, simply move the pointer off the
-icon and menu and click the first pointer button.
-The menu will be removed; however, the icon will retain the input
-focus--the label and border will remain
-highlighted--until you focus input on another window or icon.
-</PARA>
-</SECT3>
-<SECT3 ID="S3-1015-3-3"><TITLE>Maximizing a Window</TITLE>
-<INDEXTERM ID="IX-1015-3-28"><PRIMARY>button</PRIMARY><SECONDARY>command</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-29"><PRIMARY>command buttons</PRIMARY><SECONDARY>Minimize</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-30"><PRIMARY>Minimize command button</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-31"><PRIMARY>command buttons</PRIMARY><SECONDARY>Maximize</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-32"><PRIMARY>windows</PRIMARY><SECONDARY>minimizing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-33"><PRIMARY>windows</PRIMARY><SECONDARY>maximizing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-34" SPAN="START"><PRIMARY>Maximize command button</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-35"><PRIMARY>windows</PRIMARY><SECONDARY>enlargening</SECONDARY></INDEXTERM>
-<PARA>Maximizing a window generally means enlarging it to the size of the root
-window. (In some cases, a client application may specify its
-own maximum window size and maximizing will produce a window of this size.)
-This action can be performed using the Maximize command button, which
-is located to the right of the Minimize command button (in the upper-right
-corner of the window).
-</PARA>
-<PARA>The Maximize command button is identified by
-a larger square in its center.
-It allows you both to enlarge the window to the size of
-the root window (or to the maximum size the client allows), and
-once it has been enlarged, to convert it back to its original size.
-</PARA>
-<PARA>To maximize a window, use the following steps:
-</PARA>
-<ORDEREDLIST NUMERATION="ARABIC">
-<LISTITEM>
-<PARA>Place the pointer within the Maximize command button. The pointer simply
-has to rest within the button's outer border, not within the square
-identifying it.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Click the first pointer button. The window is maximized, as
-illustrated in
-<XREF LINKEND="FG-1015-3-5">Figure 3-5</XREF>.
-</PARA></LISTITEM>
-</ORDEREDLIST>
-<FIGURE ID="FG-1015-3-5">
-<TITLE>A maximized window</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.05.eps" ID="GC-1015-3-5"></GRAPHIC>
-</FIGURE>
-<PARA>The large window should function in the same way it did before it was
-maximized. Theoretically, you can maximize an <COMMAND>xterm</COMMAND> window to have a
-single, very large terminal screen. However, be aware that certain
-programs you may run within an <COMMAND>xterm</COMMAND>, such as the <COMMAND>vi</COMMAND> text
-editor, do not always work properly
-within a window of this size (even if you've used the
-<COMMAND>resize</COMMAND>
-client, as described in &cmtf05;).
-The Maximize function is more safely
-used with an application that displays a graphic image or performs a
-simple function, such as <COMMAND>xclock</COMMAND>.
-</PARA>
-<PARA>Also, some client programs that do not
-support resizing, such as the Release 3 version of <COMMAND>xcalc</COMMAND>, cannot
-<INDEXTERM ID="IX-1015-3-36"><PRIMARY>xcalc (calculator)</PRIMARY><SECONDARY>and resizing windows</SECONDARY></INDEXTERM>
-be maximized correctly.
-In the case of <COMMAND>xcalc</COMMAND>, the frame surrounding the
-calculator application is maximized, but the actual calculator remains the
-same size.
-</PARA>
-<PARA>The Maximize button is a toggle.
-To convert a maximized window back to its original size, click on
-the Maximize button again with the first pointer button.
-The <INTERFACE>Restore</INTERFACE> item on the <INTERFACE>Window Menu</INTERFACE> will also
-perform this function.
-<INDEXTERM ID="IX-1015-3-37" SPAN="END"><PRIMARY>Maximize command button</PRIMARY></INDEXTERM>
-</PARA>
-</SECT3>
-<SECT3 ID="S3-1015-3-4"><TITLE>Raising a Window or Icon</TITLE>
-<INDEXTERM ID="IX-1015-3-38"><PRIMARY>windows</PRIMARY><SECONDARY>raising</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-39"><PRIMARY>icons</PRIMARY><SECONDARY>raising</SECONDARY></INDEXTERM>
-<PARA>We've already seen the necessity for raising windows on the display:
-frequently windows overlap. In order to work with a window that is
-all or partially covered by another window, you'll want to raise it
-to the top of the window stack. Using the default <COMMAND>mwm</COMMAND>,
-you raise a window with the following steps:
-</PARA>
-<ORDEREDLIST NUMERATION="ARABIC">
-<LISTITEM>
-<PARA>Place the pointer on any part of the window frame, except the three
-command buttons (Minimize, Maximize, and Window Menu).
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Click the first pointer button. The window is raised to the top of the
-stack.
-</PARA></LISTITEM>
-</ORDEREDLIST>
-<PARA>When you are using explicit (click-to-type) focus, this click
-also selects the window to receive input, i.e.,
-makes the window the active window.
-Once you have raised a window to the top of the stack, you should be
-able to enter input and read output easily.
-</PARA>
-<PARA>Windows may obscure icons on the display. (<COMMAND>mwm</COMMAND> does not allow
-one icon to obscure another.) If an icon is partially visible under
-a window, you can raise it using the following steps:
-</PARA>
-<ORDEREDLIST NUMERATION="ARABIC">
-<LISTITEM>
-<PARA>Place the pointer on the obscured icon.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Click the first pointer button.
-</PARA></LISTITEM>
-</ORDEREDLIST>
-<PARA>The icon is raised to the top of the stack.
-</PARA>
-<PARA><XREF LINKEND="FG-1015-3-6">Figure 3-6</XREF>
-illustrates an icon being raised in front of a window.
-</PARA>
-<PARA>Notice that in addition to being raised to the top of the window stack,
-a menu (called the <INTERFACE>Window Menu</INTERFACE>)
-is displayed over the icon.
-(This menu can be displayed from a window or from an icon and can
-be used to invoke several management functions on the window or icon.
-We'll discuss the <INTERFACE>Window Menu</INTERFACE> in more detail in Chapter 4.)
-To remove the menu, move the pointer off of the icon and menu and
-click the first button.
-</PARA>
-<PARA>Notice also that the icon image changes in appearance when you raise the
-icon to the top of the stack (as it did when we paused between the double
-click to deiconify).
-The wider label and the highlighted label and frame
-indicate that the icon has the input focus. (Remember, when an icon
-has the input focus, it will interpret subsequent
-keystrokes as window manager commands.)
-Even when you remove the <INTERFACE>Window Menu</INTERFACE>, the icon will
-retain the focus (and remain highlighted). When you direct focus to another
-window (or icon), the icon label will become normal again.
-</PARA>
-<FIGURE ID="FG-1015-3-6">
-<TITLE>Raising an icon</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.06.eps" ID="GC-1015-3-6"></GRAPHIC>
-</FIGURE>
-</SECT3>
-<SECT3 ID="S3-1015-3-5"><TITLE>Moving a Window</TITLE>
-<INDEXTERM ID="IX-1015-3-40"><PRIMARY>windows</PRIMARY><SECONDARY>moving</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-41"><PRIMARY>title area</PRIMARY><SECONDARY>mwm frame</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-42"><PRIMARY>mwm (Motif window manager)</PRIMARY><SECONDARY>frame;title area</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-43"><PRIMARY>moving</PRIMARY><SECONDARY>windows</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-44"><PRIMARY>titlebar</PRIMARY><SECONDARY>and moving windows</SECONDARY></INDEXTERM>
-<PARA>In many cases you'll want to move a window from one location on the
-display to another.
-The largest part of
-the titlebar is known as the <FIRSTTERM>title area</FIRSTTERM>, primarily because it
-displays the name of the application.
-The title area allows you to move the window, using the following steps:
-</PARA>
-<ORDEREDLIST NUMERATION="ARABIC">
-<LISTITEM>
-<PARA>Place the pointer within the title area. The pointer changes to the
-arrow cursor.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Press and hold down the first pointer button.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Move the window by dragging the pointer.
-<XREF LINKEND="FG-1015-3-7">Figure 3-7</XREF>
-shows a window
-being moved in this way. When you begin to move the window,
-the pointer changes to a cross arrow pointer and a window outline appears.
-This outline tracks the pointer's movement.
-In the center of the screen, a small, rectangular box also appears,
-displaying the x and y coordinates of the window as you move it.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Drag the cross arrow pointer with the window outline to the desired location
-on your screen.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Release the first pointer button. The window will move to the
-selected location.
-</PARA></LISTITEM>
-</ORDEREDLIST>
-<FIGURE ID="FG-1015-3-7">
-<TITLE>Moving a window by dragging the title area</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.07.eps" ID="GC-1015-3-7"></GRAPHIC>
-</FIGURE>
-<PARA>With the default configuration
-of <COMMAND>mwm</COMMAND>, moving a window also selects that window as the active
-or focus window.
-</PARA>
-</SECT3>
-<SECT3 ID="S3-1015-3-6"><TITLE>Moving an Icon</TITLE>
-<INDEXTERM ID="IX-1015-3-45"><PRIMARY>icons</PRIMARY><SECONDARY>moving</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-46"><PRIMARY>moving</PRIMARY><SECONDARY>icons</SECONDARY></INDEXTERM>
-<PARA>Moving an icon is similar to moving a window. To move an icon:
-</PARA>
-<ORDEREDLIST NUMERATION="ARABIC">
-<LISTITEM>
-<PARA>Place the pointer on the icon.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Press the first pointer button.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Move the icon by dragging the pointer.
-<XREF LINKEND="FG-1015-3-8">Figure 3-8</XREF>
-shows an icon
-being moved in this way. When you begin to move the icon,
-the pointer changes to a cross arrow pointer and an icon outline appears.
-This outline tracks the pointer's movement.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Drag the cross arrow pointer with the icon outline to the desired location
-on your screen.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Release the first pointer button. The icon will move to the
-selected location.
-</PARA></LISTITEM>
-</ORDEREDLIST>
-<PARA>With the default configuration
-of <COMMAND>mwm</COMMAND>, moving an icon also selects that icon to receive the
-input focus.
-</PARA>
-<FIGURE ID="FG-1015-3-8">
-<TITLE>Dragging an icon to a new location</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.08.eps" ID="GC-1015-3-8"></GRAPHIC>
-</FIGURE>
-<INDEXTERM ID="IX-1015-3-47" SPAN="END"><PRIMARY>mwm (Motif window manager)</PRIMARY></INDEXTERM>
-</SECT3></SECT2>
-<SECT2 ID="S2-1015-3-3"><TITLE>Resizing a Window</TITLE>
-<INDEXTERM ID="IX-1015-3-48"><PRIMARY>windows</PRIMARY><SECONDARY>resizing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-49"><PRIMARY>resizing windows</PRIMARY><SECONDARY>using pointer</SECONDARY></INDEXTERM>
-<PARA>One of the most distinctive and useful features of the <COMMAND>mwm</COMMAND> window
-frame is not at all obvious. The entire frame (other than the titlebar--i.e.,
-the title area and command buttons)
-is designed to allow you to resize the window using the pointer.
-Notice that the frame is divided by small lines
-into eight sections: four long
-borders (two horizontal and two vertical) and four
-corners.
-<XREF LINKEND="FG-1015-3-9">Figure 3-9</XREF>
-shows these sections of the window frame.
-</PARA>
-<PARA>You can resize a window horizontally, vertically, or simultaneously in
-both directions.
-Resizing is a bit trickier than any of the other window management
-functions we've tried, since the way you move the pointer determines
-the size of the window. It will probably take some practice.
-</PARA>
-<PARA>If you place the pointer within a window and then move it into one of
-the long horizontal or vertical borders,
-you'll notice the pointer changes to a new shape:
-an arrow (pointing toward the window border), with a short line perpendicular
-to it. This short line
-represents the window border. Try moving the pointer in this fashion
-in one of the windows on your display to get a better idea of what the
-pointer looks like.
-If you move the pointer from within a window into the outer border at
-one of the corners,
-the pointer will become an arrow pointing diagonally at a small
-corner symbol, as pictured in
-<XREF LINKEND="FG-1015-3-10">Figure 3-10</XREF>.
- <XREF LINKEND="FG-1015-3-11">Figure 3-11</XREF>
- shows all of the possible resize pointers.
-</PARA>
-<FIGURE ID="FG-1015-3-9">
-<TITLE>The outer frame is divided into four long borders and four corners</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.09.eps" ID="GC-1015-3-9"></GRAPHIC>
-</FIGURE>
-<FIGURE ID="FG-1015-3-10">
-<TITLE>Window with resizing pointer</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.10.eps" ID="GC-1015-3-10"></GRAPHIC>
-</FIGURE>
-<FIGURE ID="FG-1015-3-11">
-<TITLE>Resizing pointer symbols</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.11.eps" ID="GC-1015-3-11"></GRAPHIC>
-</FIGURE>
-<PARA>Once the pointer changes to one of these shapes, you can move the
-border (or corner) of the window. Resizing from one of the long borders
-only allows you to change one dimension of the window: a horizontal
-border can only be moved up or down, changing the height; a
-vertical border can only be moved left or right, changing the width.
-</PARA>
-<PARA>Resizing from a corner offers the most flexibility. You can move a
-corner in any direction you choose, changing both dimensions of the
-window if you want. For example, you can drag the lower-right corner of
-a window down and to the right to enlarge the window in both dimensions.
-</PARA>
-<PARA>You determine the size and shape of the window by choosing the border or corner
-you want to extend (or contract) and moving it the desired amount using
-the following steps:
-</PARA>
-<ORDEREDLIST NUMERATION="ARABIC">
-<LISTITEM>
-<PARA>Move the pointer from within the window to the border or corner you want
-to move. The pointer changes to one of the symbols pictured in
-<XREF LINKEND="FG-1015-3-11">Figure 3-11</XREF>.
-
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Press and hold down the first pointer button and drag the window border
-or corner in the direction you want. As you resize the window, an
-image of the moving border(s) tracks the pointer movement. Also, in the
-center of the display, a small rectangular window shows the dimensions
-of the window as they change (in characters and lines for <COMMAND>xterm</COMMAND>
-windows, in pixels for most other clients).
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Resize the window as desired.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Release the first pointer button. The window is redisplayed in the
-new shape. (The border image and window geometry tracking box disappear.)
-</PARA></LISTITEM>
-</ORDEREDLIST>
-<PARA><XREF LINKEND="FG-1015-3-12">Figure 3-12</XREF>
-shows a window being “stretched” from the lower-right corner.
-</PARA>
-<PARA>Note that resizing an <COMMAND>xterm</COMMAND> window will not change the dimensions of
-the text currently in the window. If you make the window smaller,
-for instance, some of the text may be obscured. On most operating
-systems, this should not be a problem. As you continue to work, perhaps
-starting a text editor, the
-text will be adjusted to display in the newly sized window.
-Problems are more likely to
-occur if you resize a window <EMPHASIS>during</EMPHASIS> a text
-editing session. It's likely that the
-text editing program will not
-know about the window's new size and will operate incorrectly.
-To solve this problem,
-simply quit out of the editor
-and start another session.
-</PARA>
-<FIGURE ID="FG-1015-3-12">
-<TITLE>Dragging the corner to make a window larger</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.12.eps" ID="GC-1015-3-12"></GRAPHIC>
-</FIGURE>
-<PARA>If your resized <COMMAND>xterm</COMMAND> window does not seem to know its new
-size, you may be working with an operating system that does not support
-terminal resizing capabilities. Refer to the discussion of the
-<COMMAND>resize</COMMAND> client in &cmtf05;,
-and to the <COMMAND>resize</COMMAND> reference page in Part Three of this guide
-for alternative solutions.
-</PARA>
-</SECT2>
-<SECT2 ID="S2-1015-3-4"><TITLE>Closing a Window: The Window Menu Button</TITLE>
-<INDEXTERM ID="IX-1015-3-50" SPAN="START"><PRIMARY>menus</PRIMARY><SECONDARY>Window Menu (mwm)</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-51"><PRIMARY>Window Menu</PRIMARY><SECONDARY>command button</SECONDARY></INDEXTERM>
-<PARA>The command button on the left side of the titlebar is used to bring up
-the <INTERFACE>Window Menu</INTERFACE>, which provides seven items that
-can be used to manage the window and its icon.
-&cmtf04;, describes how to
-bring up the <INTERFACE>Window Menu</INTERFACE> and invoke its various functions.
-</PARA>
-<PARA>This command button also has another function.
-Double-clicking the first pointer button on the
-<INDEXTERM ID="IX-1015-3-52"><PRIMARY>windows</PRIMARY><SECONDARY>killing;with Window Menu button</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-53"><PRIMARY>killing</PRIMARY><SECONDARY>windows</SECONDARY></INDEXTERM>
-<INTERFACE>Window Menu</INTERFACE> command button kills the client program
-and closes the window.
-Be aware, however, that like other methods of “killing” a program (such as the
-<COMMAND>xkill</COMMAND> client),
-double-clicking on the <INTERFACE>Window Menu</INTERFACE> button
-can adversely affect underlying processes.
-Refer to the
-section on <COMMAND>xkill</COMMAND> in &cmtf08;,
-for a more complete discussion of the hazards of killing a client and a
-summary of alternatives.
-</PARA>
-<PARA>You can customize <COMMAND>mwm</COMMAND> so that double clicking performs no
-function by setting a resource variable, <COMPUTEROUTPUT>wMenuButtonClick2</COMPUTEROUTPUT>, to
-false. See the sections “Setting mwm Resources” and
-“mwm-Specific Appearance and Behavior Resources” in Chapter 13,
-and the <COMMAND>mwm</COMMAND> reference page in Part Three of this guide for details.
-<INDEXTERM ID="IX-1015-3-54" SPAN="END"><PRIMARY>windows</PRIMARY><SECONDARY>creating</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-55" SPAN="END"><PRIMARY>menus</PRIMARY><SECONDARY>Window Menu (mwm)</SECONDARY></INDEXTERM>
-</PARA>
-</SECT2></SECT1>
-<SECT1 ID="S1-1015-3-2"><TITLE>Exiting from an xterm Window</TITLE>
-<INDEXTERM ID="IX-1015-3-56"><PRIMARY>xterm (terminal emulator)</PRIMARY><SECONDARY>terminating</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-57"><PRIMARY>terminating xterm window</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-58"><PRIMARY>killing</PRIMARY><SECONDARY>windows</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-59"><PRIMARY>windows</PRIMARY><SECONDARY>exiting xterm</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-60"><PRIMARY>windows</PRIMARY><SECONDARY>closing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-61"><PRIMARY>exiting</PRIMARY><SECONDARY>xterm window</SECONDARY></INDEXTERM>
-<PARA>When you are finished using an <COMMAND>xterm</COMMAND> window, you can
-remove it by typing whatever command you usually use to log
-off your system. Typically, this might be <COMMAND>exit</COMMAND>
-or Control-D. We'll close the second <COMMAND>xterm</COMMAND> window in
-<XREF LINKEND="FG-1015-3-13">Figure 3-13</XREF>
-by typing <COMMAND>exit</COMMAND>.
-</PARA>
-<PARA>Notice that when we terminate the second <COMMAND>xterm</COMMAND> window,
-the first <COMMAND>xterm</COMMAND> window takes over the input focus.
-When explicit focus is being used and a window is terminated,
-the input focus reverts to the window that previously had the focus.
-</PARA>
-<PARA>Be aware that terminating the login <COMMAND>xterm</COMMAND> window (the first
-<COMMAND>xterm</COMMAND> to appear) kills the X server and all associated clients.
-(If <COMMAND>xdm</COMMAND> is running X, the server will be reset but only after
-all client processes have been killed.) Be sure to terminate all
-other <COMMAND>xterm</COMMAND> windows before terminating the <COMMAND>xterm</COMMAND> login
-window. Also, if you are in an editor such as <COMMAND>vi</COMMAND>, be sure
-to save your data before you terminate the window.
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-62"><PRIMARY>windows</PRIMARY><SECONDARY>iconifying</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-63"><PRIMARY>iconifying windows</PRIMARY></INDEXTERM>
-In fact, it may be wise to iconify the login window
-and use other <COMMAND>xterm</COMMAND> windows instead, so that you
-don't inadvertently terminate it. Remember: you iconify a window by
-placing the pointer on the Minimize command button on the frame and
-clicking the first pointer button.
-</PARA>
-<PARA>If you are worried about typing Control-D (end-of-file) accidentally
-and you normally use the C shell (<COMMAND>csh</COMMAND>), you can enter:
-</PARA>
-<SCREEN ID="SC-1015-3-2"><PROMPT>%</PROMPT> <USERINPUT>set ignoreeof</USERINPUT>
-</SCREEN>
-<PARA>in the login window. Then typing <COMMAND>exit</COMMAND> becomes the only way you can
-terminate the window.
-</PARA>
-<PARA>Note that some C shell
-implementations have an <RESOURCE>autologout</RESOURCE> variable, which will
-automatically terminate the shell if there is no activity for a given
-period of time.
-If your C shell supports this feature, be sure to disable it
-in the login <COMMAND>xterm</COMMAND> window using this command:
-</PARA>
-<SCREEN ID="SC-1015-3-3"><PROMPT>%</PROMPT> <USERINPUT>unset autologout</USERINPUT>
-</SCREEN>
-<PARA>As an alternative to entering the command used to log off the system,
-you can also terminate an <COMMAND>xterm</COMMAND>
-window by selecting <INTERFACE>Send HUP Signal</INTERFACE>, <INTERFACE>Send TERM
-Signal</INTERFACE>, <INTERFACE>Send KILL Signal</INTERFACE>, or
-<INTERFACE>Quit</INTERFACE> from the <COMMAND>xterm</COMMAND> <INTERFACE>Main Options</INTERFACE> menu. (These menu options send
-different signals to the <COMMAND>xterm</COMMAND> process. Depending on what
-signals your operating system
-recognizes, some of the options may not
-work as intended. See Chapter 5 for more information.)
-</PARA>
-<FIGURE ID="FG-1015-3-13">
-<TITLE>Closing an xterm window</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.13.eps" ID="GC-1015-3-13"></GRAPHIC>
-</FIGURE>
-<PARA>The <COMMAND>mwm</COMMAND> window manager also provides several ways
-to remove an <COMMAND>xterm</COMMAND> or any other client window, among them
-double-clicking on the Window Menu command button, as described
-previously. Additional methods are described in &cmtf04;.
-</PARA>
-</SECT1>
-<SECT1 ID="S1-1015-3-3"><TITLE>Starting Additional Clients</TITLE>
-<INDEXTERM ID="IX-1015-3-64" SPAN="START"><PRIMARY>clients</PRIMARY><SECONDARY>starting additional</SECONDARY></INDEXTERM>
-<PARA>Now that you know the basics of managing windows,
-you can start other X clients just like you can start another instance
-of <COMMAND>xterm</COMMAND>. The following sections describe how
-to open more client windows, place them on the display in
-convenient positions, and take advantage of X's networking
-capabilities by running clients on other machines.
-</PARA>
-<PARA>To start a client,
-at the command-line prompt in any <COMMAND>xterm</COMMAND> window,
-type the name of the client followed by an ampersand () to make the
-client run in the background. For example, by typing:
-</PARA>
-<SCREEN ID="SC-1015-3-4"><PROMPT>%</PROMPT> <USERINPUT>oclock </USERINPUT>
-</SCREEN>
-<INDEXTERM ID="IX-1015-3-65"><PRIMARY>oclock (analog clock)</PRIMARY></INDEXTERM>
-<PARA>you can start a clock application.
-The clock will appear in the upper-left quarter of the screen.
-With non-rectangular windows like <COMMAND>oclock</COMMAND>, a titlebar appears to
-float above the window.
-You can then drag the <COMMAND>oclock</COMMAND> window to a more convenient location--say
-the upper-right corner, as in
-<XREF LINKEND="FG-1015-3-14">Figure 3-14</XREF>.
-(Remember, to move a window, place the pointer on the title area,
-press the first button, drag the window outline to the desired
-location, and release the button. Notice that the outline is
-rectangular, even if the <COMMAND>oclock</COMMAND> window isn't!)
-</PARA>
-<FIGURE ID="FG-1015-3-14">
-<TITLE>The oclock window</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.14.eps" ID="GC-1015-3-14"></GRAPHIC>
-</FIGURE>
-<PARA>Though moving windows on the display is fairly simple, manually positioning
-every window is not particularly convenient.
-For most clients, X provides a way to specify a window's location (and also
-its size) automatically--using an option when you run the command.
-A window's size and position is referred to as its <FIRSTTERM>geometry</FIRSTTERM> and
-you set these attributes using the <OPTION>-geometry</OPTION> option.
-The use of this option is discussed in the section “Window Geometry:
-Specifying Size and Location,” later in this chapter.
-</PARA>
-<PARA>Unfortunately the developers of <COMMAND>oclock</COMMAND> neglected to provide an
-easy way to remove it. For instructions on removing an <COMMAND>oclock</COMMAND>
-window, see &cmtf08;.
-<INDEXTERM ID="IX-1015-3-66"><PRIMARY>oclock (analog clock)</PRIMARY><SECONDARY>removing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-67"><PRIMARY>killing</PRIMARY><SECONDARY>clients</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-68"><PRIMARY>windows</PRIMARY><SECONDARY>removing</SECONDARY></INDEXTERM>
-</PARA>
-<SECT2 ID="S2-1015-3-5"><TITLE>Command-line Options</TITLE>
-<INDEXTERM ID="IX-1015-3-69"><PRIMARY>clients</PRIMARY><SECONDARY>options</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-70"><PRIMARY>command-line options</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-71"><PRIMARY>options</PRIMARY><SECONDARY>client</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-72" SPAN="START"><PRIMARY>-geometry option (X Toolkit)</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-73"><PRIMARY>-display option</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-74"><PRIMARY>command-line options</PRIMARY><SECONDARY>-display</SECONDARY></INDEXTERM>
-<PARA>Most X clients accept two powerful and extremely useful options: the
-<OPTION>-geometry</OPTION> option, which allows you to specify the size and
-location of a window on the screen; and the <OPTION>-display</OPTION> option,
-which allows you to specify on which
-screen a window should be created. (Most commonly, you'd
-use the <OPTION>-display</OPTION> option to run a client on a remote machine
-and display the window locally, that is, on your display.)
-</PARA>
-<PARA>The next few sections illustrate some typical uses of these important
-options. In explaining how to use them, we introduce some new,
-perhaps somewhat involved concepts (such as the way distances can be
-measured on your screen). Bear with us. We feel that you need to master
-the <OPTION>-geometry</OPTION> and <OPTION>-display</OPTION> options in order
-to begin to take advantage of the powers of X.
-</PARA>
-<PARA>After explaining these options in detail, we'll briefly consider
-some of the characteristics you can specify using other common options.
-</PARA>
-<SECT3 ID="S3-1015-3-7"><TITLE>Window Geometry: Specifying Size and Location</TITLE>
-<INDEXTERM ID="IX-1015-3-75" SPAN="START"><PRIMARY>windows</PRIMARY><SECONDARY>geometry</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-76" SPAN="START"><PRIMARY>windows</PRIMARY><SECONDARY>size and location</SECONDARY></INDEXTERM>
-<PARA>The command-line option to specify a window's size and location has
-the form:
-</PARA>
-<SCREEN ID="SC-1015-3-5">-geometry <VARPARAM>geometry</VARPARAM>
-</SCREEN>
-<PARA>The <OPTION>-geometry</OPTION> option can be (and often is) abbreviated as
-<OPTION>-g</OPTION>, unless the client accepts another option that begins
-with “g.”
-</PARA>
-<PARA>The parameter to the geometry option (<VARPARAM>geometry</VARPARAM>), referred to
-as the “standard geometry string,” has four numerical components,
-two specifying the window's dimensions and two specifying its
-location. The standard geometry string has the syntax:
-</PARA>
-<SCREEN ID="SC-1015-3-6"><VARPARAM>width</VARPARAM>x<VARPARAM>height</VARPARAM>±<VARPARAM>xoff</VARPARAM>±<VARPARAM>yoff</VARPARAM>
-</SCREEN>
-<PARA>Obviously,
-the first half of the string provides the <VARPARAM>width</VARPARAM> and <VARPARAM>height</VARPARAM>
-of the window. Many application windows are measured in pixels.
-However, application developers are encouraged to use units that are
-meaningful in terms of the application.
-For example, <COMMAND>xterm</COMMAND>'s dimensions are measured in columns and rows
-of font characters. More precisely, an <COMMAND>xterm</COMMAND> window is some
-number of characters wide by some number of lines high (80 characters wide by
-24 lines high by default).
-</PARA>
-<PARA>The second half of the geometry string gives the location of the window
-relative to the horizontal and vertical edges of the screen.
-Imagining the screen to be a grid (where the upper-left corner is 0,0),
-<VARPARAM>xoff</VARPARAM> (x offset) and <VARPARAM>yoff</VARPARAM> (y offset) represent the
-x and y coordinates at which the window should be displayed.
-The x and y offsets are measured in pixels.
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-77"><PRIMARY>pixels</PRIMARY></INDEXTERM>
-Many users may not be accustomed to thinking in terms of pixels.
-What exactly is a pixel? A pixel is
-the smallest element of a display surface that can be addressed by a
-program. You can think of a pixel as one of the tiny dots that make
-up a graphic image, such as that displayed by a terminal or a
-television.
-The number of dots (or pixels) per inch of screen determines the
-screen's <FIRSTTERM>resolution</FIRSTTERM>.<FOOTNOTEREF LINKEND="FN-1015-3-3"></FOOTNOTEREF>The more dots per inch,
-the higher the resolution (and, hypothetically, the sharper the picture).<FOOTNOTEREF LINKEND="FN-1015-3-4"></FOOTNOTEREF>
-<FOOTNOTE ID="FN-1015-3-3">
-<PARA>Hardware manufacturers generally equate resolution with the screen's
-overall dimensions in pixels. Thus, you also need to know the actual
-physical size of the monitor (in inches) to determine the dots per inch.
-We find the dpi figure more useful.
-</PARA>
-</FOOTNOTE>
-<FOOTNOTE ID="FN-1015-3-4">
-<PARA>There are other factors that determine the “picture quality” of
-a monitor, including “depth,” or the number of bits per pixel.
-Depth relates to how many colors a monitor can display.
-See “How Many Colors are Available on My Screen?”in &cmtf12;, for more information.
-</PARA>
-</FOOTNOTE>
-</PARA>
-<PARA>Since a pixel is a tiny unit of measurement, gauging sizes and
-distances in pixels will take some practice.
-For instance, what are the dimensions of your screen in pixels (its
-resolution)?
-The <COMMAND>xdpyinfo</COMMAND> client, described in Chapter 8, will tell you this;
-your workstation or X terminal documentation may also provide this information.
-<COMMAND>xdpyinfo</COMMAND> also tells you the screen's resolution in dots per inch.
-</PARA>
-<PARA>Keep in mind that monitors can vary substantially. The Sun 19-inch monitor
-has dimensions of 1152 × 900 pixels and a resolution of 90 × 90 dots per inch
-(commonly abbreviated to dpi). The NCD 16-inch X terminal has
-dimensions of 1024 × 1024 pixels and a resolution of 106 × 106 dpi.
-</PARA>
-<PARA>What are the implications of such hardware differences in specifying
-client geometry?
-The size and location of client windows is related to
-the size and resolution of your screen.
-For example, if you specify a window with dimensions of 125 × 125 pixels,
-it will appear somewhat larger on the Sun monitor than on the NCD X
-terminal.
-</PARA>
-<PARA>So how do we use the geometry option to specify
-a window's size and location?
-First, be aware that
-you can specify any or all elements of the geometry string.
-Incomplete geometry specifications are compared to the application's
-default settings and missing elements are supplied by these values.
-All client windows have a default size.
-For example, if you run an <COMMAND>xterm</COMMAND> window with the geometry
-option and specify a location but no
-dimensions, the application default size of 80 characters by 24 lines is used.
-</PARA>
-<PARA>If you don't specify the x and y coordinates at which to place a
-client window, the client may provide a default location; if the
-application doesn't provide a default and <COMMAND>mwm</COMMAND> is
-running, the window manager will automatically position the window in the
-upper-left quarter of the screen.
-</PARA>
-<PARA>For now, let's just specify a window's location and let the size be
-the application default.
-The x and y offsets can be either positive or negative.
-If you specify positive offsets, you're positioning the left side
-and top side of the window. Negative offsets are interpreted
-differently.
-The possible values for the x and y offsets and their effects are shown in
-<XREF LINKEND="TB-1015-3-1">Table 3-1</XREF>.
-</PARA>
-<TABLE ID="TB-1015-3-1"><TITLE>Geometry Specification x and y Offsets</TITLE>
-<GRAPHIC FORMAT="tbl" FILEREF="tbl/3-1.tbl" ID="GC-1015-3-15"></GRAPHIC>
-</TABLE>
-<PARA>For example, the command line:
-</PARA>
-<SCREEN ID="SC-1015-3-7"><PROMPT>%</PROMPT> <USERINPUT>xclock -geometry -10+10 </USERINPUT>
-</SCREEN>
-<PARA>places a clock of the default size in the upper-right corner of the
-display, 10 pixels from the right and top edges of the screen.
-</PARA>
-<PARA>To place a window in any of the four corners of the screen, flush
-against its boundaries, use the following x and y offsets.
-<TABLE ID="TB-1015-3-2">
-<GRAPHIC FORMAT="tbl" FILEREF="tbl/3-2.tbl" ID="GC-1015-3-16"></GRAPHIC>
-</TABLE>
-</PARA>
-<PARA>If you want a window placed away from one or both edges of the
-screen, the guesswork starts.
-How many pixels away from the left side of the screen? How many
-pixels down from the top? You'll have to experiment with placing some
-clients on your screen to get a better idea of x and y offsets.
-</PARA>
-<PARA>It's actually a good idea to start some windows and move them around on
-your screen using the pointer. While you're dragging a window,
-check the x and y offsets displayed
-in the small box <COMMAND>mwm</COMMAND> places in the center of the screen.
-These coordinates are
-the positive x and y offsets of the window (i.e., the offsets relative
-to the upper-left corner
-of the screen). This method for gauging location is fairly reliable.<FOOTNOTEREF LINKEND="FN-1015-3-5"></FOOTNOTEREF>
-<FOOTNOTE ID="FN-1015-3-5">
-<PARA>There seems to be a very slight delay between
-pointer motion and update to the <COMMAND>mwm</COMMAND> coordinate box.
-When you finish dragging the window, the last coordinates visible in the box
-may differ from the true coordinates by a pixel in either or both directions.
-But this variance is
-so trivial that you can supply the coordinates as part of the geometry
-string and come very close.
-</PARA>
-</FOOTNOTE>
-</PARA>
-<PARA>You can also place some windows in different places by dragging and
-then determine their geometry specifications
-using the <COMMAND>xwininfo</COMMAND> client, described in &cmtf08;.
-Note that when <COMMAND>mwm</COMMAND> is running, you should
-use <COMMAND>xwininfo</COMMAND> with the <OPTION>-frame</OPTION> option.
-</PARA>
-<PARA>Now what about the size of a window?
-For <COMMAND>xterm</COMMAND>, the size of the window is measured in
-characters and lines (by default 80 characters by 24
-lines). If you want to use a large VT100 window,
-say 100 characters wide by
-30 lines long, you could use this geometry specification:
-</PARA>
-<SCREEN ID="SC-1015-3-8"><PROMPT>%</PROMPT> <USERINPUT>xterm -geometry 100x30-0-0 </USERINPUT>
-</SCREEN>
-<PARA>This command creates a large <COMMAND>xterm</COMMAND> window in the lower-right
-corner of the screen, as illustrated by
-<XREF LINKEND="FG-1015-3-15">Figure 3-15</XREF>.
-</PARA>
-<FIGURE ID="FG-1015-3-15">
-<TITLE>xterm window sized and positioned with the -geometry option</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.15.eps" ID="GC-1015-3-17"></GRAPHIC>
-</FIGURE>
-<PARA>As stated previously,
-most of the standard clients (other than <COMMAND>xterm</COMMAND>) are measured in
-pixels. For example, <COMMAND>xclock</COMMAND> is 164 pixels square by default
-(exclusive of the <COMMAND>mwm</COMMAND> frame).
-A client's default dimensions may appear on its reference page in Part
-Three of this guide. However, you'll probably need to experiment with
-specifying sizes (as well as locations) on your display. (See
-&cmtf08;, and the client reference page, for more about <COMMAND>xclock</COMMAND>.)
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-78"><PRIMARY>resource variables</PRIMARY><SECONDARY>specifying window size and location</SECONDARY></INDEXTERM>
-Be aware that the geometry option is not necessarily the only means
-available to specify window size and location.
-Several clients, including <COMMAND>xterm</COMMAND>, allow you
-to set the size and
-location of a window (and often its icon or an alternate window) using
-resource variables
-<INDEXTERM ID="IX-1015-3-79"><PRIMARY>variables</PRIMARY><SECONDARY>resource</SECONDARY><SEE>resource variables</SEE></INDEXTERM>
-(in an <FILENAME>.Xresources</FILENAME> or other defaults file).
-We'll introduce some of the basics of specifying
-resources later in this chapter. See &cmtf11;,
-for more detailed instructions.
-See the appropriate
-client reference pages in Part Three of
-this guide for a complete list
-of available resources.
-</PARA>
-<PARA>You should be aware that, as with all user preferences, you may not
-always get exactly what you ask for. Clients are designed to work
-with a window manager, which may have its own rules for window or icon
-size and placement. However, priority is always given to specific
-user requests, so you won't often be surprised.
-<INDEXTERM ID="IX-1015-3-80" SPAN="END"><PRIMARY>windows</PRIMARY><SECONDARY>geometry</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-81" SPAN="END"><PRIMARY>windows</PRIMARY><SECONDARY>size and location</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-82" SPAN="END"><PRIMARY>-geometry option (X Toolkit)</PRIMARY></INDEXTERM>
-</PARA>
-</SECT3>
-<SECT3 ID="S3-1015-3-8"><TITLE>Running a Client on Another Machine: Specifying the Display</TITLE>
-<INDEXTERM ID="IX-1015-3-83"><PRIMARY>remote system</PRIMARY><SECONDARY>running client on</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-84"><PRIMARY>network</PRIMARY><SECONDARY>running client over</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-85"><PRIMARY>clients</PRIMARY><SECONDARY>display options</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-86"><PRIMARY>clients</PRIMARY><SECONDARY>running on another machine</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-87"><PRIMARY>clients</PRIMARY><SECONDARY>options</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-88"><PRIMARY>command-line options</PRIMARY><SECONDARY>-display</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-89"><PRIMARY>-display option</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-90"><PRIMARY>DISPLAY environment variable</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-91"><PRIMARY>options</PRIMARY><SECONDARY>command-line</SECONDARY><SEE>command-line options</SEE></INDEXTERM>
-<PARA>We have yet to take advantage of X's networking capabilities.
-Remember that X allows you to run a client on a remote machine across a network.
-Generally, the results of a client program are displayed on a screen
-connected to the system where the client is running.
-However, if you are running a client on a remote system, you probably
-want to see the results on your own display (connected to a local server).
-</PARA>
-<PARA>Running a client on a remote machine may give you access to different
-software, it may increase the efficiency of certain processes, or
-benefit you in a number of other ways.
-We discussed some of the advantages of running a
-client on a remote machine in &cmtf01;. See the section
-“X Architecture Overview” for details.
-</PARA>
-<PARA>But how does running a client on a remote system affect how you work with
-the X display? Once a client is running, it doesn't.
-You can display the application window
-on your own screen, enter input using
-your own keyboard and pointer, and read the client's output in the
-window on your screen--all while the actual client process occurs on
-another machine.
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-92"><PRIMARY>-display option</PRIMARY></INDEXTERM>
-In order to run a
-client remotely and display its results locally,
-you must tell the client process where to display its window.
-For this purpose, X provides a command-line option: <OPTION>-display</OPTION>.
-Think of <OPTION>-display</OPTION> as a pointer to the physical display on
-which you want the window to appear.
-Like
-<OPTION>-geometry</OPTION>, the <OPTION>-display</OPTION> option is recognized by most X
-clients. The display option tells the client on which server to
-display results (i.e., create its window). The option has the syntax:
-</PARA>
-<SCREEN ID="SC-1015-3-9"><OPTION>-display</OPTION> <OPTIONAL><VARPARAM>host</VARPARAM></OPTIONAL>:<VARPARAM>server</VARPARAM><OPTIONAL>.<VARPARAM>screen</VARPARAM></OPTIONAL>
-</SCREEN>
-<PARA>The <OPTION>-display</OPTION> option can be abbreviated as <OPTION>-d</OPTION>,
-unless the client accepts another option that begins with “d.”
-</PARA>
-<PARA>The argument to the <OPTION>-display</OPTION> option is a three-component
-<FIRSTTERM>display name</FIRSTTERM>.
-The <VARPARAM>host</VARPARAM> specifies the machine on which to create the window,
-the <VARPARAM>server</VARPARAM>
-specifies the server number, and the <VARPARAM>screen</VARPARAM>
-specifies the screen number.
-</PARA>
-<PARA>In this context, “host” refers to the Internet address name of the
-display hardware. It might be the
-name of a single-user workstation, an X terminal, a PC running an X
-server, or another hardware device.
-</PARA>
-<PARA>“Server” refers to an instance of the X server program, which controls
-a single physical display.
-An X display may be composed of multiple screens, but the screens share
-one keyboard and pointer. Most workstations have only one keyboard
-and pointer and thus are classified as having only one display.
-Multiuser systems may have multiple independent displays, each
-running a server program. If one display exists, as in the case of
-most workstations and X terminals,
-it is numbered 0; if a machine
-has several displays, each
-is assigned a number (beginning with 0) when the X server for that
-display is started.
-</PARA>
-<PARA>Similarly, if a single display is composed of multiple screens
-(sharing one keyboard and pointer), each
-screen is assigned a number (beginning with 0) when the server for that
-display is started. Multiple screen displays may be composed of
-two or more physical monitors.
-Alternatively, two screens might be defined as different ways of using
-the same physical monitor. For example, on the Sun-3/60 color workstation,
-screen 0 is color, and screen 1 is monochrome.
-Each screen is
-the size of the monitor; you can only view one screen at a time.
-In practice, the two screens seem to be side by side:
-you can “scroll” between them by moving the pointer off either
-horizontal edge of the screen.
-</PARA>
-<PARA>Note that the <VARPARAM>server</VARPARAM> parameter of the display option
-always begins with a colon (a double colon after a DECnet
-node<FOOTNOTEREF LINKEND="FN-1015-3-6"></FOOTNOTEREF>), and that
-the <VARPARAM>screen</VARPARAM> parameter always begins with a period.
-If the host is omitted or is
-specified as <RESOURCE>unix</RESOURCE>, the local machine is assumed.
-If the screen is omitted, screen 0 is assumed.
-<FOOTNOTE ID="FN-1015-3-6">
-<PARA>By convention, DECnet node names end with a colon.
-</PARA>
-</FOOTNOTE>
-</PARA>
-<PARA>Although much of the current X Window System documentation suggests that any of
-the parameters to the <OPTION>-display</OPTION> option can be omitted and will
-default to the local node, server and screen 0, respectively,
-we have not found this to be true.
-In our experience, only the <VARPARAM>host</VARPARAM> and <VARPARAM>screen</VARPARAM> parameters
-(and the period preceding <VARPARAM>screen</VARPARAM>)
-can be omitted. The colon and <VARPARAM>server</VARPARAM> are necessary in
-all circumstances.
-</PARA>
-</SECT3>
-<SECT3 ID="S3-1015-3-9"><TITLE>The DISPLAY Environment Variable</TITLE>
-<INDEXTERM ID="IX-1015-3-93"><PRIMARY>DISPLAY</PRIMARY><SECONDARY>environment variable</SECONDARY></INDEXTERM>
-<PARA>Technically speaking, the <OPTION>-display</OPTION> option allows you to
-override the contents of the DISPLAY environment variable,
-<INDEXTERM ID="IX-1015-3-94"><PRIMARY>display</PRIMARY><SECONDARY>name</SECONDARY>
-<TERTIARY>where stored</TERTIARY></INDEXTERM>
-which stores the display name on UNIX systems.
-On UNIX systems, the display name is stored in the DISPLAY
-environment variable.
-Clients running on the local system access this variable to determine
-which physical display to connect to (for most clients, “connecting”
-is equivalent to opening a window).
-The DISPLAY variable is set
-automatically by the <COMMAND>xterm</COMMAND> terminal emulator.
-Thus it is set when you start X and
-the first <COMMAND>xterm</COMMAND> window.
-</PARA>
-<PARA>For most single-user systems, such as workstations, <COMMAND>xterm</COMMAND> sets
-the server and screen numbers to 0, and either omits a
-hostname (the local host is assumed) or sets the hostname to “unix,” a generic
-name, which also defaults to the local host. If you are working on a
-single-user system and run all processes on it, you don't have to deal
-with issues concerning the display setting.
-Clients running locally access the DISPLAY variable and open
-windows on a display connected to the local host.
-</PARA>
-<PARA>If you are using an X terminal, it should already be
-configured so that the DISPLAY variable is set properly when
-you log on to the local host. Again, if you run all process on the
-local machine (to which your terminal is connected), you don't have to
-deal with specifying the display.
-Clients will access the DISPLAY variable and open windows on
-your X terminal screen.
-</PARA>
-<PARA>Complications arise when you want to run a process on a remote machine
-and display the results locally.
-A client running on a remote machine does not have access to the
-DISPLAY variable on the
-local machine. By default, a client
-running on a remote machine checks the DISPLAY setting on <EMPHASIS>that</EMPHASIS>
-machine.
-</PARA>
-<PARA>You can override the DISPLAY environment variable a client
-accesses by using the <OPTION>-display</OPTION> option when you run the command.
-</PARA>
-</SECT3>
-<SECT3 ID="S3-1015-3-10"><TITLE>Using -display</TITLE>
-<INDEXTERM ID="IX-1015-3-95"><PRIMARY>-display option</PRIMARY><SECONDARY>using</SECONDARY></INDEXTERM>
-<PARA>Say you're using a single display workstation and the display
-also has only one screen. The hostname of the workstation is <SYSTEMNAME>kansas</SYSTEMNAME>.
-In order to tell a client to connect to a display, you must
-identify it by its unique name on the network.
-(You cannot identify your display by the shorthand setting given to it by
-<COMMAND>xterm</COMMAND>--<LITERAL>unix:0.0</LITERAL>, <LITERAL>:0.0</LITERAL> or some variation.)
-Let's assume that the complete display name for the
-workstation <SYSTEMNAME>kansas</SYSTEMNAME> is:
-</PARA>
-<SCREEN ID="SC-1015-3-10">kansas:0.0
-</SCREEN>
-<PARA>Now let's say you want to run an <COMMAND>xterm</COMMAND> window on a
-faster system--let's call
-it <SYSTEMNAME>oz</SYSTEMNAME>--on your network. In order to run an <COMMAND>xterm</COMMAND> on
-<SYSTEMNAME>oz</SYSTEMNAME> but display the window on your screen connected to
-<SYSTEMNAME>kansas</SYSTEMNAME> (the local server), you would run the <COMMAND>xterm</COMMAND> command
-using a remote shell<FOOTNOTEREF LINKEND="FN-1015-3-7"></FOOTNOTEREF>
-(<COMMAND>rsh</COMMAND>):
-<INDEXTERM ID="IX-1015-3-96"><PRIMARY>rsh command</PRIMARY></INDEXTERM>
-</PARA>
-<SCREEN ID="SC-1015-3-11"><PROMPT>%</PROMPT> <USERINPUT>rsh oz xterm -display kansas:0.0 </USERINPUT>
-</SCREEN>
-<FOOTNOTE ID="FN-1015-3-7">
-<PARA>The command to run the remote process might be different depending
-on the available networking software. Ask your system administrator
-for the proper command.
-</PARA>
-</FOOTNOTE>
-<PARA>The <COMMAND>xterm</COMMAND> process runs on <SYSTEMNAME>oz</SYSTEMNAME>, but you've directed
-the client to use the display and screen numbered 0 on <SYSTEMNAME>kansas</SYSTEMNAME>,
-your local system.
-Notice that <COMPUTEROUTPUT>kansas:0.0</COMPUTEROUTPUT> is the complete display name.
-Hypothetically, if the workstation (<SYSTEMNAME>kansas</SYSTEMNAME>) has only one screen
-or it has multiple screens but
-you want to specify screen 0, you can omit the screen number
-and the preceding period (<COMPUTEROUTPUT>.0</COMPUTEROUTPUT>).
-</PARA>
-<PARA>Keep in mind that
-for this process to succeed, the remote system (<EMPHASIS>oz</EMPHASIS>) must have
-permission to “open” the local display (on <SYSTEMNAME>kansas</SYSTEMNAME>).
-(See “Server Access Control” in &amtfA;, and the <COMMAND>xhost</COMMAND>
-reference page in Part Three of this guide, for more information.)
-If <EMPHASIS>oz</EMPHASIS> has not been granted access to the server running on
-<SYSTEMNAME>kansas</SYSTEMNAME>, the window will not be opened, and you may also get
-an error message similar to:
-<INDEXTERM ID="IX-1015-3-97"><PRIMARY>Can't Open display</PRIMARY><SECONDARY>error message</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-98"><PRIMARY>error messages</PRIMARY><SECONDARY>Can't Open display</SECONDARY></INDEXTERM>
-</PARA>
-<SCREEN ID="SC-1015-3-12">Error: Can't Open display
-</SCREEN>
-<PARA>If your command fails, try entering the command:
-</PARA>
-<SCREEN ID="SC-1015-3-13"><PROMPT>%</PROMPT> <USERINPUT>xhost +</USERINPUT>
-</SCREEN>
-<PARA>in an <COMMAND>xterm</COMMAND> window running on your display. Then run the remote
-shell (<COMMAND>rsh</COMMAND>) again. If problems persist,
-consult your system administrator or &bmtf08;.
-</PARA>
-<PARA>The following command illustrates a common mistake:
-</PARA>
-<SCREEN ID="SC-1015-3-14"><PROMPT>%</PROMPT> <USERINPUT>rsh oz xterm </USERINPUT>
-</SCREEN>
-<PARA>If you try to run a client using a remote shell and forget to direct the
-client to create its window on your own display, the window
-will not be displayed and you'll get an error
-message stating that the display cannot be opened.
-</PARA>
-<PARA>If you're using an X terminal, it will have a name
-unique to the terminal (e.g., ncd8), which should be used
-as the <VARPARAM>host</VARPARAM> component of the <OPTION>-display</OPTION> argument.
-You should not use the name of the system to which the terminal is
-connected. When you run processes on that machine, you don't have to
-use <OPTION>-display</OPTION>. If you want to run a client on another machine
-on the network, you must use <OPTION>-display</OPTION> to point back at your
-terminal.
-</PARA>
-<PARA>Say we have a terminal with the full display name:
-</PARA>
-<SCREEN ID="SC-1015-3-15">ncd8:0.0
-</SCREEN>
-<PARA>connected to <SYSTEMNAME>kansas</SYSTEMNAME> and we want to run an <COMMAND>xterm</COMMAND> on
-<EMPHASIS>oz</EMPHASIS>. The command:
-</PARA>
-<SCREEN ID="SC-1015-3-16"><PROMPT>%</PROMPT> <USERINPUT>rsh oz xterm -display ncd8:0.0 </USERINPUT>
-</SCREEN>
-<PARA>will open the window on our X terminal.
-</PARA>
-<PARA>In addition to specifying a local display, if permissions allow
-you can also use the display option to open a window on someone else's
-display.
-You might want to display a window on another user's screen
-for instructional purposes.
-Multiuser systems can even be set up to allow teachers to display
-educational material simultaneously to
-several students, each using an X display of some sort.
-And, of course, you might want to display a window on a friend's
-screen, just for the fun of it.
-(The security problems that allow
-both innocent pranks like this, as well as more serious breaches, are
-described in &bmtf08;.)
-</PARA>
-<PARA>If you're working on <SYSTEMNAME>kansas</SYSTEMNAME> and you want
-to open an <COMMAND>xterm</COMMAND> window on the first display connected to <EMPHASIS>oz</EMPHASIS>,
-you could use the command:
-</PARA>
-<SCREEN ID="SC-1015-3-17"><PROMPT>%</PROMPT> <USERINPUT>xterm -display oz:0.0 </USERINPUT>
-</SCREEN>
-<PARA>Note that you can only open a window on another display if the
-server running that display permits your server access.
-(Access must be granted from the remote server, perhaps using <COMMAND>xhost</COMMAND>.)
-If <EMPHASIS>oz</EMPHASIS> does not allow <SYSTEMNAME>kansas</SYSTEMNAME> access, this
-command will fail and an error message will indicate that the display
-cannot be opened.
-</PARA>
-</SECT3>
-<SECT3 ID="S3-1015-3-11"><TITLE>Once You Run a Remote xterm Using -display</TITLE>
-<PARA>A less than obvious repercussion of using <OPTION>-display</OPTION> to run
-a remote <COMMAND>xterm</COMMAND> is that the option
-sets the DISPLAY variable for the new <COMMAND>xterm</COMMAND> window--and that
-DISPLAY setting is passed on to all child processes of the client.
-Therefore, once you run an <COMMAND>xterm</COMMAND> on a remote system and
-correctly specify your own display, you can run any number of clients
-from that <COMMAND>xterm</COMMAND> and they will all be displayed on your screen
-automatically (no <OPTION>-display</OPTION> option is necessary).
-</PARA>
-<PARA>In one of the examples in the preceding section, we ran an <COMMAND>xterm</COMMAND>
-on the remote system <EMPHASIS>oz</EMPHASIS>, specifying the local display
-<COMPUTEROUTPUT>kansas:0.0</COMPUTEROUTPUT> with the <OPTION>-display</OPTION> option.
-To query the contents of the
-DISPLAY variable in the resulting <COMMAND>xterm</COMMAND> (under the C
-shell), use the command:
-</PARA>
-<SCREEN ID="SC-1015-3-18"><PROMPT>%</PROMPT> <USERINPUT>echo $DISPLAY</USERINPUT>
-</SCREEN>
-<PARA>The system should echo:
-</PARA>
-<SCREEN ID="SC-1015-3-19"><PROMPT>%</PROMPT> kansas:0.0
-</SCREEN>
-<PARA>verifying that the display name has been passed to the DISPLAY
-variable in the new <COMMAND>xterm</COMMAND> window.
-You can then run any client you want on <EMPHASIS>oz</EMPHASIS> by entering the
-command in this <COMMAND>xterm</COMMAND> window and the window
-will automatically be displayed on
-<COMPUTEROUTPUT>kansas:0.0</COMPUTEROUTPUT>. The DISPLAY setting will also be passed to
-any children of <EMPHASIS>this</EMPHASIS> process as well, and will be propagated
-for any number of “generations.”
-</PARA>
-</SECT3>
-<SECT3 ID="S3-1015-3-12"><TITLE>Logging In to a Remote System</TITLE>
-<INDEXTERM ID="IX-1015-3-99"><PRIMARY>remote system</PRIMARY><SECONDARY>logging in to</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-100"><PRIMARY>DISPLAY environment variable</PRIMARY><SECONDARY>setting after remote login</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-101"><PRIMARY>rlogin</PRIMARY><SECONDARY>setting DISPLAY</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-102"><PRIMARY>telnet</PRIMARY><SECONDARY>setting DISPLAY</SECONDARY></INDEXTERM>
-<PARA>If you log in to a remote UNIX system using <COMMAND>rlogin</COMMAND> (or
-<COMMAND>telnet</COMMAND>) in an <COMMAND>xterm</COMMAND> window, it's a good idea to set the
-DISPLAY variable in the new shell to reflect your local
-display. Then if you run a client process from this window, the new
-window will be placed on your local display and the DISPLAY
-setting will be passed on to all child processes.
-</PARA>
-<PARA>When you set the DISPLAY variable from the command
-line, the syntax varies depending on the UNIX shell running. The
-following command sets the variable under the C shell.
-</PARA>
-<SCREEN ID="SC-1015-3-20"><PROMPT>%</PROMPT> <USERINPUT>setenv DISPLAY kansas:0.0</USERINPUT>
-</SCREEN>
-<PARA>To set the DISPLAY variable under the Bourne shell, use:
-</PARA>
-<SCREEN ID="SC-1015-3-21">$ <USERINPUT>DISPLAY=kansas:0.0; export DISPLAY</USERINPUT>
-</SCREEN>
-<INDEXTERM ID="IX-1015-3-103"><PRIMARY>DISPLAY environment variable</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-104"><PRIMARY>environment variables</PRIMARY><SECONDARY>DISPLAY</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-105"><PRIMARY>variables</PRIMARY><SECONDARY>environment</SECONDARY><SEE>environment variables</SEE></INDEXTERM>
-</SECT3>
-<SECT3 ID="S3-1015-3-13"><TITLE>Monitoring the Load on a Remote System</TITLE>
-<INDEXTERM ID="IX-1015-3-106"><PRIMARY>remote system</PRIMARY><SECONDARY>monitoring load on</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-107"><PRIMARY>load average</PRIMARY></INDEXTERM>
-<PARA>A client you may wish to run on another machine is
-<COMMAND>xload</COMMAND>, which is used to keep track of the system load average.
-<INDEXTERM ID="IX-1015-3-108"><PRIMARY>xload (poll system load average)</PRIMARY></INDEXTERM>
-By default, <COMMAND>xload</COMMAND> polls the system for the load
-average at ten-second intervals and displays the results in a simple
-histogram.
-</PARA>
-<PARA>If you are running processes on more than one machine, it's useful to
-gauge the level of activity on the systems in question.
-This information should help you judge when to start processes and
-monitor how your processes are impacting system resources.
-</PARA>
-<PARA>Say you're running clients both on the local machine
-<SYSTEMNAME>kansas</SYSTEMNAME> and on the remote machine <EMPHASIS>oz</EMPHASIS>. On the local display,
-you can have two <COMMAND>xload</COMMAND> windows, one showing activity on <SYSTEMNAME>kansas</SYSTEMNAME>
-and another showing activity on <EMPHASIS>oz</EMPHASIS>.
-</PARA>
-<PARA>To create an <COMMAND>xload</COMMAND> window monitoring activity on <SYSTEMNAME>kansas</SYSTEMNAME>, use the
-command:
-</PARA>
-<SCREEN ID="SC-1015-3-22"><PROMPT>%</PROMPT> <USERINPUT>xload </USERINPUT>
-</SCREEN>
-<PARA>Once the <COMMAND>xload</COMMAND> window is created, move it to a convenient
-location on the screen.
-</PARA>
-<PARA>Then run an <COMMAND>xload</COMMAND> process on <EMPHASIS>oz</EMPHASIS> using
-a remote shell and display the results in a window on
-<SYSTEMNAME>kansas</SYSTEMNAME>:
-</PARA>
-<SCREEN ID="SC-1015-3-23"><PROMPT>%</PROMPT> <USERINPUT>rsh oz xload -display kansas:0.0 </USERINPUT>
-</SCREEN>
-<PARA>The display option tells <COMMAND>xload</COMMAND> to create its window on the local
-display (<SYSTEMNAME>kansas</SYSTEMNAME>).
-Again, move the window using the pointer.
-</PARA>
-<PARA><XREF LINKEND="FG-1015-3-16">Figure 3-16</XREF>
-shows the resulting <SYSTEMNAME>kansas</SYSTEMNAME> display:
-two <COMMAND>xload</COMMAND> windows--the top window monitoring activity on the
-local system and the bottom one monitoring activity on the remote system.
-</PARA>
-<FIGURE ID="FG-1015-3-16">
-<TITLE>Monitoring activity on two systems with xload</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.16.eps" ID="GC-1015-3-18"></GRAPHIC>
-</FIGURE>
-<INDEXTERM ID="IX-1015-3-109" SPAN="END"><PRIMARY>clients</PRIMARY><SECONDARY>starting additional</SECONDARY></INDEXTERM>
-</SECT3></SECT2></SECT1>
-<SECT1 ID="S1-1015-3-4"><TITLE>Putting It All Together</TITLE>
-<PARA>Now that we've learned something about the tools of the display, how
-to size and position windows, and run remote processes, let's try to
-set up a useful working display.
-</PARA>
-<PARA>Say we're using a Sun 3/60 workstation with the hostname
-<SYSTEMNAME>jersey</SYSTEMNAME>. The workstation has a single display with two screens:
-screen 0 is color and screen 1 is black and white. Once X and
-the window manager<FOOTNOTEREF LINKEND="FN-1015-3-8"></FOOTNOTEREF>
-are running, we might set up the display using the
-following commands.
-<FOOTNOTE ID="FN-1015-3-8">
-<PARA>Note that you should run <COMMAND>mwm</COMMAND> with the <OPTION>-multiscreens</OPTION>
-option to have the program manage all screens on the display. If
-you start <COMMAND>mwm</COMMAND> without this option, it only manages screen 0. In
-this case, you can either kill and restart it with
-<OPTION>-multiscreens</OPTION> or run another instance of it on screen 1.
-</PARA>
-</FOOTNOTE>
-</PARA>
-<PARA>First,
-run an <COMMAND>xterm</COMMAND> on a more powerful remote system called
-<SYSTEMNAME>manhattan</SYSTEMNAME> and place it on screen 0 of <SYSTEMNAME>jersey</SYSTEMNAME>.
-</PARA>
-<SCREEN ID="SC-1015-3-24"><PROMPT>%</PROMPT> <USERINPUT>rsh manhattan xterm -geometry +0-0 -display jersey:0.0</USERINPUT></SCREEN>
-<PARA>Run <COMMAND>xload</COMMAND> windows on both <SYSTEMNAME>jersey</SYSTEMNAME> and <SYSTEMNAME>manhattan</SYSTEMNAME> to
-monitor loads on these systems. Again, place the windows
-on <SYSTEMNAME>jersey</SYSTEMNAME>'s color screen in convenient locations.
-</PARA>
-<SCREEN ID="SC-1015-3-25"><PROMPT>%</PROMPT> <USERINPUT>xload -geometry -10-200 </USERINPUT>
-
-<PROMPT>%</PROMPT> <USERINPUT>rsh manhattan xload -geometry -10-20 -display jersey:0.0
-</USERINPUT></SCREEN>
-<SCREEN></SCREEN>
-<PARA>Run another <COMMAND>xterm</COMMAND> window on <SYSTEMNAME>jersey</SYSTEMNAME>.
-</PARA>
-<SCREEN ID="SC-1015-3-26"><PROMPT>%</PROMPT> <USERINPUT>xterm -geometry +50-0 </USERINPUT>
-</SCREEN>
-<PARA>Then iconify the login <COMMAND>xterm</COMMAND> window so that you don't
-inadvertently kill it (and shut down X in the bargain). Remember: to
-iconify a window place the
-pointer on the Minimize command button on the window's frame and click the
-first button. (See “Converting a Window to an Icon” earlier in this
-chapter.)
-</PARA>
-<PARA>Run an <COMMAND>oclock</COMMAND>.
-</PARA>
-<SCREEN ID="SC-1015-3-27"><PROMPT>%</PROMPT> <USERINPUT>oclock -geometry +0+0 </USERINPUT>
-</SCREEN>
-<PARA><XREF LINKEND="FG-1015-3-17">Figure 3-17</XREF>
-shows the <SYSTEMNAME>jersey</SYSTEMNAME> display, screen 0: a fairly useful layout.
-</PARA>
-<FIGURE ID="FG-1015-3-17">
-<TITLE>A working display, screen 0</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.17.eps" ID="GC-1015-3-19"></GRAPHIC>
-</FIGURE>
-<PARA>You might also place client windows on the workstation's alternate
-screen, the black and white screen numbered 1.
-By default, windows are always placed on screen 0 but
-you can place a client window on screen 1
-by specifying the screen number in the <OPTION>-display</OPTION> option when
-starting the client.
-For instance,
-each of the following commands places an <COMMAND>xterm</COMMAND> window on screen 1.
-</PARA>
-<SCREEN ID="SC-1015-3-28"><PROMPT>%</PROMPT> <USERINPUT>xterm -display jersey:0.1 </USERINPUT>
-
-<PROMPT>%</PROMPT> <USERINPUT>rsh manhattan xterm -geometry -0-0 -display jersey:0.1 </USERINPUT>
-</SCREEN>
-<PARA><XREF LINKEND="FG-1015-3-18">Figure 3-18</XREF>
-illustrates screen 1.
-</PARA>
-<FIGURE ID="FG-1015-3-18">
-<TITLE>A working display, screen 1</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.18.eps" ID="GC-1015-3-20"></GRAPHIC>
-</FIGURE>
-<PARA>As we'll see in &amtfA;, on most systems you can place the commands
-you run to set up your display in a special file that is invoked when
-you log in. Once this file (usually called either <FILENAME>.xinitrc</FILENAME> or
-<FILENAME>.xsession</FILENAME>) is in place, when you log in your display will be
-set up to your specifications automatically.
-</PARA>
-<PARA>Notice that the commands we used to set up <SYSTEMNAME>jersey</SYSTEMNAME> illustrate the power of
-the <OPTION>-geometry</OPTION> and <OPTION>-display</OPTION> options to create a working
-environment that suits individual needs. However, these options
-barely hint at the number of features you can specify for each
-client. The following section introduces some principles of client
-customization. Part Two of this guide examines customization in depth.
-</PARA>
-<SECT2 ID="S2-1015-3-6"><TITLE>Customizing a Program</TITLE>
-<INDEXTERM ID="IX-1015-3-110" SPAN="START"><PRIMARY>command-line options</PRIMARY></INDEXTERM>
-<PARA>In a sense, command-line options allow you to customize one program.
-We've already seen how to use the <OPTION>-geometry</OPTION> and
-<OPTION>-display</OPTION> options, which are accepted by most clients.
-&cmtf10;, describes some of the other options accepted by most of
-the standard clients. These options set window features such as:
-</PARA>
-<ITEMIZEDLIST MARK="BULLET">
-<LISTITEM>
-<PARA>The font in which text is displayed.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>The background color.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>The foreground color (such as the color of text).
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>The text displayed in the title area.
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>The text of an icon label.
-</PARA></LISTITEM>
-</ITEMIZEDLIST>
-<PARA>Many clients also accept a large number of
-application-specific options (listed on the reference page for each
-client in Part Three of this guide). Using a combination of standard and
-application-specific options, you can
-tailor a client to look and behave in ways that better suit your needs.
-</PARA>
-<PARA>Like most clients, <COMMAND>xclock</COMMAND> accepts a variety of options.
-Some of <COMMAND>xclock</COMMAND>'s options are intended
-to enhance the clock display aesthetically and some to
-affect its operation. Taking a look at a few of <COMMAND>xclock</COMMAND>'s options
-should give you a better idea of the flexibility of X.
-</PARA>
-<PARA>The following command line runs a custom <COMMAND>xclock</COMMAND> display:
-</PARA>
-<SCREEN ID="SC-1015-3-29"><PROMPT>%</PROMPT> <USERINPUT>xclock -hd green -hl royalblue -bg lightblue -fg royalblue -update 1 -chime </USERINPUT>
-</SCREEN>
-<INDEXTERM ID="IX-1015-3-111"><PRIMARY>-hd option</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-112"><PRIMARY>command-line options</PRIMARY><SECONDARY>-hd</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-113"><PRIMARY>-hl option</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-114"><PRIMARY>command-line options</PRIMARY><SECONDARY>-hl</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-115"><PRIMARY>-bg option (X Toolkit)</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-116"><PRIMARY>command-line options</PRIMARY><SECONDARY>-bg (background)</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-117"><PRIMARY>command-line options</PRIMARY><SECONDARY>-fg</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-118"><PRIMARY>-fg option (X Toolkit)</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-119"><PRIMARY>-update option</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-120"><PRIMARY>command-line options</PRIMARY><SECONDARY>-update</SECONDARY></INDEXTERM>
-<PARA>As you can see, these specifications are intended for a color monitor.
-(X is highly flexible in the use of color. See &cmtf12;, for more
-information.) The <OPTION>-hd</OPTION> option sets the color of the clock's
-hands to green. The <OPTION>-hl</OPTION> option provides even more
-detail, specifying the color of the outline of the hands as royal blue.
-<OPTION>-bg</OPTION> and <OPTION>-fg</OPTION> are two of the options accepted by most clients;
-they set the window's background and foreground color, in this case to
-light blue and royal blue, respectively.
-</PARA>
-<PARA>The <OPTION>-update</OPTION> option takes as its argument the frequency in
-seconds at which the time on the clock should be updated. We've specified
-that the time be updated at one second intervals. Thus a second hand
-(also green) will be added to the <COMMAND>xclock</COMMAND> display.
-(The <COMMAND>xclock</COMMAND> reference page in Part Three of this guide specifies
-that a second hand is added if <OPTION>-update</OPTION> is given an argument of
-less than 30 seconds.)
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-121"><PRIMARY>-chime option</PRIMARY></INDEXTERM>
-The <OPTION>-chime</OPTION> option specifies that the keyboard bell will ring
-once on the half hour and twice on the hour.
-</PARA>
-<PARA>These options create a somewhat fancy <COMMAND>xclock</COMMAND> display. You might
-or might not want to use so many options, but these and several more
-are available.
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-122"><PRIMARY>xclock (analog or digital clock)</PRIMARY></INDEXTERM>
-By default, <COMMAND>xclock</COMMAND> displays a traditional clock face (an analog clock).
-You can create a digital <COMMAND>xclock</COMMAND> using the following option:
-</PARA>
-<SCREEN ID="SC-1015-3-30"><PROMPT>%</PROMPT> <USERINPUT>xclock -digital </USERINPUT>
-</SCREEN>
-<PARA>The digital <COMMAND>xclock</COMMAND> is pictured in
-<XREF LINKEND="FG-1015-3-19">Figure 3-19</XREF>.
-</PARA>
-<FIGURE ID="FG-1015-3-19">
-<TITLE>Digital xclock display</TITLE>
-<GRAPHIC FORMAT="EPS" FILEREF="figs/3m.03.19.eps" ID="GC-1015-3-21"></GRAPHIC>
-</FIGURE>
-<PARA>Logically, the <OPTION>-hd</OPTION> and <OPTION>-hl</OPTION> options, which set the color
-of the clock hands, are only valid with the analog (default) <COMMAND>xclock</COMMAND>.
-For a complete list of options, see the <COMMAND>xclock</COMMAND> reference page in
-Part Three of this guide.
-</PARA>
-<PARA>Command-line options override the default characteristics of a client
-for the <EMPHASIS>single client
-process</EMPHASIS>. Traditional UNIX applications rely on command-line options
-to allow users to customize the way they work. X also offers many
-command-line options, but these options have some limitations and
-liabilities.
-</PARA>
-<PARA>First, the number of client features that can be controlled by command
-line options is limited. Most applications have many more
-customizable features than their command-line options indicate. Actually,
-a client can have so many customizable features that typing a command line to
-set them all would be impractical. And if you generally use
-the same options with a client, it is tedious (and a waste of time) to
-type the options each time you run the program.
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-123"><PRIMARY>clients</PRIMARY><SECONDARY>specifying default characteristics for</SECONDARY></INDEXTERM>
-X offers an alternative to customizing a single client process
-on the command line. You can specify default characteristics for a
-client using variables called <EMPHASIS>resources</EMPHASIS>.
-<INDEXTERM ID="IX-1015-3-124" SPAN="END"><PRIMARY>command-line options</PRIMARY></INDEXTERM>
-</PARA>
-</SECT2>
-<SECT2 ID="S2-1015-3-7"><TITLE>Customizing the X Environment</TITLE>
-<INDEXTERM ID="IX-1015-3-125" SPAN="START"><PRIMARY>clients</PRIMARY><SECONDARY>customizing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-126" SPAN="START"><PRIMARY>customizing</PRIMARY><SECONDARY>clients</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-127" SPAN="START"><PRIMARY>X Window System</PRIMARY><SECONDARY>environment</SECONDARY>
-<TERTIARY>customizing</TERTIARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-128" SPAN="START"><PRIMARY>customizing</PRIMARY><SECONDARY>X environment</SECONDARY></INDEXTERM>
-<PARA>Command-line options allow you to customize one instance of a client
-program. In addition, X provides a mechanism that allows you to specify
-characteristics that take effect <EMPHASIS>every</EMPHASIS> time you run a client.
-Almost every feature of a client program can be controlled using a
-variable called a <FIRSTTERM>resource</FIRSTTERM>. You can change the behavior or
-appearance of a program by changing the <FIRSTTERM>value</FIRSTTERM> associated with a
-resource variable.
-(In some cases, a resource variable controls the same characteristic as
-a command-line option. However, while the option specifies a
-characteristic for the single client process being invoked, a resource
-variable makes the characteristic the program default.)
-</PARA>
-<PARA><INDEXTERM ID="IX-1015-3-129"><PRIMARY>resource variables</PRIMARY><SECONDARY>file kept in</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-130"><PRIMARY>.Xdefaults file</PRIMARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-131"><PRIMARY>.Xresources file</PRIMARY></INDEXTERM>
-You generally place resource specifications in a file in your home
-directory. (The file can have any name, but is often called
-<FILENAME>.Xresources</FILENAME> or <FILENAME>.Xdefaults</FILENAME>.)
-The resources you specify are one of several factors that affect the
-appearance and behavior of a client.
-</PARA>
-<PARA>By default, the way a client looks and behaves is determined by
-the program code, and in some cases, by
-a system-wide file of <EMPHASIS>application defaults</EMPHASIS>.
-Several clients have application defaults files that determine certain
-client
-features.<FOOTNOTEREF LINKEND="FN-1015-3-9"></FOOTNOTEREF>
-<FOOTNOTE ID="FN-1015-3-9">
-<PARA>For <COMMAND>xterm</COMMAND>, the application defaults specify such
-things as the labels for menu items, the fonts used to display menu items,
-and the shape of the pointer when it's in an <COMMAND>xterm</COMMAND> window.
-</PARA>
-<PARA>Application defaults files generally reside in the
-directory <FILENAME>/usr/lib/X11/app-defaults</FILENAME> and are named for the client
-application.
-In describing the appearance and behavior of clients in this guide, we
-assume all of the standard application defaults files are present on
-your system and accessible by the client programs. If, by some chance,
-a client's application defaults file has been edited or removed from
-your system, the client may not look or behave exactly as we describe it.
-If a client application appears substantially different than
-depicted in this guide, you may be using a different version of the
-program or the application defaults may be different. Consult your
-system administrator.
-</PARA>
-</FOOTNOTE>
-Within an application defaults file, defaults are set using resources.
-The resources specified in a client's application defaults
-files are usually just a subset of a greater number of resources that
-can be set.
-</PARA>
-<PARA>If the characteristics you set in your own resources file
-already have system-wide application defaults, your own settings
-take precedence.
-<INDEXTERM ID="IX-1015-3-132" SPAN="START"><PRIMARY>resources</PRIMARY><SECONDARY>setting</SECONDARY></INDEXTERM>
-Keep in mind, however, that command-line options override
-both your own defaults and any system-wide defaults for the single
-client process.
-</PARA>
-<PARA>To make your resource specifications available to all clients, X
-provides a program called <COMMAND>xrdb</COMMAND>, the X resource database manager.
-<COMMAND>xrdb</COMMAND> stores resources directly in the server where they are
-accessible to all clients, regardless of the machine the
-clients are running on.
-</PARA>
-<PARA>The basic syntax of a resource specification is fairly simple. Each
-client recognizes certain resource variables that can be assigned a
-value. The variables for each client are listed on its reference page
-in Part Three of this guide.
-</PARA>
-<PARA>A resource definition file is basically
-a two-column list, where each line specifies a different resource.
-The simplest resource definition line has
-the name of the client, followed
-by an asterisk, and the name of the variable, followed by a
-colon, in the left column. The right column (separated from the left
-by a tab or whitespace) contains the value of the resource variable.
-</PARA>
-<SCREEN ID="SC-1015-3-31"><VARPARAM>client</VARPARAM><LITERAL>*</LITERAL><VARPARAM>variable</VARPARAM><LITERAL>:</LITERAL><VARPARAM>value</VARPARAM>
-</SCREEN>
-<PARA>The following example shows five simple resource specifications for the
-<COMMAND>xclock</COMMAND> client. These particular resources specify the same
-characteristics as the command-line
-options we used to create the green and blue <COMMAND>xclock</COMMAND> in the
-preceding section.
-</PARA>
-<EXAMPLE ID="EX-1015-3-1">
-<TITLE>Resources to create a custom xclock</TITLE>
-<PROGRAMLISTING>xclock*hands: green
-xclock*highlight: royalblue
-xclock*background: lightblue
-xclock*foreground: royalblue
-xclock*update: 1
-xclock*chime: true
-</PROGRAMLISTING>
-</EXAMPLE>
-<PARA>To set up your environment so that these characteristics apply each
-time you run <COMMAND>xclock</COMMAND>, you would perform the following steps:
-</PARA>
-<ORDEREDLIST NUMERATION="ARABIC">
-<LISTITEM>
-<PARA>In your home directory,
-create a file containing the resources listed in <XREF LINKEND="EX-1015-3-1">Example 3-1</XREF>.
-
-Name the file <FILENAME>.Xresources</FILENAME>. (A resource file can actually have
-any name, but is often called <FILENAME>.Xresources</FILENAME> or <FILENAME>.Xdefaults</FILENAME>.)
-</PARA></LISTITEM>
-<LISTITEM>
-<PARA>Load the resources into the server by entering the following command
-in an <COMMAND>xterm</COMMAND> window:
-</PARA>
-<SCREEN ID="SC-1015-3-32"><PROMPT>%</PROMPT> <USERINPUT>xrdb -load .Xresources</USERINPUT>
-</SCREEN>
-<PARA></PARA></LISTITEM>
-</ORDEREDLIST>
-<PARA>Then each time you run <COMMAND>xclock</COMMAND> without options (for the remainder
-of that login session), the window will reflect the new defaults.
-</PARA>
-<PARA>You should load resources using <COMMAND>xrdb</COMMAND> every time you log in.
-In &amtfA;, we'll describe how to automate this process using
-a special startup script, which also opens the client windows you want
-on your display.
-</PARA>
-<PARA>If you want to run an application with different characteristics (colors,
-update frequency, etc.) from the defaults, use the appropriate command
-line options to override the resource specifications.
-</PARA>
-<PARA>Resource specifications can be much more complicated than our samples
-suggest. For applications written with a toolkit (such as the X
-Toolkit or the Open Software Foundation's Motif Toolkit),
-X allows you to specify different characteristics for individual
-components, or <EMPHASIS>widgets</EMPHASIS>, within the application.
-Typical widgets create graphical features such as menus, command buttons,
-dialog boxes, and scrollbars. Within most toolkit applications is a
-fairly complex widget hierarchy--widgets exist within widgets (e.g., a
-command button within a dialog box).
-</PARA>
-<PARA>Resource naming syntax can parallel the widget hierarchy within an
-application. For instance, you might set different background colors for
-different command buttons and specify still another background color
-for the dialog box that encloses them. In such cases, the actual widget names
-are used within the resource specification. &cmtf11;,
-explains the resource
-naming syntax in greater detail
-and outlines the rules governing the precedence of resources.
-It also explains how to use the <COMMAND>editres</COMMAND> program to examine a
-(standard) client's widget hierarchy and set resources accordingly.
-<INDEXTERM ID="IX-1015-3-133" SPAN="END"><PRIMARY>X Window System</PRIMARY><SECONDARY>environment</SECONDARY>
-<TERTIARY>customizing</TERTIARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-134" SPAN="END"><PRIMARY>customizing</PRIMARY><SECONDARY>X environment</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-135" SPAN="END"><PRIMARY>resources</PRIMARY><SECONDARY>setting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-136" SPAN="END"><PRIMARY>clients</PRIMARY><SECONDARY>customizing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-1015-3-137" SPAN="END"><PRIMARY>customizing</PRIMARY><SECONDARY>clients</SECONDARY></INDEXTERM>
-</PARA>
-</SECT2></SECT1>
-<SECT1 ID="S1-1015-3-5"><TITLE>Where to Go from Here</TITLE>
-<PARA>There are many useful client programs supplied with the X Window
-System. Details of how to use one of the most important
-clients, the <COMMAND>xterm</COMMAND> terminal emulator, are provided in Chapter 5.
-Clients to list and display fonts are described in &cmtf06;.
-Chapter 6 also describes the X font naming conventions and various
-ways to specify fonts on the command line (and in resource files).
-Chapter 7 describes several <EMPHASIS>Graphics Utilities</EMPHASIS> available with
-X. An overview and tutorial for other standard clients and
-instructions on using certain public domain clients
-are provided in &cmtf08;.
-&cmtf09;, gives instructions on using Motif applications.
-All clients are described in detail in a reference
-page format in Part Three of this guide.
-</PARA>
-<PARA>We've introduced some basic operations you can perform using the
-<COMMAND>mwm</COMMAND> window manager.
-For instructions on performing additional window manager operations,
-such as lowering a window, read &cmtf04;.
-You can then go on to read more about
-<COMMAND>xterm</COMMAND> in Chapter 5 and about some of the other standard clients
-in Chapters 6 through 8.
-</PARA>
-</SECT1></CHAPTER></DOCBOOK>
+++ /dev/null
-<!-- ===================================================================== -->
-
-<!--
-
- DocBook DTD $Revision$
-
- $Date$
-
- Copyright 1992, 1993 HaL Computer Systems International, Ltd., and
- O'Reilly & Associates, Inc.
-
- Permission to use, copy, modify and distribute the DocBook DTD and
- its accompanying documentation for any purpose and without fee is
- hereby granted, provided that this copyright notice appears in
- all copies. If you modify the DocBook DTD, rename your modified
- version. HaL Computer Systems International, Ltd., and
- O'Reilly & Associates, Inc., make no representation about the
- suitability of the DTD for any purpose. It is provided "as is"
- without expressed or implied warranty.
-
- The DocBook DTD is maintained by HaL Computer Systems
- International, Ltd., and O'Reilly & Associates, Inc. Please
- direct all questions, bug reports, or suggestions for changes to:
- davenport@ora.com or by postal mail to either: Terry Allen, O'Reilly &
- Associates, Inc., 103A Morris Street, Sebastopol, California,
- 95472; or Conleth O'Connell, HaL Computer Systems, 3006-A
- Longhorn Blvd., Austin, Texas, 78758.
-
- Please note that an SGML declaration is provided for this DTD.
-
- Public Identifier:
- "-//HaL and O'Reilly//DTD DocBook//EN"
-
- -->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!-- NOTATIONS -->
-
-<!NOTATION CGM-CHAR PUBLIC "ISO 8632/2//NOTATION Character encoding//EN" >
-<!NOTATION CGM-CLEAR PUBLIC "ISO 8632/4//NOTATION Clear text encoding//EN" >
-<!NOTATION DITROFF SYSTEM "DITROFF" >
-<!NOTATION DVI SYSTEM "DVI" >
-<!NOTATION EPS PUBLIC "+//ISBN 0-201-18127-4::Adobe//NOTATION
- PostScript Language Ref. Manual//EN" >
-<!NOTATION EQN SYSTEM "-//AT&T//NOTATION EQN-1//EN" >
-<!NOTATION FAX PUBLIC "-//USA-DOD//NOTATION CCITT Group 4 Fascimile
- Type 1 Untiled Raster//EN" >
-<!NOTATION FAXTILE PUBLIC "-//USA-DOD//NOTATION CCITT Group 4 Fascimile
- Type 2 Tiled Raster//EN" >
-<!NOTATION GIF SYSTEM "GIF" >
-<!NOTATION IGES PUBLIC "-//USA-DOD//NOTATION (ASME/ANSI Y14.26M-1987)
- Initial Graphics Exchange Specification//EN" >
-<!NOTATION PIC SYSTEM "-//AT&T//NOTATION PIC-1//EN" >
-<!NOTATION PS SYSTEM "PS" >
-<!NOTATION TBL SYSTEM "-//AT&T//NOTATION TBL-1//EN" >
-<!NOTATION TEX PUBLIC "+//ISBN 0-201-13448-9::Knuth//NOTATION
- The TeXbook//EN" >
-<!NOTATION TIFF SYSTEM "TIFF" >
-<!NOTATION linespecific SYSTEM
- "line ends and leading white space must be preserved in output" >
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!-- EXTERNALLY DECLARED CHARACTER ENTITIES -->
-
-<!-- Uncomment the ENTITY sets needed for your application. -->
-
-<!--
-<!ENTITY % ISOchars PUBLIC
- "-//ENTITIES Public ISO Character Declarations//EN"
- "iso-public" >
-<!ENTITY % ISOchars PUBLIC
- "-//ENTITIES System ISO Character Declarations//EN"
- "iso-system" >
-<!ENTITY % ISOchars SYSTEM "iso-public">
-<!ENTITY % ISOchars SYSTEM "iso-system">
- -->
-
-<!--
- %ISOchars;
- -->
-
-<!--
- %ISOamsa;
- %ISOamsb;
- %ISOamsc;
- %ISOamsn;
- %ISOamso;
- %ISOamsr;
- %ISObox;
- %ISOcyr1;
- %ISOcyr2;
- %ISOdia;
- %ISOgrk1;
- %ISOgrk2;
- %ISOgrk3;
- %ISOgrk4;
- %ISOlat1;
- %ISOlat2;
- %ISOmfrk;
- %ISOmopf;
- %ISOmscr;
- %ISOnum;
- %ISOpub;
- %ISOtech;
- -->
-
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!--
-
- PARAMETER ENTITIES to allow inclusion of local modifications.
- To include your local terms, table content model, graphics
- format, or other local item,
-
- At the head of your instance, after the DOCTYPE line, include
- a reference to an external entity file that that includes all
- the local terms, table content models, and (or) graphics
- formats you are using:
-
- <!DOCTYPE Chapter SYSTEM "/yourpath/docbook.dtd" [
- <!ENTITY % localmods SYSTEM "/yourpath/localmodfile" >
- %localmods;
- ]>
-
- You may need to set up attributes for your local elements.
-
- -->
-
-<!-- CONTENT MODEL LOCALIZATIONS -->
-
-<!ENTITY % local.admonitions "" >
-<!ENTITY % local.appendix "" >
-<!ENTITY % local.book "" >
-<!ENTITY % local.chapter "" >
-<!ENTITY % local.cptrterms "" >
-<!ENTITY % local.equations "" >
-<!ENTITY % local.examples "" >
-<!ENTITY % local.index "" >
-<!ENTITY % local.links "" >
-<!ENTITY % local.lists "" >
-<!ENTITY % local.notations "" >
-<!ENTITY % local.refclasses "" >
-<!ENTITY % local.nav "" >
-<!ENTITY % local.ndxterms "" >
-<!ENTITY % local.synopsis "" >
-<!ENTITY % local.tables "" >
-<!ENTITY % local.terms "" >
-
-<!-- ===================================================================== -->
-
-<!--
-
- ATTRIBUTE LIST for a set of common attributes.
-
- -->
-
-<!ENTITY % commonatts
- "Id ID #IMPLIED
- Lang CDATA #IMPLIED
- Remap CDATA #IMPLIED
- Role CDATA #IMPLIED
- XRefLabel CDATA #IMPLIED"
->
-
-<!-- ===================================================================== -->
-<!--
-
- Many attributes have a Boolean value. They are given the declared
- value of "%yesorno;" rather then NUMBER to indicate this intent. 0
- is interpreted as false; all other numbers as true. This concept
- is borrowed from the CALS MIL DTD.
-
- -->
-
-<!ENTITY % yesorno "NUMBER" >
-<!ENTITY % yes "1" >
-<!ENTITY % no "0" >
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- PARAMETER ENTITIES -->
-<!-- ===================================================================== -->
-
-<!-- Book Contents -->
-
-<!ENTITY % appendix.gp "Appendix %local.appendix;" >
-
-<!ENTITY % book.gp "Book %local.book;" >
-
-<!ENTITY % chapter.gp "Chapter %local.chapter;" >
-
-<!ENTITY % index.gp "Index | SetIndex %local.index;" >
-
-<!ENTITY % bookcontent.gp "%appendix.gp; | Bibliography | %chapter.gp; |
- Glossary | %index.gp; | LoT | Preface | RefEntry | Reference |
- ToC " >
-
-<!-- ===================================================================== -->
-
-<!-- Contents that can appear almost anywhere -->
-
-<!ENTITY % ndxterm.gp "IndexTerm %local.ndxterms;" >
-
-<!ENTITY % xref.gp "FootnoteRef | XRef" >
-
-<!ENTITY % links.gp "Link | OLink | ULink %local.links;" >
-
-<!ENTITY % basechar.gp "%ndxterm.gp; | #PCDATA | Anchor | BeginPage" >
-
-<!ENTITY % phrase.gp "%basechar.gp; | Comment | Subscript | Superscript |
- %links.gp;" >
-
-<!-- ===================================================================== -->
-
-<!ENTITY % bookinfo.content.gp "Author | AuthorInitials | Title | Copyright |
- CorpAuthor | CorpName | Date | Editor | Edition |
- InvPartNumber | ISBN | LegalNotice | OrgName | OtherCredit |
- PrintHistory | ProductName | ProductNumber | Publisher |
- PubsNumber | ReleaseInfo | RevHistory | Subtitle |
- VolumeNum" >
-
-<!-- ===================================================================== -->
-
-<!ENTITY % docinfo.content.gp "Author | AuthorInitials | CorpAuthor | ModeSpec
- | OtherCredit | RevHistory" >
-
-<!-- ===================================================================== -->
-
-<!ENTITY % words.gp "Abbrev | Acronym | Character | Charset | Citation |
- CiteTitle | CiteRefEntry | Emphasis | FirstTerm | Font |
- ForeignPhrase | GlossTerm | Glyph | Footnote | Markup |
- Quote | SGMLTag | Trademark | WordAsWord" >
-
-<!-- ===================================================================== -->
-
-<!ENTITY % computerterms.gp "Action | Application | Classname | Command |
- ComputerOutput | Database | ErrorName | ErrorType |
- EventStructure | EventType | Filename | Function | Hardware |
- Interface | InterfaceDefinition | KeyCap | KeyCode | KeySym |
- Literal | Mask | MediaLabel | MsgText | Option | Parameter |
- Property | ProtocolRequest | Replaceable | ReturnValue |
- StructField | StructName | Symbol | SystemItem | Token | Type
- | UserInput %local.cptrterms;" >
-
-<!-- ===================================================================== -->
-
-<!ENTITY % cptrphrase.gp "%phrase.gp; | %computerterms.gp;" >
-
-<!ENTITY % inlinechar.gp "%phrase.gp; | %computerterms.gp; |
- %docinfo.content.gp; | %words.gp; | %xref.gp; %local.terms;" >
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!-- ===================================================================== -->
-
-<!-- Contents of Equation -->
-
-<!ENTITY % eqncontent.gp "Graphic %local.equations;" >
-
-<!-- ===================================================================== -->
-
-<!-- Contents of Table -->
-
-<!ENTITY % tblcontent.gp "(Graphic+ | TGroup+ %local.tables;)" >
-
-<!-- All the varieties of lists -->
-
-<!ENTITY % list.gp "ItemizedList | OrderedList | SegmentedList | SimpleList |
- VariableList %local.lists; " >
-
-<!-- ===================================================================== -->
-
-<!-- All of the varieties of admonitions -->
-
-<!ENTITY % admonition.gp "Caution | Important | Note | Tip | Warning
- %local.admonitions;" >
-
-<!-- ===================================================================== -->
-
-<!-- All of the varieties of code and whitespace-sensitive examples -->
-
-<!ENTITY % code.example.gp "LiteralLayout | ProgramListing | Screen |
- ScreenShot %local.examples;" >
-
-<!ENTITY % synop.gp "Synopsis | CmdSynopsis | FuncSynopsis %local.synopsis;" >
-
-<!-- ===================================================================== -->
-
-<!-- Informal elements used within other paragraph elements -->
-
-<!ENTITY % object.gp "BlockQuote | InformalEquation | InformalTable |
- %code.example.gp; | Graphic | %synop.gp;" >
-
-<!-- ===================================================================== -->
-
-<!-- Para elements -->
-
-<!ENTITY % para.gp "FormalPara | Para | SimPara" >
-
-<!-- ===================================================================== -->
-
-<!-- Formal elements used within other paragraph elements -->
-
-<!ENTITY % formalobject.gp "Equation | Example | Figure | Table" >
-
-<!-- ===================================================================== -->
-
-<!ENTITY % component.gp "Abstract | Anchor | AuthorBlurb | %admonition.gp; |
- BridgeHead | Comment | Epigraph | %formalobject.gp; |
- Highlights | %ndxterm.gp; | %list.gp; | %object.gp; |
- %para.gp; | MsgSet | Procedure | Sidebar" >
-
-<!-- ===================================================================== -->
-
-<!ENTITY % refclass.gp "#PCDATA | Application %local.refclasses;" >
-
-<!ENTITY % nav.gp "ToC | LoT | Index | Glossary | Bibliography %local.nav;" >
-
-<!ENTITY % inlineobj.gp "%inlinechar.gp; | InlineGraphic | InlineEquation |
- %synop.gp;" >
-
-<!-- ===================================================================== -->
-
-<!-- The sect1.gp parameter entity is used in Chapter, Preface, and
- Appendix -->
-
-<!ENTITY % sect1.gp "((%component.gp;)+, (Sect1* | RefEntry*)) | Sect1+ |
- RefEntry+" >
-
-<!-- ===================================================================== -->
-
-<!ENTITY % primsee "PrimaryIE, (SeeIE | SeeAlsoIE+)*" >
-
-<!ENTITY % secsee "(SecondaryIE, ((SeeIE | SeeAlsoIE+) | TertiaryIE)*)" >
-
-<!ENTITY % notationtypes "(CGM-CHAR | CGM-CLEAR | DITROFF | DVI | EPS | EQN |
- FAX | FAXTILE | GIF | IGES | PIC | PS | TBL | TEX | TIFF |
- linespecific %local.notations;)" >
-
-<!-- Common attributes for command synopses: -->
-
-<!ENTITY % argchcatt "Choice ( opt | req | plain ) 'opt'">
-<!ENTITY % grpchcatt "Choice ( opt | req | plain | optmult | reqmult )
- 'opt'">
-<!ENTITY % repatt "Rep ( norepeat | repeat ) 'norepeat'">
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- ELEMENTS -->
-<!-- ===================================================================== -->
-
-<!-- ===================================================================== -->
-<!-- GENERAL BOOK STRUCTURES -->
-<!-- ===================================================================== -->
-
-<!--
-
- A Set contains at least two books. A Book, which could be a
- journal or an anthology, must have a Chapter or Reference or
- Part, and may contain other contents as required. We believe
- this model accomodates the order of contents for English,
- French, German, and Japanese books.
-
- A Part contains at least one book content element. A
- Preface, ToC, LoT, Bibliography, Glossary, or Index can be a
- chapter-level component, while ToC, LoT, Bibliography,
- Glossary, RefEntry, and Index may also appear within
- chapter-level components.
-
- -->
-
-<!-- A model for a Set of Books -->
-
-<!ELEMENT Set - - ((Title, TitleAbbrev?)?, SetInfo?, ToC?, (%book.gp;),
- (%book.gp;)+, SetIndex?) >
-<!ATTLIST Set
- %commonatts;
- FPI CDATA #IMPLIED
->
-
-<!ELEMENT SetInfo - - ((%bookinfo.content.gp;)+) >
-<!ATTLIST SetInfo
- %commonatts;
- -- Contents points to the IDs of the book pieces (from
- book.gp) in the order of their appearance --
- Contents IDREFS #IMPLIED
->
-
-<!-- A prescriptive model for a Book -->
-
-<!ELEMENT Book - - ((Title, TitleAbbrev?)?, BookInfo?, ToC?, LoT*, Preface*,
- (((%chapter.gp;)+, Reference*) | Part+ | Reference+ |
- Article+), (%appendix.gp;)*, Glossary?, Bibliography?,
- (%index.gp;)*, LoT*, ToC? ) >
-<!ATTLIST Book
- %commonatts;
- FPI CDATA #IMPLIED
- Label CDATA #IMPLIED
->
-
-<!ELEMENT BookInfo - - (BookBiblio, LegalNotice*, ModeSpec*) >
-<!ATTLIST BookInfo
- %commonatts;
- -- Contents points to the IDs of the book pieces (from
- book.gp) in the order of their appearance --
- Contents IDREFS #IMPLIED
->
-
-<!--
-
- PageNums is the pages contained in a given issue or volume.
-
- -->
-
-<!ELEMENT BookBiblio - - (Title, TitleAbbrev?, Subtitle?, Edition?,
- AuthorGroup+, ((ISBN, VolumeNum?) | (ISSN, VolumeNum?,
- IssueNum?, PageNums?))?, InvPartNumber?, ProductNumber?,
- ProductName?, PubsNumber?, ReleaseInfo?, PubDate*, Publisher*,
- Copyright?, SeriesInfo?, Abstract*, ConfGroup*, (ContractNum |
- ContractSponsor)*, PrintHistory?, RevHistory?) >
-<!ATTLIST BookBiblio
- %commonatts;
->
-
-<!-- Most of the book component elements -->
-
-<!ELEMENT Appendix - - (DocInfo?, Title, TitleAbbrev?, (%sect1.gp;)) >
-<!ATTLIST Appendix
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!ELEMENT Chapter - - (DocInfo?, Title, TitleAbbrev?, (%sect1.gp;),
- (Index | Glossary | Bibliography)*) >
-<!ATTLIST Chapter
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!ELEMENT DocInfo - - (Title, TitleAbbrev?, Subtitle?, AuthorGroup+,
- Abstract*, RevHistory?, LegalNotice*) >
-<!ATTLIST DocInfo
- %commonatts;
->
-
-<!ELEMENT Part - - (DocInfo?, Title, TitleAbbrev?, PartIntro?,
- (%bookcontent.gp;)+) >
-<!ATTLIST Part
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!ELEMENT PartIntro - - ((Title, TitleAbbrev?)?, (%sect1.gp;)) >
-<!ATTLIST PartIntro
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!ELEMENT Preface - - (DocInfo?, Title, TitleAbbrev?, (%sect1.gp;)) >
-<!ATTLIST Preface
- %commonatts;
->
-
-<!ELEMENT Reference - - (DocInfo?, Title, TitleAbbrev?, PartIntro?, RefEntry+)
- >
-<!ATTLIST Reference
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!ELEMENT SeriesInfo - - (Title, TitleAbbrev?, Subtitle?, AuthorGroup*, ISBN?,
- VolumeNum?, IssueNum?, SeriesVolNums, PubDate*, Publisher*,
- Copyright?) >
-<!ATTLIST SeriesInfo
- %commonatts;
->
-
-<!ELEMENT Title - - ((%inlinechar.gp;)+) >
-<!ATTLIST Title
- %commonatts;
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT TitleAbbrev - - ((%inlinechar.gp;)+) >
-<!ATTLIST TitleAbbrev
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- SECTIONS -->
-<!-- ===================================================================== -->
-
-<!ELEMENT Sect1 - - (Title, TitleAbbrev?, (%nav.gp;)*, (((%component.gp;)+,
- (RefEntry* | Sect2*)) | RefEntry+ | Sect2+), (%nav.gp;)*) >
-<!ATTLIST Sect1
- %commonatts;
- Label CDATA #IMPLIED
- Renderas (Sect1 | Sect2 | Sect3 | Sect4 | Sect5)
- Sect1
->
-
-<!ELEMENT Sect2 - - (Title, TitleAbbrev?, (%nav.gp;)*, (((%component.gp;)+,
- (RefEntry* | Sect3*)) | RefEntry+ | Sect3+), (%nav.gp;)*) >
-<!ATTLIST Sect2
- %commonatts;
- Label CDATA #IMPLIED
- Renderas (Sect1 | Sect2 | Sect3 | Sect4 | Sect5)
- Sect2
->
-
-<!ELEMENT Sect3 - - (Title, TitleAbbrev?, (%nav.gp;)*, (((%component.gp;)+,
- (RefEntry* | Sect4*)) | RefEntry+ | Sect4+), (%nav.gp;)*) >
-<!ATTLIST Sect3
- %commonatts;
- Label CDATA #IMPLIED
- Renderas (Sect1 | Sect2 | Sect3 | Sect4 | Sect5)
- Sect3
->
-
-<!ELEMENT Sect4 - - (Title, TitleAbbrev?, (%nav.gp;)*, (((%component.gp;)+,
- (RefEntry* | Sect5*)) | RefEntry+ | Sect5+), (%nav.gp;)*) >
-<!ATTLIST Sect4
- %commonatts;
- Label CDATA #IMPLIED
- Renderas (Sect1 | Sect2 | Sect3 | Sect4 | Sect5)
- Sect4
->
-
-<!ELEMENT Sect5 - - (Title, TitleAbbrev?, (%nav.gp;)*, (((%component.gp;)+,
- RefEntry*) | RefEntry+), (%nav.gp;)*) >
-<!ATTLIST Sect5
- %commonatts;
- Label CDATA #IMPLIED
- Renderas (Sect1 | Sect2 | Sect3 | Sect4 | Sect5)
- Sect5
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- OTHER SECTION-ISH ELEMENTS -->
-<!-- ===================================================================== -->
-
-<!ELEMENT MsgSet - - (MsgEntry+) >
-<!ATTLIST MsgSet
- %commonatts;
->
-
-<!ELEMENT MsgEntry - - (Msg+, MsgInfo?, MsgExplan*) >
-<!ATTLIST MsgEntry
- %commonatts;
->
-
-<!ELEMENT Msg - - (Title?, MsgMain, (MsgSub | MsgRel)*) >
-<!ATTLIST Msg
- %commonatts;
->
-
-<!ELEMENT MsgMain - - (Title?, MsgText) >
-<!ATTLIST MsgMain
- %commonatts;
->
-
-<!ELEMENT MsgSub - - (Title?, MsgText) >
-<!ATTLIST MsgSub
- %commonatts;
->
-
-<!ELEMENT MsgRel - - (Title?, MsgText) >
-<!ATTLIST MsgRel
- %commonatts;
->
-
-<!ELEMENT MsgText - - ((%component.gp;)+) >
-<!ATTLIST MsgText
- %commonatts;
->
-
-<!ELEMENT MsgInfo - - ((MsgLevel | MsgOrig | MsgAud)*) >
-<!ATTLIST MsgInfo
- %commonatts;
->
-
-<!ELEMENT MsgLevel - - (#PCDATA) >
-<!ATTLIST MsgLevel
- %commonatts;
->
-
-<!ELEMENT MsgOrig - - (#PCDATA) >
-<!ATTLIST MsgOrig
- %commonatts;
->
-
-<!ELEMENT MsgAud - - (#PCDATA) >
-<!ATTLIST MsgAud
- %commonatts;
->
-
-<!ELEMENT MsgExplan - - (Title?, (%component.gp)+) >
-<!ATTLIST MsgExplan
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!ELEMENT Procedure - - ((Title, TitleAbbrev?)?, (%component.gp;)*, Step+) >
-<!ATTLIST Procedure
- %commonatts;
->
-
-<!ELEMENT Step - - (Title?, (((%component.gp;)+, SubSteps?) | (SubSteps))) >
-<!ATTLIST Step
- %commonatts;
- Performance (Optional|Required)
- Required
->
-
-<!ELEMENT SubSteps - - (Step+) >
-<!ATTLIST SubSteps
- %commonatts;
- Performance (Optional|Required)
- Required
->
-
-<!--
-
- Components not included are: Abstract, AuthorBlurb, Epigraph,
- Highlights, and Sidebar.
-
- -->
-
-<!ELEMENT Sidebar - - ((Title, TitleAbbrev?)?, (%para.gp; | %list.gp; |
- %object.gp; | %admonition.gp; | %formalobject.gp; | Highlights
- | BridgeHead | Procedure | Comment | Anchor |
- %ndxterm.gp;)+) >
-<!ATTLIST Sidebar
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- PARAGRAPH-RELATED ELEMENTS -->
-<!-- ===================================================================== -->
-
-<!ELEMENT (Abstract | AuthorBlurb) - - (Title?, (%para.gp;)+) >
-<!ATTLIST (Abstract | AuthorBlurb)
- %commonatts;
->
-
-<!ELEMENT BlockQuote - - (Title?, (%component.gp;)+) >
-<!ATTLIST BlockQuote
- %commonatts;
->
-
-<!ELEMENT BridgeHead - - ((%inlinechar.gp;)+) >
-<!ATTLIST BridgeHead
- %commonatts;
- Renderas (Other | Sect1 | Sect2 | Sect3 | Sect4 |
- Sect5) Other
->
-
-<!ELEMENT Comment - - ((%inlinechar.gp;)+) >
-
-<!ELEMENT Epigraph - - ((%para.gp;)+) >
-<!ATTLIST Epigraph
- %commonatts;
->
-
-<!ELEMENT Footnote - - ((%para.gp; | %object.gp; | %list.gp;)+) >
-<!ATTLIST Footnote
- Id ID #REQUIRED
- Label CDATA #IMPLIED
- Lang CDATA #IMPLIED
- Remap CDATA #IMPLIED
- Role CDATA #IMPLIED
- XRefLabel CDATA #IMPLIED
->
-
-<!ELEMENT Highlights - - ((%list.gp; | %para.gp; | (%admonition.gp;))+) >
-<!ATTLIST Highlights
- %commonatts;
->
-
-<!ELEMENT FormalPara - - (Title, Para) >
-<!ATTLIST FormalPara
- %commonatts;
->
-
-<!ELEMENT Para - - ((%inlinechar.gp; | %list.gp; | %object.gp;)+) >
-<!ATTLIST Para
- %commonatts;
->
-
-<!ELEMENT SimPara - - ((%inlineobj.gp;)+) >
-<!ATTLIST SimPara
- %commonatts;
->
-
-<!--
-
- Components not included are: Abstract, AuthorBlurb, other admonitions,
- Epigraph, and Highlights.
-
- -->
-
-<!ELEMENT (Tip | Caution | Warning | Important | Note) - - (Title?, (Anchor |
- BridgeHead | Comment | %formalobject.gp; | %ndxterm.gp; |
- %list.gp; | %object.gp; | %para.gp; | Procedure | Sidebar)+) >
-<!ATTLIST (Tip | Caution | Warning | Important | Note)
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- LISTS -->
-<!-- ===================================================================== -->
-
-<!--
-
- The Mark attribute specifies the mark that should appear
- before each ListItem, such as Bullet, Dash, Box, Check.
-
- -->
-
-<!ELEMENT ItemizedList - - (ListItem+) >
-<!ATTLIST ItemizedList
- %commonatts;
- Mark CDATA #IMPLIED
->
-
-<!ELEMENT ListItem - - ((%component.gp;)+) >
-<!ATTLIST ListItem
- %commonatts;
- Override CDATA #IMPLIED
->
-
-<!ELEMENT OrderedList - - (ListItem+) >
-<!ATTLIST OrderedList
- %commonatts;
- Numeration (Arabic | Upperalpha | Loweralpha
- | Upperroman | Lowerroman)
- #IMPLIED
- InheritNum (Inherit | Ignore)
- Ignore
- Continuation (Continues | Restarts)
- Restarts
->
-
-<!ELEMENT SegmentedList - - ((Title, TitleAbbrev?)?, SegTitle*, SegListItem+)
- >
-<!ATTLIST SegmentedList
- %commonatts;
->
-
-<!ELEMENT SegTitle - - ((%inlinechar.gp;)+) >
-<!ATTLIST SegTitle
- %commonatts;
->
-
-<!ELEMENT SegListItem - - (Seg, Seg+) >
-<!ATTLIST SegListItem
- %commonatts;
->
-
-<!ELEMENT Seg - - ((%inlinechar.gp;)+) >
-<!ATTLIST Seg
- %commonatts;
->
-
-<!ELEMENT VariableList - - ((Title, TitleAbbrev?)?, VarListEntry+) >
-<!ATTLIST VariableList
- %commonatts;
->
-
-<!ELEMENT VarListEntry - - (Term+, ListItem) >
-<!ATTLIST VarListEntry
- %commonatts;
->
-
-<!ELEMENT Term - - ((%inlinechar.gp;)+) >
-<!ATTLIST Term
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!--
-
- SimpleList allows you to list short strings (Members) in an array or
- in a normal sentence. The "inline" value of the Type attribute
- presents the Members inline (you have to generate commas
- and the "and" if need be). "Horiz" means set up as many columns
- as are specified by the value of the Columns attribute, of equal
- width, indented as for a BlockQuote, and enter the Members in
- these slots from L to R, top to bottom, left justified. "Vert" means
- calculate the columns the same way and determine the number of rows
- as if you were using Horiz; then just fill in the positions from
- top to bottom, L to R left-justified. In other words, you
- don't set the number of rows, only the number of columns.
- (This way, when on-line and the window resizes, you don't have to
- readjust the text unless the window gets so narrow you can't
- display the specified number of columns, then a renderer might
- reduce the number of columns.) When Column = 1, Vert and Horiz
- provide the same rendition.
-
- -->
-
-<!ELEMENT SimpleList - - (Member+) >
-<!ATTLIST SimpleList
- %commonatts;
- Columns NUMBER #IMPLIED
- Type (Inline | Vert | Horiz)
- Vert
->
-
-<!ELEMENT Member - - ((%inlinechar.gp;)+) >
-<!ATTLIST Member
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- OBJECTS -->
-<!-- ===================================================================== -->
-
-<!-- ===================================================================== -->
-<!-- EXAMPLE -->
-<!-- ===================================================================== -->
-
-<!ELEMENT Example - - (Title, TitleAbbrev?, (%para.gp; | %list.gp; |
- %object.gp;)+) >
-<!ATTLIST Example
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!ELEMENT ProgramListing - - ((LineAnnotation | Optional | %inlinechar.gp;)+)
- >
-<!ATTLIST ProgramListing
- %commonatts;
- Format NOTATION
- (linespecific) linespecific
- Width NUMBER #IMPLIED
->
-
-<!ELEMENT LiteralLayout - - ((LineAnnotation | Optional | %inlinechar.gp;)+) >
-<!ATTLIST LiteralLayout
- %commonatts;
- Format NOTATION
- (linespecific) linespecific
- Width NUMBER #IMPLIED
->
-
-<!ELEMENT Screen - - ((LineAnnotation | Optional | %inlinechar.gp;)+) >
-<!ATTLIST Screen
- %commonatts;
- Format NOTATION
- (linespecific) linespecific
- Width NUMBER #IMPLIED
->
-
-<!ELEMENT ScreenShot - - (ScreenInfo?, Graphic) >
-<!ATTLIST ScreenShot
- %commonatts;
- Width NUMBER #IMPLIED
->
-
-<!ELEMENT ScreenInfo - - (#PCDATA) >
-<!ATTLIST ScreenInfo
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- FIGURE -->
-<!-- ===================================================================== -->
-<!--
-
- N.B.: Graphic occurs in object.gp, so does not appear
- explicitly in Figure.
-
- -->
-
-<!ELEMENT Figure - - (Title, TitleAbbrev?, (%object.gp; | %links.gp;)+) >
-<!ATTLIST Figure
- %commonatts;
- Float %yesorno; %no;
- Label CDATA #IMPLIED
->
-
-<!--
-
- Graphical data can be the content of Graphic, or you can
- reference an external file through the Fileref attribute,
- either as an entity or a filename.
-
- -->
-
-<!ELEMENT Graphic - - CDATA>
-<!ATTLIST Graphic
- Entityref ENTITY #IMPLIED
- Fileref CDATA #IMPLIED
- Format NOTATION
- %notationtypes; #IMPLIED
- Id ID #IMPLIED
->
-
-<!ELEMENT InlineGraphic - - CDATA>
-<!ATTLIST InlineGraphic
- Entityref ENTITY #IMPLIED
- Fileref CDATA #IMPLIED
- Format NOTATION
- %notationtypes; #IMPLIED
- Id ID #IMPLIED
->
-
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- EQUATION -->
-<!-- ===================================================================== -->
-
-<!ELEMENT Equation - - ((Title, TitleAbbrev?)?, (InformalEquation |
- %eqncontent.gp;)+) >
-<!ATTLIST Equation
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!ELEMENT InformalEquation - - ((%eqncontent.gp;)+) >
-<!ATTLIST InformalEquation
- %commonatts;
->
-
-<!ELEMENT InlineEquation - - ((%eqncontent.gp;)+) >
-<!ATTLIST InlineEquation
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- TABLE -->
-<!-- ===================================================================== -->
-
-<!--
-
- The CALS table specification derived from MIL-M-28001B. The only
- difference is the content of Entry. InformalTable was derived
- from Table by removing titling and the attributes: Label,
- ShortEntry, and Tocentry.
-
- -->
-
-<!ELEMENT Table - - (Title, TitleAbbrev?, (%tblcontent.gp;))
- -(Table|InformalTable)>
-<!ATTLIST Table
- %commonatts;
- Colsep %yesorno; #IMPLIED
- Frame (Top|Bottom|Topbot|All|Sides|None)
- #IMPLIED
- Label CDATA #IMPLIED
- Orient (Port | Land) #IMPLIED
- Pgwide %yesorno; #IMPLIED
- Rowsep %yesorno; #IMPLIED
- Shortentry %yesorno; #IMPLIED
- Tabstyle NMTOKEN #IMPLIED
- Tocentry %yesorno; %yes;
->
-
-<!ELEMENT InformalTable - - ((%tblcontent.gp;)) -(Table|InformalTable)>
-<!ATTLIST InformalTable
- %commonatts;
- Colsep %yesorno; #IMPLIED
- Frame (Top|Bottom|Topbot|All|Sides|None)
- #IMPLIED
- Orient (Port | Land) #IMPLIED
- Pgwide %yesorno; #IMPLIED
- Rowsep %yesorno; #IMPLIED
- Tabstyle NMTOKEN #IMPLIED
->
-
-<!ELEMENT TGroup - O (ColSpec*, SpanSpec*, THead?, TFoot?, TBody) >
-<!ATTLIST TGroup
- %commonatts;
- Align (Left|Right|Center|Justify|Char)
- Left
- Char CDATA ""
- Charoff NUTOKEN "50"
- Cols NUMBER #REQUIRED
- Colsep %yesorno; #IMPLIED
- Rowsep %yesorno; #IMPLIED
- TGroupStyle NMTOKEN #IMPLIED
->
-
-<!ELEMENT ColSpec - O EMPTY >
-<!ATTLIST ColSpec
- %commonatts;
- Align (Left|Right|Center|Justify|Char)
- #IMPLIED
- Char CDATA #IMPLIED
- Charoff NUTOKEN #IMPLIED
- Colname NMTOKEN #IMPLIED
- Colnum NUMBER #IMPLIED
- Colsep %yesorno; #IMPLIED
- Colwidth CDATA #IMPLIED
- Rowsep %yesorno; #IMPLIED
->
-
-<!ELEMENT SpanSpec - O EMPTY >
-<!ATTLIST SpanSpec
- %commonatts;
- Align (Left|Right|Center|Justify|Char)
- "Center"
- Char CDATA #IMPLIED
- Charoff NUTOKEN #IMPLIED
- Colsep %yesorno; #IMPLIED
- Nameend NMTOKEN #REQUIRED
- Namest NMTOKEN #REQUIRED
- Rowsep %yesorno; #IMPLIED
- Spanname NMTOKEN #REQUIRED
->
-
-<!ELEMENT THead - O (ColSpec*, Row+) -(EntryTbl) >
-<!ATTLIST THead
- %commonatts;
- VAlign (Top | Middle | Bottom)
- "Bottom"
->
-
-<!ELEMENT TFoot - O (ColSpec*, Row+) -(EntryTbl) >
-<!ATTLIST TFoot
- %commonatts;
- VAlign (Top | Middle | Bottom)
- "Top"
->
-
-<!ELEMENT TBody - O (Row+) >
-<!ATTLIST TBody
- %commonatts;
- VAlign (Top | Middle | Bottom)
- "Top"
->
-
-<!ELEMENT Row - O ((Entry | EntryTbl)+) >
-<!ATTLIST Row
- %commonatts;
- Rowsep %yesorno; #IMPLIED
- VAlign (Top | Middle | Bottom)
- #IMPLIED
->
-
-<!ELEMENT Entry - O ((%para.gp; | %admonition.gp; | %list.gp; | Graphic)+ |
- (%inlineobj.gp;)+) >
-<!ATTLIST Entry
- %commonatts;
- Align (Left|Right|Center|Justify|Char)
- #IMPLIED
- Char CDATA #IMPLIED
- Charoff NUTOKEN #IMPLIED
- Colname NMTOKEN #IMPLIED
- Colsep %yesorno; #IMPLIED
- Morerows NUMBER "0"
- Nameend NMTOKEN #IMPLIED
- Namest NMTOKEN #IMPLIED
- Rotate %yesorno; %no;
- Rowsep %yesorno; #IMPLIED
- Spanname NMTOKEN #IMPLIED
- VAlign (Top | Middle | Bottom)
- #IMPLIED
->
-
-<!ELEMENT EntryTbl - - ((ColSpec*, SpanSpec*, THead?, TBody)+)
- -(EntryTbl) >
-<!ATTLIST EntryTbl
- %commonatts;
- Align (Left|Right|Center|Justify|Char)
- #IMPLIED
- Char CDATA #IMPLIED
- Charoff NUTOKEN #IMPLIED
- Colname NMTOKEN #IMPLIED
- Cols NUMBER #REQUIRED
- Colsep %yesorno; #IMPLIED
- Nameend NMTOKEN #IMPLIED
- Namest NMTOKEN #IMPLIED
- Rowsep %yesorno; #IMPLIED
- Spanname NMTOKEN #IMPLIED
- TGroupStyle NMTOKEN #IMPLIED
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- LINKS -->
-<!-- ===================================================================== -->
-
-<!ELEMENT Anchor - O EMPTY >
-<!ATTLIST Anchor
- Id ID #REQUIRED
- Pagenum CDATA #IMPLIED
- Remap CDATA #IMPLIED
- Role CDATA #IMPLIED
- XRefLabel CDATA #IMPLIED
->
-
-<!--
-
- The PageNum attribute of BeginPage, if given, specifies
- the number of the page that begins at that point.
-
- -->
-
-<!ELEMENT BeginPage - O EMPTY >
-<!ATTLIST BeginPage
- Id ID #REQUIRED
- PageNum CDATA #IMPLIED
- Remap CDATA #IMPLIED
- Role CDATA #IMPLIED
- XRefLabel CDATA #IMPLIED
->
-
-<!--
-
- IndexTerms occur in the text flow for generating or linking an
- Index.
-
- -->
-
-<!ELEMENT IndexTerm - O (Primary, ((Secondary, (Tertiary | See | SeeAlso+)?) |
- See | SeeAlso+)?) -(%ndxterm.gp;)>
-<!ATTLIST IndexTerm
- %commonatts;
- Pagenum CDATA #IMPLIED
- Significance (Preferred | Normal)
- Normal
- SpanEnd IDREF #CONREF
->
-
-<!ELEMENT (Primary | Secondary | Tertiary ) - - ((%inlinechar.gp;)+) >
-<!ATTLIST (Primary | Secondary | Tertiary )
- %commonatts;
- SortAs CDATA #IMPLIED
->
-
-<!ELEMENT (See | SeeAlso) - - ((%inlinechar.gp;)+) >
-<!ATTLIST (See | SeeAlso)
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!--
-
- Use of the HyTime terms Linkend and Endterm does not indicate
- that HyTime processing is required. Link has both Endterm and
- Linkend attributes: Linkend is the spot linked to, Endterm
- identifies information that may be used by the Link. You
- might, for example, make the Linkend a Sect2 and make the
- Endterm its Title.
-
- -->
-
-
-<!ELEMENT Link - - ((%inlinechar.gp;)+) >
-<!ATTLIST Link
- Endterm IDREF #IMPLIED
- Linkend IDREF #REQUIRED
- Type CDATA #IMPLIED
->
-
-<!-- ===================================================================== -->
-<!--
-
- Hytimeish link, after Eliot Kimber. TargetDocEnt points
- to an entity in the manner of HyTime's Docorsub; this could
- be an FPI inside a text entity or could be a data entity.
- LinkMode points to a ModeSpec, which may contain
- application-specific information and may appear only in
- DocInfo and BookInfo.
-
- -->
-
-<!ELEMENT OLink - - ((%inlinechar.gp;)+) >
-<!ATTLIST OLink
- TargetDocEnt ENTITY #IMPLIED
- LinkMode IDREF #IMPLIED
- LocalInfo CDATA #IMPLIED
- Type CDATA #IMPLIED
->
-
-<!ELEMENT ModeSpec - - (#PCDATA) >
-<!ATTLIST ModeSpec
- %commonatts;
- Application NOTATION %notationtypes;
- #IMPLIED
->
-
-<!--
- URL link. To point to a filename, use "file://pathname/filename" as
- the value of the URL attribute
- -->
-
-<!ELEMENT ULink - - ((%inlinechar.gp;)+) >
-<!ATTLIST ULink
- URL CDATA #REQUIRED
- Type CDATA #IMPLIED
->
-
-<!ELEMENT FootnoteRef - O (#PCDATA) >
-<!ATTLIST FootnoteRef
- id ID #IMPLIED
- Linkend IDREF #REQUIRED
- Mark CDATA #CONREF
->
-
-<!ELEMENT XRef - O EMPTY >
-<!ATTLIST XRef
- Endterm IDREF #IMPLIED
- Linkend IDREF #REQUIRED
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- DOCINFO -->
-<!-- ===================================================================== -->
-
-<!--
-
- DOCINFO elements; some appear in BiblioEntry, too
-
- -->
-
-<!ELEMENT (Author | Editor | OtherCredit) - - ((Honorific | Firstname |
- Surname | Lineage | OtherName | Affiliation | AuthorBlurb)+) >
-
-<!ELEMENT (AuthorInitials | CorpAuthor | CorpName | Date | Edition | Firstname
- | Holder | Honorific | ISBN | InvPartNumber | Lineage |
- OtherName | ProductNumber | ReleaseInfo | RevNumber |
- RevRemark | Subtitle | Surname | Year ) - - (#PCDATA) >
-
-<!ELEMENT Affiliation - - (ShortAffil?, JobTitle*, OrgName?, OrgDiv*,
- Address*) >
-
-<!ELEMENT JobTitle - - (#PCDATA) >
-
-<!-- ShortAffil is for places like ToCs -->
-<!ELEMENT ShortAffil - - (#PCDATA) >
-
-<!ELEMENT Copyright - - (Year+, Holder*) >
-
-<!ELEMENT LegalNotice - - (Title?, (%para.gp; | BlockQuote)+) >
-
-<!ELEMENT PrintHistory - - ((%para.gp;)+) >
-
-<!ELEMENT ProductName - - ((%inlinechar.gp;)+) >
-<!ATTLIST ProductName
- %commonatts;
- Class (Service|Trade|Registered|Copyright|Logo)
- Trade
->
-
-<!ELEMENT RevHistory - - (Revision*) >
-
-<!ELEMENT Revision - - (RevNumber, Date, AuthorInitials+, RevRemark) >
-
-<!ATTLIST (Author | AuthorInitials | CorpAuthor | OtherCredit | RevHistory)
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- COMPUTER TERM INLINES -->
-<!-- ===================================================================== -->
-
-<!ELEMENT Application - - ((%cptrphrase.gp;)+) >
-<!ATTLIST Application
- %commonatts;
- Class (Hardware|Software)
- #IMPLIED
- MoreInfo (RefEntry|None) None
->
-
-<!ELEMENT Database - - ((%cptrphrase.gp;)+) >
-<!ATTLIST Database
- %commonatts;
- Class (Name|Table|Field|Key1|Key2|Record)
- #IMPLIED
- MoreInfo (RefEntry|None) None
->
-
-<!ELEMENT Interface - - ((%cptrphrase.gp;)+) >
-<!ATTLIST Interface
- %commonatts;
- Class (Button|Icon|Menu|MenuItem)
- #IMPLIED
- MoreInfo (RefEntry|None) None
->
-
-<!ELEMENT MediaLabel - - (#PCDATA) >
-<!ATTLIST MediaLabel
- %commonatts;
- Class (Cartridge|CDRom|Disk|Tape)
- #IMPLIED
->
-
-<!ELEMENT Parameter - - ((%cptrphrase.gp;)+) >
-<!ATTLIST Parameter
- %commonatts;
- Class (Command|Function|Option)
- #IMPLIED
- MoreInfo (RefEntry|None) None
->
-
-<!ELEMENT Replaceable - - ((%phrase.gp;)+) >
-<!ATTLIST Replaceable
- %commonatts;
- Class (Command | Function | Option | Parameter)
- #IMPLIED
->
-
-<!ELEMENT SystemItem - - ((%cptrphrase.gp;)+) >
-<!ATTLIST SystemItem
- %commonatts;
- Class
- (Constant|EnvironVar|Macro|OSname|Prompt|Resource|SystemName)
- #IMPLIED
- MoreInfo (RefEntry|None) None
->
-
-<!ELEMENT (Command | Literal) - - ((%cptrphrase.gp;)+) >
-<!ATTLIST (Command | Literal)
- %commonatts;
- MoreInfo (RefEntry|None) None
->
-
-<!ELEMENT (Action | Filename | Function | Hardware | KeyCap |
- InterfaceDefinition | Property | ProtocolRequest) - -
- ((%cptrphrase.gp;)+) >
-<!ATTLIST (Action | Filename | Function | Hardware | KeyCap |
- InterfaceDefinition | Property | ProtocolRequest)
- %commonatts;
- MoreInfo (RefEntry|None) None
->
-
-<!ELEMENT ComputerOutput - - ((%cptrphrase.gp;)+) >
-<!ATTLIST ComputerOutput
- %commonatts;
- MoreInfo (RefEntry|None) None
->
-
-<!ELEMENT UserInput - - ((%cptrphrase.gp;)+) >
-<!ATTLIST UserInput
- %commonatts;
- MoreInfo (RefEntry|None) None
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!ELEMENT CiteTitle - - ((%cptrphrase.gp;)+) >
-<!ATTLIST CiteTitle
- %commonatts;
- -- The kind of title in a published work being cited. --
- Pubwork (Article|Book|Chapter|RefEntry|Section)
- #IMPLIED
->
-
-<!ELEMENT CiteRefEntry - - (RefEntryTitle, ManVolNum?) >
-<!ATTLIST CiteRefEntry
- %commonatts;
->
-
-<!ELEMENT Option - - ((%cptrphrase.gp;)+) >
-<!ATTLIST Option
- %commonatts;
->
-
-<!ELEMENT Quote - - ((%cptrphrase.gp;)+) >
-<!ATTLIST Quote
- %commonatts;
->
-
-<!ELEMENT Trademark - - ((%cptrphrase.gp;)+) >
-<!ATTLIST Trademark
- %commonatts;
- Class (Service|Trade|Registered|Copyright|Logo)
- Trade
->
-
-<!ELEMENT (Subscript | Superscript) - - ((%phrase.gp; | Replaceable)+) >
-<!ATTLIST (Subscript | Superscript)
- %commonatts;
->
-
-<!ELEMENT SGMLTag - - (#PCDATA) >
-<!ATTLIST SGMLTag
- %commonatts;
- Class (Attribute|Element|GenEntity|ParamEntity)
- #IMPLIED
->
-
-<!ELEMENT (Abbrev | Acronym | Character | Charset | Citation | Classname |
- Emphasis | ErrorName | ErrorType | EventStructure | EventType
- | FirstTerm | Font | ForeignPhrase | Glyph | KeySym | KeyCode
- | LineAnnotation | Markup | Mask | PubsNumber | ReturnValue |
- StructField | StructName | Symbol | Token | Type | VolumeNum |
- WordAsWord) - - (#PCDATA) >
-<!ATTLIST (Abbrev | Acronym | Character | Charset | Citation | Classname |
- Emphasis | ErrorName | ErrorType | EventStructure | EventType
- | FirstTerm | Font | ForeignPhrase | Glyph | KeySym | KeyCode
- | LineAnnotation | Markup | Mask | PubsNumber | ReturnValue |
- StructField | StructName | Symbol | Token | Type | VolumeNum |
- WordAsWord)
-
- %commonatts;
->
-
-<!--
-
- The element named Optional is for use in syntax lines, as in a
- RefEntry, where optional parameters are shown in square
- brackets. Optional should replace those brackets.
-
- -->
-
-<!ELEMENT Optional - - ((%cptrphrase.gp;)+) >
-<!ATTLIST Optional
- %commonatts;
->
-
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- NAVIGATION -->
-<!-- ===================================================================== -->
-
-<!ELEMENT ToC - - (DocInfo?, (Title, TitleAbbrev?)?, ToCfront*, (ToCpart+ |
- ToCchap+), ToCback*) >
-<!ATTLIST ToC
- %commonatts;
->
-
-<!ELEMENT ToCfront - - ((%inlinechar.gp;)+) >
-<!ATTLIST ToCfront
- %commonatts;
- Label CDATA #IMPLIED
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT ToCpart - - ((%inlinechar.gp;)+, ToCchap*) >
-<!ATTLIST ToCpart
- %commonatts;
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT ToCchap - - ((%inlinechar.gp;)+, ToClevel1*) >
-<!ATTLIST ToCchap
- %commonatts;
- Label CDATA #IMPLIED
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT ToClevel1 - - ((%inlinechar.gp;)+, ToClevel2*) >
-<!ATTLIST ToClevel1
- %commonatts;
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT ToClevel2 - - ((%inlinechar.gp;)+, ToClevel3*) >
-<!ATTLIST ToClevel2
- %commonatts;
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT ToClevel3 - - ((%inlinechar.gp;)+, ToClevel4*) >
-<!ATTLIST ToClevel3
- %commonatts;
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT ToClevel4 - - ((%inlinechar.gp;)+, ToClevel5*) >
-<!ATTLIST ToClevel4
- %commonatts;
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT ToClevel5 - - ((%inlinechar.gp;)+) >
-<!ATTLIST ToClevel5
- %commonatts;
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!ELEMENT ToCback - - ((%inlinechar.gp;)+) >
-<!ATTLIST ToCback
- %commonatts;
- Label CDATA #IMPLIED
- Linkend IDREF #IMPLIED
- Pagenum CDATA #IMPLIED
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!ELEMENT LoT - - (DocInfo?, (Title, TitleAbbrev?)?, LoTentry+) >
-<!ATTLIST LoT
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!ELEMENT Bibliography - - (DocInfo?, (Title, TitleAbbrev?)?,
- (%component.gp;)*, (BiblioDiv+ | BiblioEntry+)) >
-<!ATTLIST Bibliography
- %commonatts;
->
-
-<!ELEMENT BiblioDiv - - ((Title, TitleAbbrev?)?, (%component.gp;)*,
- BiblioEntry+) >
-<!ATTLIST BiblioDiv
- %commonatts;
->
-
-<!--
- N.B. this model of BiblioEntry produces info in the order
- "title, author"; TEI prefers "author, title".
- -->
-<!ELEMENT BiblioEntry - - (BiblioMisc?, (ArtHeader | BookBiblio | SeriesInfo),
- BiblioMisc?) >
-<!ATTLIST BiblioEntry
- %commonatts;
->
-
-<!ELEMENT BiblioMisc - - (#PCDATA) >
-<!ATTLIST BiblioMisc
- %commonatts;
->
-
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!ELEMENT Glossary - - (DocInfo?, (Title, TitleAbbrev?)?, (%component.gp;)*,
- (GlossDiv+ | GlossEntry+)) >
-<!ATTLIST Glossary
- %commonatts;
->
-
-<!ELEMENT GlossDiv - - (Title, TitleAbbrev?, (%component.gp;)*,
- GlossEntry+) >
-<!ATTLIST GlossDiv
- %commonatts;
->
-
-<!ELEMENT GlossEntry - - (GlossTerm, Acronym?, Abbrev?, (GlossSee |
- GlossDef+)) >
-<!ATTLIST GlossEntry
- %commonatts;
->
-
-<!ELEMENT GlossTerm - - ((%inlineobj.gp;)+) >
-<!ATTLIST GlossTerm
- %commonatts;
->
-
-<!ELEMENT GlossDef - - ((Comment | %para.gp; | %list.gp; | %object.gp;)+,
- GlossSeeAlso*) >
-<!ATTLIST GlossDef
- %commonatts;
- Subject NMTOKENS #IMPLIED
->
-
-<!ELEMENT GlossSee - O (#PCDATA) >
-<!ATTLIST GlossSee
- %commonatts;
- OtherTerm IDREF #CONREF
->
-
-<!ELEMENT GlossSeeAlso - O (#PCDATA) >
-<!ATTLIST GlossSeeAlso
- %commonatts;
- OtherTerm IDREF #CONREF
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!ELEMENT (SetIndex | Index) - - (DocInfo?, (Title, TitleAbbrev?)?,
- (%component.gp;)*, (IndexDiv+ | IndexEntry+)) >
-<!ATTLIST (SetIndex | Index)
- %commonatts;
->
-
-<!--
-
- The IndexDiv model allows a SegmentedList as the content of
- IndexDiv so SegmentedList can be used for permuted indices.
-
- -->
-
-<!ELEMENT IndexDiv - - ((Title, TitleAbbrev?)?, ((Anchor | Comment |
- %links.gp; | ItemizedList | OrderedList | VariableList |
- %object.gp; | %para.gp;)*, (IndexEntry+ | SegmentedList))) >
-<!ATTLIST IndexDiv
- %commonatts;
->
-
-<!--
-
- IndexEntries appear in the Index, not the text.
-
- -->
-
-<!ELEMENT IndexEntry - - (%primsee, (%secsee)*) >
-<!ATTLIST IndexEntry
- %commonatts;
->
-
-<!ELEMENT PrimaryIE - - (#PCDATA) >
-<!ATTLIST PrimaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED
->
-
-<!ELEMENT SecondaryIE - - (#PCDATA) >
-<!ATTLIST SecondaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED
->
-
-<!ELEMENT TertiaryIE - - (#PCDATA) >
-<!ATTLIST TertiaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED
->
-
-<!ELEMENT SeeIE - - (#PCDATA) >
-<!ATTLIST SeeIE
- %commonatts;
- Linkend IDREF #REQUIRED
->
-
-<!ELEMENT SeeAlsoIE - - (#PCDATA) >
-<!ATTLIST SeeAlsoIE
- %commonatts;
- Linkends IDREFS #REQUIRED
->
-
-<!ELEMENT LoTentry - - ((%inlinechar.gp;)+ ) >
-<!ATTLIST LoTentry
- %commonatts;
- Pagenum CDATA #IMPLIED
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- REFERENCE ENTRIES -->
-<!-- ===================================================================== -->
-
-<!ELEMENT RefEntry - - (DocInfo?, RefMeta?, (Comment | %links.gp;)*,
- RefNameDiv, RefSynopsisDiv?, RefSect1+) >
-<!ATTLIST RefEntry
- %commonatts;
->
-
-<!ELEMENT RefMeta - - (RefEntryTitle, ManVolNum?, RefMiscInfo*) >
-<!ATTLIST RefMeta
- %commonatts;
->
-
-<!ELEMENT RefEntryTitle - - ((%inlinechar.gp;)+) >
-<!ATTLIST RefEntryTitle
- %commonatts;
->
-
-<!ELEMENT ManVolNum - - (#PCDATA) >
-<!ATTLIST ManVolNum
- %commonatts;
->
-
-<!ELEMENT RefMiscInfo - - (#PCDATA) >
-<!ATTLIST RefMiscInfo
- %commonatts;
- Class CDATA #IMPLIED
->
-
-<!ELEMENT RefNameDiv - - (RefDescriptor?, RefName+, RefPurpose, RefClass?,
- (Comment | %links.gp;)*) >
-<!ATTLIST RefNameDiv
- %commonatts;
->
-
-<!ELEMENT RefDescriptor - - (#PCDATA) >
-<!ATTLIST RefDescriptor
- %commonatts;
->
-
-<!ELEMENT RefName - - ((#PCDATA | %computerterms.gp;)+) >
-<!ATTLIST RefName
- %commonatts;
->
-
-<!ELEMENT RefPurpose - - ((%inlinechar.gp;)+) >
-<!ATTLIST RefPurpose
- %commonatts;
->
-
-<!ELEMENT RefClass - - ((%refclass.gp;)+) >
-
-<!ELEMENT RefSynopsisDiv - - ((Title, TitleAbbrev?)?, (((%synop.gp;)+,
- RefSect2*) | (RefSect2+))) >
-<!ATTLIST RefSynopsisDiv
- %commonatts;
->
-
-<!ELEMENT RefSect1 - - (Title, TitleAbbrev?, (((%component.gp;)+, RefSect2*) |
- RefSect2+)) >
-<!ATTLIST RefSect1
- %commonatts;
->
-
-<!ELEMENT RefSect2 - - (Title, TitleAbbrev?, (((%component.gp;)+, RefSect3*) |
- RefSect3+)) >
-<!ATTLIST RefSect2
- %commonatts;
->
-
-<!ELEMENT RefSect3 - - (Title, TitleAbbrev?, (%component.gp;)+) >
-<!ATTLIST RefSect3
- %commonatts;
->
-
-<!ELEMENT Synopsis - - ((LineAnnotation | Optional | %inlinechar.gp; |
- Graphic)+) >
-<!ATTLIST Synopsis
- %commonatts;
- Format NOTATION
- (linespecific) linespecific
- Label CDATA #IMPLIED
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!-- Example command synopsis in typical UNIX(tm) format:
-
- rm [-f] [-r] [-i] [-] {filename|dirname}...
- ^ ^ ^ ^ ^ ^ ^ ^ ^
- | | | | | | | | |
- | optional args | | | repeat indicator
- | (contain options)| | |
- | | | second child of group
- command name | |
- | first child of group
- |
- required repeatable group
-
- SGML source for this example:
-
- <CMDSYNOPSIS>
- <COMMAND>rm</COMMAND>
- <ARG Choice="opt">-f</ARG> (<OPTION> not required for arg
- contents unless doing extra-special
- processing)
- <ARG Choice="opt">-r</ARG>
- <ARG Choice="opt">-i</ARG>
- <ARG Choice="opt">-</ARG> (UNIX(tm) synopsis format or other
- format can be generated)
- <GROUP Choice="req" Rep="repeat">
- <REPLACEABLE>filename</REPLACEABLE>
- <REPLACEABLE>dirname</REPLACEABLE>
- </GROUP>
- </CMDSYNOPSIS>
--->
-
-<!ELEMENT CmdSynopsis - - ((Arg | Group)*, Command, (Arg | Group)*,
- SynopFragment*) >
-<!ATTLIST CmdSynopsis
- %commonatts;
- Label CDATA #IMPLIED
- Sepchar CDATA " "
->
-
-<!ELEMENT Arg - - ((#PCDATA | Arg | Group | Option | SynopFragmentRef |
- Replaceable)+) >
-<!ATTLIST Arg
- %commonatts;
- %argchcatt;
- %repatt;
->
-
-<!ELEMENT Group - - ((Arg | Group | SynopFragmentRef | Replaceable)+) >
-<!ATTLIST Group
- %commonatts;
- %grpchcatt;
- %repatt;
->
-
-<!ELEMENT SynopFragmentRef - - RCDATA >
-<!ATTLIST SynopFragmentRef
- %commonatts;
- Linkend IDREF #REQUIRED -- to Fragment --
->
-
-<!ELEMENT SynopFragment - - ((Arg | Group)+) >
-<!ATTLIST SynopFragment
- Id ID #REQUIRED
- Lang CDATA #IMPLIED
- Remap CDATA #IMPLIED
- Role CDATA #IMPLIED
- XRefLabel CDATA #IMPLIED
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-
-<!ELEMENT FuncSynopsis - - (FuncSynopsisInfo?, ((FuncDef, (void | varargs |
- ParamDef+)))+ ) >
-<!ATTLIST FuncSynopsis
- %commonatts;
- Label CDATA #IMPLIED
->
-
-<!ELEMENT FuncSynopsisInfo - - ((LineAnnotation | Optional | %cptrphrase.gp;)*
- ) >
-<!ATTLIST FuncSynopsisInfo
- %commonatts;
- Format NOTATION
- (linespecific) linespecific
->
-
-<!ELEMENT FuncDef - - ((#PCDATA | Replaceable | Function)*) >
-<!ATTLIST FuncDef
- %commonatts;
->
-
-<!ELEMENT void - O EMPTY >
-<!ATTLIST void
- %commonatts;
->
-
-<!ELEMENT varargs - O EMPTY >
-<!ATTLIST varargs
- %commonatts;
->
-
-<!--
-
- Processing assumes that only one Parameter will appear in a
- ParamDef, and that funcparams will be used at most once, for
- providing information on the "inner parameters" for parameters
- that are pointers to functions.
-
- -->
-
-<!ELEMENT ParamDef - - ((#PCDATA | Replaceable | Parameter | FuncParams)*) >
-<!ATTLIST ParamDef
- %commonatts;
->
-
-<!ELEMENT FuncParams - - ((%cptrphrase.gp;)*) >
-<!ATTLIST FuncParams
- %commonatts;
->
-
-<!-- ===================================================================== -->
-<!-- ##################################################################### -->
-<!-- ===================================================================== -->
-<!-- ARTICLE -->
-<!-- ===================================================================== -->
-
-<!-- This Article model is derived from the MAJOUR header DTD.
-
- CHANGES from MAJOUR:
- - Gnomic element names (oad, onm, odv, oid, kwdg, cgn, cgs, cnm . . .)
- have been replaced by understandable ones.
- - Quite a few elements have been dropped; others that already exist
- in Docbook have been substituted for the Majour ones.
- - Some of the modularity has been suppressed, empty elements
- containing pointers have been eliminated, and occurrence
- indicators have been changed ad lib.
- - Affiliation has been nested inside Author, instead of inside
- AuthorGroup.
- - JournalInfo info has been folded into BookBiblio inside BookInfo,
- cf. also BiblioEntry. Some of this info lies elsewhere in
- the Majour model.
-
- A journal or anthology is a Book in Docbook, and the meta for
- a journal is permitted in BookInfo. Articles (Chapters)
- within a journal or anthology have ArtHeaders, which may
- contain the same info.
--->
-
-<!ELEMENT Article - - (ArtHeader, (%sect1.gp;), ((%nav.gp;) | (%appendix.gp;)
- | Ackno)*) >
-<!ATTLIST Article
- %commonatts;
- ParentBook IDREF #IMPLIED
->
-
-<!--
-
- ArtPageNums are the page numbers of the article as published.
- -->
-
-<!ELEMENT ArtHeader - - (Title, TitleAbbrev?, Subtitle?, AuthorGroup+,
- BookBiblio?, ArtPageNums, Abstract*, ConfGroup*, (ContractNum
- | ContractSponsor)*) >
-<!ATTLIST ArtHeader
- %commonatts;
->
-
-<!ELEMENT ArtPageNums - - (#PCDATA) >
-
-<!ELEMENT Ackno - - (#PCDATA) >
-
-<!ELEMENT Address - - (Street | POB | Postcode | City | State | Country |
- Phone | Fax | Email)*>
-
-<!ELEMENT (Street | POB | Postcode | City | State | Country | Phone | Fax |
- Email) - - (#PCDATA) >
-
-<!ELEMENT (OrgName | OrgDiv) - - (#PCDATA) >
-
-<!ELEMENT AuthorGroup - - ((CorpAuthor | Collab | Author)+) >
-
-<!ELEMENT Collab - - (CollabName, Affiliation*) >
-
-<!ELEMENT CollabName - - (#PCDATA) >
-
-<!ELEMENT ConfDates - - (#PCDATA) >
-
-<!ELEMENT ConfGroup - - ((ConfDates | ConfTitle | ConfNum | Address |
- ConfSponsor)*) >
-
-<!ELEMENT ConfNum - - (#PCDATA) >
-
-<!ELEMENT ConfSponsor - - (#PCDATA) >
-
-<!ELEMENT ConfTitle - - (#PCDATA) >
-
-<!ELEMENT ContractNum - - (#PCDATA) >
-
-<!ELEMENT ContractSponsor - - (#PCDATA) >
-
-<!ELEMENT ISSN - - (#PCDATA) >
-
-<!ELEMENT IssueNum - - (#PCDATA) >
-
-<!ELEMENT PageNums - - (#PCDATA) >
-
-<!ELEMENT PubDate - - (#PCDATA) >
-
-<!ELEMENT Publisher - - (PublisherName, Address*) >
-
-<!ELEMENT PublisherName - - (#PCDATA) >
-
-<!ELEMENT SeriesVolNums - - (#PCDATA) >
-
-<!-- ===================================================================== -->
-<!-- End of the DocBook DTD -->
-<!-- ===================================================================== -->
-
+++ /dev/null
-<!SGML "ISO 8879:1986"
--- SGML declaration with Reference Concrete Syntax modifications --
-
--- DocBook DTD
- Release 1.0, Copyright 1992 HaL Computer Systems, Inc., and
- O'Reilly & Associates, Inc.
-
- Permission to use, copy, modify and distribute the DocBook DTD and
- its accompanying documentation for any purpose and without fee is
- hereby granted, provided that this copyright notice appears in all
- copies. HaL Computer Systems and O'Reilly & Associates make no
- representation about the suitability of the DTD for any purpose.
- It is provided "as is" without expressed or implied warranty.
-
- The DocBook DTD is maintained by O'Reilly & Associates. Please
- direct all questions, bug reports, or suggestions for changes to
- dtd@ora.com or by mail to: Terry Allen, O'Reilly & Associates, Inc.,
- 103A Morris Street, Sebastopol, California, 95472.
-
- --
-
-CHARSET
- BASESET "ISO 646:1983//CHARSET
- International Reference Version (IRV)//ESC 2/5 4/0"
- DESCSET 0 9 UNUSED
- 9 2 9
- 11 2 UNUSED
- 13 1 13
- 14 18 UNUSED
- 32 95 32
- 127 1 UNUSED
-
-CAPACITY SGMLREF
- TOTALCAP 150000
- GRPCAP 150000
-
-SCOPE DOCUMENT
-SYNTAX
- SHUNCHAR CONTROLS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
- 19 20 21 22 23 24 25 26 27 28 29 30 31 127 255
- BASESET "ISO 646:1983//CHARSET
- International Reference Version (IRV)//ESC 2/5 4/0"
- DESCSET 0 128 0
- FUNCTION RE 13
- RS 10
- SPACE 32
- TAB SEPCHAR 9
- NAMING LCNMSTRT ""
- UCNMSTRT ""
- LCNMCHAR ".-"
- UCNMCHAR ".-"
- NAMECASE GENERAL YES
- ENTITY NO
- DELIM GENERAL SGMLREF
- SHORTREF SGMLREF
- NAMES SGMLREF
- QUANTITY SGMLREF
- NAMELEN 34
- TAGLVL 100
- LITLEN 1024
- GRPGTCNT 150
- GRPCNT 64
-
-FEATURES
- MINIMIZE
- DATATAG NO
- OMITTAG NO
- RANK NO
- SHORTTAG YES
- LINK
- SIMPLE NO
- IMPLICIT NO
- EXPLICIT NO
- OTHER
- CONCUR NO
- SUBDOC NO
- FORMAL NO
- APPINFO NONE
->
-
-
-<!DOCTYPE Docbook [
-<!-- Publicly declared External Entities -->
-
-<!-- Uncomment the ENTITY declaration for your application. -->
-
-<!--
-<!ENTITY % ISOamsa PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Arrow Relations//EN">
- %ISOamsa;
- -->
-<!--
-<!ENTITY % ISOamsa SYSTEM "iso-amsa.gml">
- %ISOamsa;
- -->
-
-<!--
-<!ENTITY % ISOamsb PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Binary Operators//EN">
- %ISOamsb;
- -->
-<!--
-<!ENTITY % ISOamsb SYSTEM "iso-amsb.gml">
- %ISOamsb;
- -->
-
-<!--
-<!ENTITY % ISOamsc PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Delimiters//EN">
- %ISOamsc;
- -->
-<!--
-<!ENTITY % ISOamsc SYSTEM "iso-amsc.gml">
- %ISOamsc;
- -->
-
-<!--
-<!ENTITY % ISOamsn PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Negated Relations//EN">
- %ISOamsn;
- -->
-<!--
-<!ENTITY % ISOamsn SYSTEM "iso-amsn.gml">
- %ISOamsn;
- -->
-
-<!--
-<!ENTITY % ISOamso PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Ordinary//EN">
- %ISOamso;
- -->
-<!--
-<!ENTITY % ISOamso SYSTEM "iso-amso.gml">
- %ISOamso;
- -->
-
-<!--
-<!ENTITY % ISOamsr PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Relations//EN">
- %ISOamsr;
- -->
-<!--
-<!ENTITY % ISOamsr SYSTEM "iso-amsr.gml">
- %ISOamsr;
- -->
-
-<!--
-<!ENTITY % ISObox PUBLIC "ISO 8879:1986//ENTITIES Box and Line Drawing//EN">
- %ISObox;
- -->
-<!--
-<!ENTITY % ISObox SYSTEM "iso-box.gml">
- %ISObox;
- -->
-
-<!--
-<!ENTITY % ISOcyr1 PUBLIC "ISO 8879:1986//ENTITIES Russian Cyrillic//EN">
- %ISOcyr1;
- -->
-<!--
-<!ENTITY % ISOcyr1 SYSTEM "iso-cyr1.gml">
- %ISOcyr1;
- -->
-
-<!--
-<!ENTITY % ISOcyr2 PUBLIC "ISO 8879:1986//ENTITIES Non-Russian Cyrillic//EN">
- %ISOcyr2;
- -->
-<!--
-<!ENTITY % ISOcyr2 SYSTEM "iso-cyr2.gml">
- %ISOcyr2;
- -->
-
-<!--
-<!ENTITY % ISOdia PUBLIC "ISO 8879:1986//ENTITIES Diacritical Marks//EN">
- %ISOdia;
- -->
-<!--
-<!ENTITY % ISOdia SYSTEM "iso-dia.gml">
- %ISOdia;
- -->
-
-<!--
-<!ENTITY % ISOgrk1 PUBLIC "ISO 8879:1986//ENTITIES Greek Letters//EN">
- %ISOgrk1;
- -->
-<!--
-<!ENTITY % ISOgrk1 SYSTEM "iso-grk1.gml">
- %ISOgrk1;
- -->
-
-<!--
-<!ENTITY % ISOgrk2 PUBLIC "ISO 8879:1986//ENTITIES Monotoniko Greek//EN">
- %ISOgrk2;
- -->
-<!--
-<!ENTITY % ISOgrk2 SYSTEM "iso-grk2.gml">
- %ISOgrk2;
- -->
-
-<!--
-<!ENTITY % ISOgrk3 PUBLIC "ISO 8879:1986//ENTITIES Greek Symbols//EN">
- %ISOgrk3;
- -->
-<!--
-<!ENTITY % ISOgrk3 SYSTEM "iso-grk3.gml">
- %ISOgrk3;
- -->
-
-<!--
-<!ENTITY % ISOlat1 PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN">
- %ISOlat1;
- -->
-<!--
-<!ENTITY % ISOlat1 SYSTEM "iso-lat1.gml">
- %ISOlat1;
- -->
-
-<!--
-<!ENTITY % ISOlat2 PUBLIC "ISO 8879:1986//ENTITIES Added Latin 2//EN">
- %ISOlat2;
- -->
-<!--
-<!ENTITY % ISOlat2 SYSTEM "iso-lat2.gml">
- %ISOlat2;
- -->
-
-<!--
-<!ENTITY % ISOnum PUBLIC "ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN">
- %ISOnum;
- -->
-<!--
-<!ENTITY % ISOnum SYSTEM "iso-num.gml">
- %ISOnum;
- -->
-
-<!--
-<!ENTITY % ISOpub PUBLIC "ISO 8879:1986//ENTITIES Publishing//EN">
- %ISOpub;
- -->
-<!--
-<!ENTITY % ISOpub SYSTEM "iso-pub.gml">
- %ISOpub;
- -->
-
-<!--
-<!ENTITY % ISOtech PUBLIC "ISO 8879:1986//ENTITIES General Technical//EN">
- %ISOtech;
- -->
-<!--
-<!ENTITY % ISOtech SYSTEM "iso-tech.gml">
- %ISOtech;
- -->
-
-<!-- Parameter Entities -->
-<!-- These are reuseable groups of entities and elements, collected to make
- revision, augmentation, and maintenance of this DTD easier. -->
-
-<!-- Book Components -->
-<!ENTITY % bookcomponent.gp "((Preface)|(TitlePage)|(ToC)|(LoT)|(Chapter)|(Appendix)|(Bibliography)|(Glossary)|(Index)|(Reference))" >
-
-<!-- Contents that can appear almost anywhere -->
-<!ENTITY % basechar.gp "((#PCDATA)|(VarParam)|(Anchor))" >
-
-<!-- Contents that can appear in most contexts, in-line -->
-<!ENTITY % inlinechar.gp "(((%basechar.gp;))|(FootnoteRef)|(Command)|(Filename)|(Flag)|(Function)|(Application)|(Hardware)|(Interface)|(CiteBook)|(CiteChap)|(CiteSect)|(FirstTerm)|(GlossaryTerm)|(IndexTerm)|(ComputerOutput)|(UserInput)|(Subscript)|(Superscript)|(Quote)|(Citation)|(Footnote)|(Link)|(XRef)|(Emphasis)|(OopsChar)|(wordasword)|(systemitem))" >
-
-<!-- Contents for the element VarParam -->
-<!ENTITY % varparam.content.gp "((#PCDATA)|(Superscript)|(Subscript))" >
-
-<!-- Contents for citations of Titles -->
-<!ENTITY % cite.title.content.gp "((#PCDATA)|(Command)|(Filename)|(Flag)|(Function)|(Application)|(Hardware)|(Interface)|(UserInput)|(ComputerOutput)|(Footnote)|(Subscript)|(Superscript))" >
-
-<!-- Contents for the element GlossaryTerm -->
-<!ENTITY % glossterm.content.gp "((#PCDATA)|(Command)|(Filename)|(Function)|(Application)|(Hardware)|(Interface))" >
-
-<!-- Contents for the element UserInput -->
-<!ENTITY % uicontent.gp "(((%basechar.gp;))|(Command)|(Filename)|(Flag)|(Function)|(Application)|(Hardware)|(Interface)|(OopsChar))" >
-
-<!-- Contents for the elements Subscript and Superscript -->
-<!ENTITY % script.content.gp "((#PCDATA)|(VarParam))" >
-
-<!-- Contents for the element Quote -->
-<!ENTITY % quote.content.gp "(((%basechar.gp;))|(FootnoteRef)|(Command)|(Filename)|(Flag)|(Function)|(Application)|(Hardware)|(Interface)|(CiteBook)|(CiteChap)|(CiteSect)|(GlossaryTerm)|(IndexTerm)|(UserInput)|(ComputerOutput)|(Subscript)|(Superscript)|(Footnote)|(Citation)|(XRef)|(Emphasis)|(OopsChar))" >
-
-<!-- Contents for other parameter entities.
- These are all the varieties of lists. -->
-<!ENTITY % list.gp "((ItemizedList)|(OrderedList)|(VariableList)|(AdmonitionList))" >
-
-<!-- More elements for other parameter entities -->
-<!ENTITY % literallayout.gp "((Example)|(LiteralLayout)|(Screen))" >
-
-<!-- More elements for other parameter entities -->
-<!ENTITY % object.gp "((Graphic)|(Equation)|(Table)|(Admonition)|(BlockQuote)|((%literallayout.gp;)))" >
-
-<!-- More elements for other parameter entities -->
-<!ENTITY % component.gp "((Anchor)|(Para)|(Highlights)|(Epigraph)|((%list.gp;))|((%object.gp;))|(Oops)|(Comment)|(Figure)|(IndexTerm)|(Sidebar))" >
-
-<!-- Contents for the elements Para and BlockQuote -->
-<!ENTITY % paracontent.gp "(((%inlinechar.gp;))|(Comment)|(Graphic)|(Equation))" >
-
-<!-- Contents for the element Example -->
-<!ENTITY % examplecontent.gp "(Screen|LiteralLayout|ProgramListing)" >
-
-<!-- Contents for the element ListItem -->
-<!ENTITY % listcontent.gp "((Para)|((%list.gp;))|(Figure)|((%object.gp;))|(Oops)|(Comment))" >
-
-<!-- Contents for the element Admonition -->
-<!ENTITY % admoncontent.gp "((Para)|((%list.gp;))|((%object.gp;))|(Oops)|(Comment)|(IndexTerm))" >
-
-<!-- Elements comprising the body of a Table -->
-<!ENTITY % tablecontent.gp "(TableSpec?, TableColHead*, TableRow+)" >
-
-<!-- Contents for the elements ProgramListing, LiteralLayout, Screen, and RefSynopsisblock -->
-<!ENTITY % literalcontent.gp "(((%inlinechar.gp;))|(Comment))" >
-
-<!-- Contents for the element Oops -->
-<!ENTITY % oopscontent.gp "(((%inlinechar.gp;))|(Para)|((%list.gp;))|(Figure)|((%object.gp;))|(Comment))" >
-
-<!-- Contents for the element Figure -->
-<!ENTITY % figurecontent.gp "(((%object.gp;))|(Oops)|(Comment)|(IndexTerm))" >
-
-<!-- Contents for the element Sidebar -->
-<!ENTITY % Sbcontent.gp "((Para)|((%list.gp;))|((%object.gp;)))" >
-
-<!-- Contents for the element Link -->
-<!ENTITY % linkcontent.gp "(((%basechar.gp;))|(CiteBook)|(CiteChap)|(CiteSect)|(Command)|(Filename)|(Flag)|(Function)|(Application)|(Hardware)|(Interface)|(OopsChar)|(Subscript)|(Superscript))" >
-
-<!-- The headX.gp parameter entities handle nesting of heads. -->
-<!ENTITY % head1.gp "(((%component.gp;)+, (Head1|RefEntry)*)|(Head1|RefEntry)+)" >
-
-<!ENTITY % head2.gp "(((%component.gp;)+, Head2*)|(Head2+))" >
-
-<!ENTITY % head3.gp "(((%component.gp;)+, Head3*)|(Head3+))" >
-
-<!ENTITY % head4.gp "(((%component.gp;)+, Head4*)|(Head4+))" >
-
-<!ENTITY % head5.gp "(((%component.gp;)+, Head5*)|(Head5+))" >
-
-<!-- Contents for the element IndexEntry -->
-<!ENTITY % indexcontent.gp "(((%basechar.gp;))|(Command)|(Filename)|(Flag)|(Function)|(Application)|(Hardware)|(Interface)|(CiteBook)|(CiteChap)|(CiteSect)|(OopsChar)|(Emphasis)|(ComputerOutput))" >
-
-<!-- Contents for the element TitlePage -->
-<!ENTITY % titlepagecontent.gp "((Author)|(Date)|(Copyright)|(ISBN)|(LegalNotice)|(RevHistory)|(TitleBook)|(Editor)|(Edition)|(PrintHistory)|(Publisher)|(Series))" >
-
-<!-- Two parameter entities for the element IndexTerm, handling nesting -->
-<!ENTITY % Secondarynest "((Tertiary)|(See)|(SeeAlso))" >
-
-<!ENTITY % Primarynest "((Secondary, (%Secondarynest;)?)|(See)|(SeeAlso))" >
-
-<!-- A parameter entity for the next parameter entity -->
-<!ENTITY % refname.gp "(RefDescriptor?, RefName+, RefPurpose)" >
-
-<!-- Contents for the element RefNameDiv -->
-<!ENTITY % refnamediv.content.gp "(((%refname.gp;))|(Comment)|(IndexTerm))" >
-
-<!-- Contents for some elements in RefEntry -->
-<!ENTITY % refname.content.gp "(((%basechar.gp;))|(Command)|(Filename)|(Function)|(Application)|(Hardware)|(Interface)|(OopsChar))" >
-
-<!-- Contents for the element RefHead1 -->
-<!ENTITY % refdivbody.gp "(((%component.gp;)+, RefHead2*)|(RefHead2+))" >
-
-
-
-<!-- Document Structure -->
-
-<!-- Base element -->
-<!ELEMENT DocBook - - (Comment*, (%bookcomponent.gp;)+)>
-
-<!-- Most of the book component elements -->
-<!ELEMENT TitlePage - - ((%titlepagecontent.gp;)+)>
- <!ATTLIST TitlePage id ID #IMPLIED>
-
-<!ELEMENT Chapter - - (Title, TitleAbbrev?, (%head1.gp;))>
- <!ATTLIST Chapter id ID #IMPLIED
- Number CDATA #IMPLIED>
-
-<!ELEMENT Preface - - (Title, TitleAbbrev?, (%head1.gp;))>
- <!ATTLIST Preface id ID #IMPLIED>
-
-<!ELEMENT ToC - - (Title, TitleAbbrev?, ToCentry1+)>
- <!ATTLIST ToC id ID #IMPLIED>
-
-<!ELEMENT LoT - - (Title, TitleAbbrev?, LoTentry+)>
- <!ATTLIST LoT id ID #IMPLIED>
-
-<!ELEMENT Appendix - - (Title, TitleAbbrev?, (%head1.gp;))>
- <!ATTLIST Appendix id ID #IMPLIED
- Number CDATA #IMPLIED>
-
-<!ELEMENT Bibliography - - (Title, TitleAbbrev?, (%head1.gp;))>
- <!ATTLIST Bibliography id ID #IMPLIED>
-
-<!ELEMENT Glossary - - (Title, TitleAbbrev?, GlossaryEntry+)>
- <!ATTLIST Glossary id ID #IMPLIED>
-
-<!ELEMENT Index - - (Para*, IndexEntry+)>
- <!ATTLIST Index id ID #IMPLIED>
-
-<!ELEMENT Reference - - (Title, TitleAbbrev?, RefEntry+)>
- <!ATTLIST Reference id ID #IMPLIED>
-
-<!-- Most of the in-line elements -->
-<!ELEMENT Comment - - ((%inlinechar.gp;)+)>
-
-<!ELEMENT VarParam - - ((%varparam.content.gp;)+)>
-
-<!ELEMENT Anchor - O EMPTY>
- <!ATTLIST Anchor id ID #IMPLIED>
-
-<!ELEMENT Command - - ((%basechar.gp;)+)>
- <!ATTLIST Command RefEntry (Yes|No) No >
-
-<!ELEMENT Filename - - ((%basechar.gp;)+)>
- <!ATTLIST Filename RefEntry (Yes|No) No >
-
-<!ELEMENT Flag - - ((%basechar.gp;)+)>
-
-<!ELEMENT Application - - ((%basechar.gp;)+)>
- <!ATTLIST Application RefEntry (Yes|No) No >
-
-<!ELEMENT Function - - ((%basechar.gp;)+)>
- <!ATTLIST Function RefEntry (Yes|No) No >
-
-<!ELEMENT Hardware - - ((%basechar.gp;)+)>
-
-<!ELEMENT Interface - - ((%basechar.gp;)+)>
-
-<!ELEMENT CiteBook - - ((%cite.title.content.gp;)+)>
-
-<!ELEMENT CiteChap - - ((%cite.title.content.gp;)+)>
-
-<!ELEMENT CiteSect - - ((%cite.title.content.gp;)+)>
-
-<!ELEMENT FirstTerm - - (#PCDATA)>
-
-<!ELEMENT GlossaryTerm - - ((%glossterm.content.gp;)+)>
-
-<!ELEMENT ComputerOutput - - ((%basechar.gp;)+)>
-
-<!ELEMENT UserInput - - ((%uicontent.gp;)+)>
-
-<!ELEMENT Subscript - - ((%script.content.gp;)+)>
-
-<!ELEMENT Superscript - - ((%script.content.gp;)+)>
-
-<!ELEMENT Quote - - ((%quote.content.gp;)+)>
-
-<!ELEMENT Citation - - (#PCDATA)>
-
-<!ELEMENT Emphasis - - (#PCDATA)>
-
-<!ELEMENT OopsChar - - ((%inlinechar.gp;)+)>
-
-<!ELEMENT WordAsWord - - (#PCDATA)>
-
-<!ELEMENT SystemItem - - ((%basechar.gp;)+)>
-
-<!ELEMENT Link - - ((%linkcontent.gp;)+)>
- <!ATTLIST Link Target IDREF #IMPLIED
- Type CDATA #IMPLIED>
-
-<!ELEMENT FootnoteRef - O EMPTY>
- <!ATTLIST FootnoteRef Target IDREF #IMPLIED
- Mark CDATA #IMPLIED>
-
-<!ELEMENT XRef - O (#PCDATA)>
- <!ATTLIST XRef Target IDREF #CONREF
- Type (Figure|Example|Table|Footnote|Chapter|Section|Sidebar) #IMPLIED>
-
-<!-- Contents for indexing terms in the text (not in the Index) -->
-<!ELEMENT IndexTerm - - (Primary, (%Primarynest;)?)>
- <!ATTLIST IndexTerm id ID #IMPLIED
- Span (Start|End) #IMPLIED
- Pagenum CDATA #IMPLIED>
-
-<!ELEMENT Primary - - ((%indexcontent.gp;))>
-
-<!ELEMENT Secondary - - ((%indexcontent.gp;))>
-
-<!ELEMENT Tertiary - - ((%indexcontent.gp;))>
-
-<!ELEMENT See - - ((%indexcontent.gp;))>
-
-<!ELEMENT SeeAlso - - ((%indexcontent.gp;))>
-
-<!-- Parts of a book component, sort of like objects, with some of the
- elements that belong to them specifically -->
-<!ELEMENT Head1 - - (Title, TitleAbbrev?, (%head2.gp;))>
- <!ATTLIST (Head1|Head2|Head3|Head4|Head5)
- id ID #IMPLIED
- Number CDATA #IMPLIED>
-
-<!ELEMENT Head2 - - (Title, TitleAbbrev?, (%head3.gp;))>
-
-<!ELEMENT Head3 - - (Title, TitleAbbrev?, (%head4.gp;))>
-
-<!ELEMENT Head4 - - (Title, TitleAbbrev?, (%head5.gp;))>
-
-<!ELEMENT Head5 - - (Title, TitleAbbrev?, (%component.gp;)+)>
-
-<!ELEMENT Footnote - - ((%component.gp;)+)>
- <!ATTLIST Footnote id ID #IMPLIED>
-
-<!ELEMENT Epigraph - - ((Para)+)>
-
-<!ELEMENT Para - - ((%paracontent.gp;)+)>
-
-<!ELEMENT Highlights - - (((%list.gp;)|Para|(Admonition))+)>
- <!ATTLIST Highlights id ID #IMPLIED>
-
-<!ELEMENT Graphic - - RCDATA>
- <!ATTLIST Graphic id ID #IMPLIED
- Type (GIF|TIFF|DVI|EPS|tbl|Tex|bitmap) GIF >
-
-<!ELEMENT ItemizedList - - (ListItem+)>
- <!ATTLIST ItemizedList Mark CDATA #IMPLIED>
-
-<!ELEMENT ListItem - - ((%listcontent.gp;)+)>
-
-<!ELEMENT OrderedList - - (ListItem+)>
- <!ATTLIST OrderedList Numeration (Arabic|Upperalpha|Loweralpha|Upperroman|Lowerroman) Arabic
- Continuation (Yes|No) No >
-
-<!ELEMENT VariableList - - ((Term+, ListItem)+)>
-
-<!ELEMENT Term - - ((%inlinechar.gp;)+)>
-
-<!ELEMENT AdmonitionList - - (ListItem+)>
- <!ATTLIST AdmonitionList Heading CDATA #IMPLIED>
-
-<!ELEMENT Admonition - - ((%admoncontent.gp;)+)>
- <!ATTLIST Admonition Heading CDATA #IMPLIED>
-
-<!ELEMENT Equation - - (Title?, TitleAbbrev?, Graphic)>
- <!ATTLIST Equation id ID #IMPLIED>
-
-<!ELEMENT Title - - ((%inlinechar.gp;)+)>
- <!ATTLIST Title id ID #IMPLIED
- Pagenum CDATA #IMPLIED>
-
-<!ELEMENT TitleAbbrev - - ((%inlinechar.gp;)+)>
-
-<!ELEMENT BlockQuote - - ((%paracontent.gp;)+)>
-
-<!ELEMENT Example - - (Title?, TitleAbbrev?, (%examplecontent.gp;))>
- <!ATTLIST Example id ID #IMPLIED>
-
-<!ELEMENT ProgramListing - - ((%literalcontent.gp;)+)>
-
-<!ELEMENT LiteralLayout - - ((%literalcontent.gp;)+)>
-
-<!ELEMENT Screen - - (((%literalcontent.gp;)+) | (ScreenInfo, Graphic))>
- <!ATTLIST Screen id ID #IMPLIED>
-
-<!ELEMENT ScreenInfo - - (#PCDATA)>
-
-<!ELEMENT Oops - - ((%oopscontent.gp;)+)>
-
-<!ELEMENT Figure - - (Title, TitleAbbrev?, ((%figurecontent.gp;)+)*)>
- <!ATTLIST Figure id ID #IMPLIED
- Height CDATA #IMPLIED
- Width CDATA #IMPLIED
- Align (l|c|r) l
- Float (YES|NO) NO >
-
-<!ELEMENT Sidebar - - (Title, TitleAbbrev?, (%Sbcontent.gp;)+)>
- <!ATTLIST Sidebar id ID #IMPLIED>
-
-<!-- Table elements, provisional -->
-<!ELEMENT Table - - (Title?, TitleAbbrev?, Graphic?, (%tablecontent.gp;))>
- <!ATTLIST Table id ID #IMPLIED>
-
-<!ELEMENT TableSpec - - (%inlinechar.gp;)>
-
-<!ELEMENT TableColHead - - (TableCell+)>
-
-<!ELEMENT TableCell - - ((%inlinechar.gp;)+)>
-
-<!ELEMENT TableRow - - (TableCell+)>
-
-<!ELEMENT GlossaryEntry - - (#PCDATA)>
-
-<!ELEMENT IndexEntry - - ((%indexcontent.gp;)*)>
- <!ATTLIST IndexEntry id IDREFS #IMPLIED>
-
-<!ELEMENT LoTentry - - ((%inlinechar.gp;)+ )>
- <!ATTLIST LoTentry Pagenum CDATA #IMPLIED>
-
-<!-- Title Page elements -->
-<!ELEMENT Author - - (Firstname+, Surname?)>
-
-<!ELEMENT Firstname - - (#PCDATA)>
-
-<!ELEMENT Surname - - (#PCDATA)>
-
-<!ELEMENT Date - - (#PCDATA)>
-
-<!ELEMENT Copyright - - (Year+, Holder*)>
-
-<!ELEMENT Year - - (#PCDATA)>
-
-<!ELEMENT Holder - - (#PCDATA)>
-
-<!ELEMENT ISBN - - (#PCDATA)>
-
-<!ELEMENT LegalNotice - - (Para+)>
-
-<!ELEMENT RevHistory - - (Revision*)>
-
-<!ELEMENT Revision - - (RevNumber, Date, AuthorInitials+, RevRemark)>
-
-<!ELEMENT RevNumber - - (#PCDATA)>
-
-<!ELEMENT AuthorInitials - - (#PCDATA)>
-
-<!ELEMENT RevRemark - - (#PCDATA)>
-
-<!ELEMENT TitleBook - - (Title, Subtitle?, TitleAbbrev?, ReleaseInfo?, BookAcronym?)>
-
-<!ELEMENT Subtitle - - (#PCDATA)>
-
-<!ELEMENT ReleaseInfo - - (#PCDATA)>
-
-<!ELEMENT BookAcronym - - (#PCDATA)>
-
-<!ELEMENT Editor - - (Firstname+, Surname?)>
-
-<!ELEMENT Edition - - (#PCDATA)>
-
-<!ELEMENT PrintHistory - - (Para+)>
-
-<!ELEMENT Publisher - - (#PCDATA)>
-
-<!ELEMENT Series - - (#PCDATA)>
-
-<!-- Contents for Tables of Contents -->
-<!ELEMENT ToCentry1 - - ((%inlinechar.gp;)+, ToCentry2*)>
- <!ATTLIST ToCentry1 Pagenum CDATA #IMPLIED>
-
-<!ELEMENT ToCentry2 - - ((%inlinechar.gp;)+, ToCentry3*)>
- <!ATTLIST ToCentry2 Pagenum CDATA #IMPLIED>
-
-<!ELEMENT ToCentry3 - - ((%inlinechar.gp;)+, ToCentry4*)>
- <!ATTLIST ToCentry3 Pagenum CDATA #IMPLIED>
-
-<!ELEMENT ToCentry4 - - ((%inlinechar.gp;)+, ToCentry5*)>
- <!ATTLIST ToCentry4 Pagenum CDATA #IMPLIED>
-
-<!ELEMENT ToCentry5 - - ((%inlinechar.gp;)+)>
- <!ATTLIST ToCentry5 Pagenum CDATA #IMPLIED>
-
-<!-- All the elements for reference entries -->
-<!ELEMENT RefEntry - - (Comment*, RefMeta, Comment*, RefNameDiv, RefSynopsis?, RefHead1+)>
- <!ATTLIST RefEntry id ID #IMPLIED>
-
-<!ELEMENT RefMeta - - (RefFileName, RefSection, RefMiscInfo*)>
- <!ATTLIST RefMeta id ID #IMPLIED>
-
-<!ELEMENT RefFileName - - (#PCDATA)>
-
-<!ELEMENT RefSection - - (#PCDATA)>
-
-<!ELEMENT RefMiscInfo - - (#PCDATA)>
-
-<!ELEMENT RefNameDiv - - ((%refnamediv.content.gp;)+)>
- <!ATTLIST RefNameDiv id ID #IMPLIED>
-
-<!ELEMENT RefDescriptor - - ((%refname.content.gp;)+)>
-
-<!ELEMENT RefName - - ((%refname.content.gp;)+)>
-
-<!ELEMENT RefPurpose - - ((%inlinechar.gp;)+)>
-
-<!ELEMENT RefSynopsis - - ((RefSynopsisblock, RefHead2*)|(RefHead2+))>
- <!ATTLIST RefSynopsis id ID #IMPLIED
- Name (Synopsis|Syntax) Synopsis >
-
-<!ELEMENT RefSynopsisblock - - ((%literalcontent.gp;)+)>
-
-<!ELEMENT RefHead1 - - (Title, (%refdivbody.gp;))>
- <!ATTLIST RefHead1 id ID #IMPLIED>
-
-<!ELEMENT RefHead2 - - (Title, (%component.gp;)+)>
- <!ATTLIST RefHead2 id ID #IMPLIED>
-
-
-]>
-
+++ /dev/null
-<DOCBOOK>
-<CHAPTER>
-<TITLE>DocBook DTD 1.2: The Elements Alphabetized</TITLE>
-<ITEMIZEDLIST>
-<LISTITEM><PARA>Abstract is a summary of a document's content. It
-contains Paras and may bear a Title. Abstract
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Acronym is a pseudoword made up of the initials or
-initial parts of a conventional series of words. For
-purposes of the DocBook DTD Acronym may also be a string
-of initials. Acronym contains plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Action is a function to be invoked in response to a user event.
-It contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Anchor marks a target for a Link, and may appear almost anywhere.
-Anchor has no content, and no end tag.
-Anchor has common and Pagenum attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Appendix may contain anything
-found in a Chapter.
-It may have a DocInfo and
-must have a Title and may have a TitleAbbrev.
-Appendix has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Application is the name of a software program that does something
-useful. Application may contain
-plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Author is part of DocInfo and consists of
-one or more optional Firstnames and an optional Surname element.
-Author also occurs in BiblioEntry. It has
-common attributes.
-<LITERALLAYOUT>
-<AUTHOR><FIRSTNAME>Marmaduke Anthony</FIRSTNAME>
-<SURNAME>Pickthall</SURNAME></AUTHOR>
-</LITERALLAYOUT>
-</PARA></LISTITEM>
-<LISTITEM><PARA>AuthorBlurb is a short description of a document's
-author. It
-contains Paras and may bear a Title. AuthorBlurb
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>AuthorInitials indicate the author of
-a Revision or Comment.
-AuthorInitials contains plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>BiblioEntry is an entry in a Bibliography. For
-flexibility, it may contain a TitleAbbrev, must
-contain at least one of Author, CorpAuthor,
-Editor, or Title, may
-have any or all of
-Subtitle, Date, and Publisher,
-and following all of that, plain text. BiblioEntry
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Bibliography may be a book
-component on its own, or it may appear within a Preface, Chapter,
-or Appendix. It may have a DocInfo,
-a Title and a TitleAbbrev, may have one or more introductory Paras,
-and contains BiblioEntries. No provision
-has been made for bibliographies that are divided into sections.
-Bibliography has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>BlockQuote is a quotation set off from the main text,
-rather than occurring in-line. It may be titled, and
-may contain anything found in a Sect except another
-Sect---that
-is, it may contain Paras, lists, and so forth. BlockQuote has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Book is <EMPHASIS>NOT THE SAME AS DOCBOOK.</EMPHASIS>
-A Book is loosely
-defined as having a required DocInfo, then an optional ToC,
-any number of LoTs, any number of Prefaces, one or more Chapters,
-the following: Appnedix, Bibliography, and
-then, in order, any number of References, Appendixes,
-Glossaries, Bibliographies, and Indexes.
-Book has common and Number
-attributes (you can supply the number of a Book through
-this attribute or as the content of the VolumeNumber
-element in DocInfo).
-</PARA></LISTITEM>
-<LISTITEM><PARA>BookAcronym is an optional part of BookTitle, part of
-DocInfo, and
-may be used alongside or in preference to TitleAbbrev.
-BookAcronym contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>BookTitle is part of DocInfo, and contains, in order,
-a mandatory Title and optional Subtitle, TitleAbbrev, ReleaseInfo,
-and Book Acronym. BookTitle may also appear as the first element
-of DocBook. BookTitle has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Button is a button in a graphical user interface. It
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Caution is an admonition set off from the text and supplied
-with a title, which is ``Caution'' unless another Title is
-supplied explicitly. The contents of a Caution
-may include Paras, lists, and so forth.
-Caution has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Chapter may contain anything except
-higher-level elements
-such as Part, Book, and Set. It may have a DocInfo,
-must have a Title, and may have a TitleAbbrev.
-Chapter has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Character is a character, that is, an element of a writing
-system. Characters may belong to Charsets, and in some contexts
-one may speak of fonts as representing characters. But <EMPHASIS>cf.</EMPHASIS>
-Glyph, Font.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Charset is a conventionally defined
-set of characters, (not a font). Charset
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Citation is any in-line bibliographic
-reference to another published work that uses a reference
-string, such as an abbreviation in a Bibliography.
-Citation may contain plain text only, and has
-common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CiteBook is the name of another book (or journal)
-cited in the text. CiteBook may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CiteChap is a reference to a specific chapter
-(or other component) of any
-book cited in the text, including the book in which
-the CiteChap appears. CiteChap may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CiteRefEntry is a reference to a RefEntry
-in any
-book cited in the text, including the book in which
-the CiteRefEntry
-appears. CiteRefEntry may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CiteSect is a reference to a specific section of another
-document cited in the text, including the document in which
-the CiteSect appears. CiteSect may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Classname is the name of the class to which a
-program component belongs.
-Classname contains plain text and has common
-and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Command is the name of an executable program, or
-the entry a user makes to execute a command.
-Command may contain
-plain text, FunctionParam, VarParam, Anchor, Optional,
-and Option,
-and has common and HasRefEntry
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Comment is a remark made within the document file that
-is intended for use during interim stages of production. A
-finished piece of computer documentation intended for an
-end user would have no visible Comments. Comment may
-appear almost anywhere, and may contain almost anything
-below the Section level;
-it has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ComputerOutput is data presented to the user by a
-computer. It may contain plain text and Anchors,
-and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Constant is a fixed value. Constant contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Copyright is part of DocInfo and consists of one or
-more Years and any number of Holders. Copyright has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CorpAuthor is the corporate author of a book, for use
-in DocInfo or BiblioEntry. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CorpName is the name of a corporation. It contains
-plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Date appears in DocInfo, BiblioEntry, and Revision, and
-contains plain text. It has common attributes. No provision
-has been made for representing eras; you could include this
-information along with the date data.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DbField is the name of a field in a database.
-DBField contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DbName is the name of a database or database file.
-DbName contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DbRecord is the name of a record in a database.
-DbRecord contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DbTable is the name of a database table. DbTable contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DocBook is the base document element for this DTD.
-It is only a wrapper and has no semantic value.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DocInfo is a book component, containing one or more of the
-following: Author, AuthorInitials, BookAcronym,
-BookTitle, Copyright, CorpAuthor, CorpName, Date,
-Editor, Edition, InvPartNumber, ISBN, LegalNotice,
-OrgName, PrintHistory, ProductName, ProductNumber,
-Publisher, PubsNumber, RevHistory, Series,
-and VolumeNumber. No order is enforced among these
-elements, but you are urged to begin with BookTitle and Author(s).
-DocInfo has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Edition is the edition of a document. It contains
-plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Editor is like Author, an element of DocInfo and
-BiblioEntry. It consists of
-one or more optional Firstnames and an optional Surname element.
-It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Emphasis is provided for use where one would traditionally employ italics
-(more rarely, bold) to emphasize a word or phrase. Emphasis
-may contain only plain text; it has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Epigraph is to be used for a brief section of poetry or prose
-at the start of a chapter. It contains Paras, and has and
-common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Equation is a mathematical equation set off on a line
-by itself, or occurring in-line. An Equation has an optional
-Title and TitleAbbrev, and contains a Graphic, <EMPHASIS>q.v.</EMPHASIS>
-Equation has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Error is an error reported by a computer. Error
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>EventStructure is the code that defines an Event.
-EventStructure contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>EventType is a classification of an event.
-EventType
-contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Example is intended for sections of program source code
-that are provided as examples in the text.
-A Example has an optional Title,
-optional TitleAbbrev, and one or more Screens, LiteralLayouts, or
-ProgramListings, in any combination. Example has common
-attributes and bears the
-``linespecific'' Notation attribute.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ExternalLink is like Link, <EMPHASIS>q.v.,</EMPHASIS> except that its
-Linkend and Endlink attributes are not defined as
-SGML IDREFs; this is so you can make reference to
-external documents without
-incurring parsing errors.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Figure is an illustration. A Figure must have a Title, and may have a
-TitleAbbrev; it may then contain
-one or more of the following:
-BlockQuote, Comment, Equation, Example,
-FigureFileRef, Graphic, IndexTerm,
-LiteralLayout, ProgramListing, Screen, Synopsis,
-and Table.
-It has an ID attribute, and also
-Height, Width, Align, and Float attributes. To
-reference an external file containing graphical
-content use the Graphic element.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Filename is the name of a file, including pathname if this
-information is present. Filename may contain
-plain text, FunctionParam, VarParam, and Anchor,
-and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Firstname is part of Author and Editor, <EMPHASIS>q.q.v.</EMPHASIS> It contains
-plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>FirstTerm is to be used for the first occurrence
-of a word in a given context, when
-the style of the document is such that these first occurrences are
-differentiated in some manner. A FirstTerm may contain
-plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Footnote is the text of a footnote.
-The point in the text where the mark for a specific
-footnote goes is indicated by FootnoteRef; the text of
-the Footnote may appear somewhere else in the file.
-A Footnote may contain all of the
-permissible contents of Paras.
-Footnote has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Font is a collection of Glyphs, <EMPHASIS>q.v.</EMPHASIS> Font
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>FootnoteRef indentifies the location for a footnote mark.
-It may contain plain text, which is the mark to be displayed,
-or it may be empty. It has ID, Linkend, and Mark
-attributes: the Linkend attribute has as its value the ID of
-the associated Footnote, and the Mark attribute provides
-another way of indicating the contents of the mark (such as an asterisk, *).
-</PARA></LISTITEM>
-<LISTITEM><PARA>ForeignPhrase is any word or words
-from a language other than
-that of the document which it is desired to mark off
-in some way. In English, <FOREIGNPHRASE>inter alia</FOREIGNPHRASE> and
-<FOREIGNPHRASE>c'est la vie</FOREIGNPHRASE> are ForeignPhrases.
-ForeignPhrase contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Function is a subroutine in a program or external
-library. Function may contain
-plain text, FunctionParam, VarParam, and Anchor, and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>FunctionParam identifies an argument for a Function.
-It may contain plain text, Subscript, and Superscript,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Glossary may occur within a Chapter, Appendix, or Preface,
-or may be a book component in its own right.
-It contains an optional DocInfo,
-optional Title and TitleAbbrev, may contain
-any number of Paras, and then consists of GlossaryEntries.
-No provision has been made for Glossaries divided into sections.
-Glossary has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>GlossaryDef is the definition attached to a GlossaryTerm
-in a GlossaryEntry, which occurs in a Glossary. It may
-contain in-line elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>GlossaryEntry is an entry in a Glossary, containing
-a GlossaryTerm and GlossaryDef. Please note that GlossaryEntry occurs
-in a Glossary, not in the text of (<EMPHASIS>e.g.</EMPHASIS>) a Chapter
-(although a Glossary may be included within a
-Chapter). GlossaryEntry
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>GlossaryTerm is an in-line element for tagging terms in the
-text of a Chapter (for example) that are glossed in a Glossary,
-and also for tagging those terms in GlossaryEntries, in the
-Glossary itself. As you may not want to tag all occurrences
-of these words outside of Glossaries, you might consider
-GlossaryTerm, when used outside of Glossaries, to be similar
-to FirstTerm, except that GlossaryTerm may contain other
-in-line
-elements. GlossaryTerm has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Glyph is a mark, a component of a font. A character
-or ligature might be made up of one, two, or more Glyphs.
-Glyph contains plain text and has common attributes.
-<EMPHASIS>Cf.</EMPHASIS> Character.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Graphic may occur within a Figure, Table, Screen,
-Paragraph, or Equation, to enclose graphical data or to
-point to an external file containing the contents of one of these
-elements. Graphic contains CDATA (data in which
-SGML entities and tags, other than the Graphic end tag, are not
-recognized by the SGML parser) and has format,
-Fileref, Entityref, and ID attributes.
-The format attribute may have the value of
-GIF, TIFF, CGM, DVI, EPS, TEX, TBL, EQN, DITROFF, or PS.
-If it is desired to point to an external file, a filename may
-be supplied as the value of the Fileref attribute, or an
-external entity may be supplied as the value of the
-Entityref attribute.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Hardware is any name for a physical part of a computer system. It
-may contain plain text, FunctionParam, VarParam, and Anchor,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Highlights is a list of main points that are discussed
-a book component such as a Chapter. It may contain
-Paras and lists, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Holder is part of Copyright and is the name of the
-holder of the copyright of the document. It may contain
-plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Honorific is a person's title, to be used as part of Author
-or Editor. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>HWapplic describes the hardware to which
-given context (such as a RefEntry) is relevant. RefClass is
-a good place to put HWapplic information. HWapplic
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Icon is the name of an icon or image
-presented on a computer screen.
-Icon contains plaint text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Important
-is an admonition set off from the text and supplied
-with a title, which is ``Important'' unless another Title is
-supplied explicitly. The contents of an Important
-may include Paras, lists, and so forth.
-Important has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Index may occur within a Chapter, Appendix, or
-Preface, or may be a book
-component on its own.
-It contains an optional DocInfo, Title, and TitleAbbrev, may contain
-any number of Paras, and then consists of IndexEntries.
-No provision has been made for Indices divided into sections. Index has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>IndexAs may be nested within the IndexTerm components
-Primary, Secondary, and Tertiary to indicate an
-alternate string by which the indexed term (the other
-content of Primary, Secondary, or Tertiary) should be
-indexed in the Index. You might want to use this element
-if you tag IndexTerms in the body of the text, rather
-than as separate elements. IndexAs contains in-line
-elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>IndexEntry is a part of Index, and contains a
-PrimaryIE, which may be accompanied by SecondaryIE,
-TertiaryIE, SeeIE, and SeeAlsoIE. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>IndexTerm is a word or phrase to be indexed.
-IndexTerm appears in the text, not in the Index; you
-can apply IndexTerm
-to words in the flow of text or include
-IndexTerms as separate elements.
-Primary, Secondary, and Tertiary
-index items are nested within this tag, as are See and
-SeeAlso items. IndexTerm has common, Span, and PageNum
- attributes.
-The Span attribute, which may have the value
-Start or End, may be used for showing a span
-of text to be indexed.
-The PageNum attribute may be used to
-indicate the page on which the indexed term is found in print.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Interface is the name of any part of a graphical user
-interface,
-such as a button, icon, menu, menu selection, or window; a more
-specific element may be used instead. Interface
-plain text, FunctionParam, VarParam, and
-Anchor, and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>InterfaceDefinition is a specification for a graphical user
-interface. It contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>InvPartNumber is an inventory part number, which
-may occur in DocInfo. It contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ISBN is part of DocInfo, and should be used for the International
-Standard Book Number of the document if it has one. (You could use
-it for an ISSN, also.) ISBN contains plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ItemizedList is a list in which each item is marked with
-a bullet, dash, or other dingbat (or no mark at all). It
-consists of one or more ListItems. A ListItem in an
-ItemizedList contains Paras and other objects, which
-may in turn contain other lists; an ItemizedList may be
-nested within other lists, too. ItemizedList
-has common attributes and
-a Mark attribute. Your application might supply the mark to be used
-for an ItemizedList, but you can use this attribute to
-indicate the mark you desire to be used (such as
-•); for no mark at all, use the attribute but give it
-no value.
-ItemizedList may be nested within Task, so as to provide a
-Title and introductory matter.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Keycap is the text printed on a physical key on a
-computer keyboard, not necessarily the same thing as a
-Keycode. Keycap contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Keycode is the computer's numeric designation of a key on
-a computer keyboard. Keycode contains plain text and has common and HasRefEntry
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Keysym is a key symbol name, which is not necessarily the same thing
-as a Keycap. The Keysym for the H key (Keycap H) is h, for
-example. Keysym contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LegalNotice is part of DocInfo, for
-acknowledgement of trademarks and so forth. It consists of
-Paras and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LineAnnotation is a writer's or editor's comment on
-a line of program code within an Example, ProgramListing,
-or Screen. The code's own comments are not
-LineAnnotations. LineAnnotation contains plain text
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Link is a hypertext link. It may contain in-line elements
-and has Endterm, Linkend, and Type attributes. The required
-Linkend attribute specifies the target of the link,
-and the optional Endterm attribute specifies
-text that is to be fetched from elsewhere in the document
-to appear in the Link. You can also supply this text directly as
-the content of the Link.
-The use of the optional Type attribute is undefined, allowing
-you to create local link types.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ListItem is a wrapper for the elements of
-item in an ItemizedList or OrderedList; it also
-occurs within VarListEntry in VariableList.
-It may contain just about anything except Sects and book
-components.
-ListItem has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Literal is any literal string, used in-line, that is part of
-data in a computer. This may be as precise as
-the value of an argument, but Literal may also be used
-as a catch-all element. Literal may contain plain text
-and Anchor; it is not meant as a wrapper for in-line
-elements. Literal
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LiteralLayout is the wrapper for lines set off from
-the main text that are not tagged as Screens, Examples,
-or ProgramListing, in which line breaks and leading
-white space are to be regarded as significant.
-LiteralLayout
-contains in-line elements; it has common attributes
-and the ``linespecific'' Notation attribute.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LoT is the generic tag for such things as a List
-of Figures or List of Tables. An LoT may occur within a Chapter,
-or Appendix, or may be a book
-component on its own.
-It contains an optional DocInfo, Title, and TitleAbbrev,
-followed by multiple LoTentries. LoT has
-common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LoTentry is an element of LoT, and contains
-the text of the thing to be listed,
-including, if desired, in-line elements. LoTentry has
-common and PageNum attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Macro is the name of a computer macro. It contains plain
-text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ManVolNum, which is specific to UNIX man pages,
- designates the section of a complete set of
-reference pages that a reference page belongs to. It appears
-within RefMeta, contains plain text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Mask specifies which values in a specified structure should
-be read when updating resource values. Mask contains plain text
-and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Menu is part of a graphical user interface, containing
-choices of actions for the user. Menu contains
-plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>MenuItem is a choice in a menu. MenuItem contains
-plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Note is a message to the user, set off from the text and supplied
-with a title, which is ``Note'' unless another Title is
-supplied explicitly. The contents of a Note
-may include Paras, lists, and so forth.
-Note has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Option is a option to a Command (in the Command ``ls -l''
-``-l'' is an Option), but is not nested within Command. It may
-contain plain text, FunctionParam, VarParam, and Anchor, and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Optional is for use in Synopsis, as in a
-RefEntry, where optional parameters
-conventionally are shown in square
-brackets. Optional should replace those brackets; it may contain
-any element listed in the parameter
-entity computerterms.gp, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>OrderedList is a numbered or lettered list, consisting of
-ListItems. A ListItem in an
-OrderedList contains Paras and other objects, which
-may in turn contain other lists; an OrderedList may be
-nested within
-other lists, too.
-OrderedList has common attributes, along with
-a Numeration attribute, which
-may have the value Arabic, Upperalpha, Loweralpha,
-Upperroman, or Lowerroman. The default is Arabic.
- OrderedList
-also has an InheritNum attribute, specifying that for a
-nested list the numbering of ListItems should include the
-number of the item within which they are nested (2a, 2b, etc.,
-rather than a, b, etc.). Orderedlist also has
-a Continuation attribute, with values Yes or No,
-which may be used to
-indicate whether the numbering of a list begins afresh (No)
-or continues that of the immediately preceding list (Yes). The
-default is No, so you need supply the Continuation attribute only
-if your list continues the numbering of the preceding list.
-</PARA></LISTITEM>
-<LISTITEM><PARA>OrgName is the name of an organization that is not
-a corporation (<EMPHASIS>cf.</EMPHASIS> CorpName), for use in DocInfo.
-It contains plain text
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>OSname is the name of an operating system.
-It contains plain text
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>OtherName is provided as an alternative to Firstname
-and Surname in Author and Editor. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Para is a paragraph. It may have a Title, by means of which
-authors may evade the Sect hierarchy, as with a ``bridgehead.''
-Para may contain any in-line element, any list, Graphic, Equation,
-Synopsis, Table, BlockQuote, ProgramListing, LiteralLayout,
-Screen, and Figure. Abstract, AuthorBlurb, Caution, Important, Note, and
-Warning are excluded, as are Sects and higher-level elements.
-Para has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Part may be used to compose a Book. It
-contains a Title, an optional TitleAbbrev, an optional PartIntro,
-followed by two or more Chapters or Appendices.
-Part has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>PartIntro is a part of Part, and may also appear in
-Reference. In Part, it should introduce the
-contents of the Part. It may contain just about anything except
-Sects. PartIntro has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Preface is a book component, just like a Chapter,
-<EMPHASIS>q.v.</EMPHASIS> Use the Title element to provide the word ``Preface''
-or other string as desired. Preface has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Primary is a word or phrase occurring in
-the text that is to
-appear in the index under as a primary entry. It must be
-nested within IndexTerm tags. Primary may contain in-line elements and IndexAs, <EMPHASIS>q.v.</EMPHASIS> Primary. Primary has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>PrimaryIE is a primary entry in an Index, not in the
-text. It may contain only plain text, and has common
-attributes and a Linkends attribute, which has the
-value of some list of element IDs.
-</PARA></LISTITEM>
-<LISTITEM><PARA>PrintHistory is part of DocInfo, <EMPHASIS>q.v.</EMPHASIS> It contains Paras
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ProductName is a formal name for any product, part
-of DocInfo. It contains plain text and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ProductNumber is a number assigned to a product,
-part of DocInfo. It contains plain text and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ProgramListing contains a listing of a program, including
-LineAnnotations.
-Line breaks and leading
-white space are significant in a ProgramListing. Programlisting
-may contain in-line elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Prompt is a prompt appearing on a computer screen,
-such as the percent sign (%),
-including any other text appearing there (marmaduke%).
-Prompt may contain only plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Property is the name of a defined set of data
-associated with a window. Property may contain
-in-line elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ProtocolRequest is a message sent from a program to the
-server. ProtocolRequest contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>PubsNumber is a number assigned to a publication
-other than ISBN, for use
-in DocInfo. <EMPHASIS>Cf.</EMPHASIS> also InvPartNumber. PubsNumber
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Publisher is an element of DocInfo and BiblioEntry. It may contain
-plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Quote is supplied for in-line quotations. For block quotes
-use BlockQuote. Quote may contain in-line elements and has
-common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefClass is an element of RefNameDiv, in which the
-applicability or scope of the topic of a RefEntry may be
-indicated (such as the element SWapplic or
-a string such as ``LocalBlocking''). It may contain
-in-line elements and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefDescriptor is a substitute for RefName to be used when a
-RefEntry covers more than one topic and none of the topic name
-is to be used as the sort name. RefDescriptor contains plain
-text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefEntry is a reference page. RefEntry
-has common attributes. For more on RefEntries see
-version 1.0 of the <CITEBOOK>Guide to the DocBook DTD.</CITEBOOK>
-</PARA></LISTITEM>
-<LISTITEM><PARA>Reference is a collection of RefEntries. It may
-be a book
-component on its own,
-or it may appear within a Preface, Chapter, or Appendix.
-Reference has an optional DocInfo,
-a required Title,
-an optional TitleAbbrev, an optional PartIntro, and
-one or more RefEntries.
-Reference has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefFileName is the primary name given to the reference page for
-sorting and indexing. It may be the same as the first of
-the RefNames, or it may be the same as the
-RefDescriptor.
-RefFileName may contain only plain text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefMeta is the first major division of a reference page,
-in which metainformation about the reference page is supplied.
-RefMeta is optional, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefMiscInfo marks information in RefMeta that may be
-supplied by vendors, such as copyright, release date, revision
-date, print status, operating system, hardware architecture,
-or a descriptive phrase for use in a print header. It
-may contain only plain text, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefName is the name of the subject or subjects of a
-reference page, and appears within RefNameDiv. It
-may contain plain text and in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefNameDiv is the second major division of a reference page,
-in which the name (RefName) or names of the subject or subjects of the
-reference page are given, along with a RefPurpose.
-RefNameDiv has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefPurpose is a short phrase describing the subject of
-the reference page. It follows the RefNames in
-the RefNameDiv division. It may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefSect1 is equivalent to a Sect1 in the DocBook DTD.
-It contains a Title, followed by any of the allowable contents
-of a Sect, except that only one level of subsection
-is allowed, called RefSect2. RefSect1 has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefSect2 is equivalent to a Sect2 in the DocBook DTD, and may
-occur within RefSect1 or RefSynopsisDiv. It may contain any of the
-allowable contents of a Sect, except that no further subsections
-are allowed. RefSect2 has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefSynopsisDiv is the third major division of a reference page,
-in which the syntax of the subject of the reference page is
-indicated. It contains a Synopsis, and may have
-subdivisions, which must be RefSect2s, not RefSect1s (that is,
-RefSynopsisDiv counts as a RefSect1).
-RefSynopsisDiv has common attributes and a Name
-attribute, which may be either Synopsis or Syntax;
-the default is Synopsis.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ReleaseInfo is an element of DocInfo, in which
-information about a particular version of a document may
-occur. It may contain only plain text, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Resource is a configurable setting available to a program
-that controls its behavior or appearance.
-Resource
-may contain plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ReturnValue is a value returned by a function.
-ReturnValue may contain plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RevHistory is a section of DocInfo
-consisting of Revisions. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Revision is an entry in RevHistory, describing some
-revision made to the text. A Revision has a mandatory
-Revisionnumber and Date, one or more sets of AuthorInitials, and a
-Revisionremark. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RevNumber is an element of Revision, <EMPHASIS>q.v.</EMPHASIS>
-It may contain only plain text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RevRemark is an element
-of Revision, describing the Revision.
-It may contain only plain text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Screen is intended to represent what the user sees or
-might see on a computer screen.
-A Screen may
-consist of in-line elements (in which line breaks
-and leading white space are considered
-significant) or a ScreenInfo and a Graphic. Screen has common attributes and the Notation attribute
-``linespecific.''
-</PARA></LISTITEM>
-<LISTITEM><PARA>ScreenInfo is a part of Screen, <EMPHASIS>q.v.</EMPHASIS> A ScreenInfo
-indicates how the Graphic with which it is paired was created
-as a guide for future revisions. It may contain only plain
-text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Secondary is a word or phrase in the text that is to
-appear in the index beneath a Primary entry. It must be
-nested within IndexTerm tags and must follow a Primary element.
-Secondary may contain in-line elements
-and IndexAs, and has common and
-HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SecondaryIE is part of IndexEntry, like PrimaryIE, <EMPHASIS>q.v.</EMPHASIS>
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect1 marks a section of a document that
-begins with a first-level heading. Anything may occur
-within a Sect1 except a DocInfo, Preface,
-Chapter, Appendix, or
-another Sect1, including a Glossary, Bibliography, RefEntry, Reference, Toc, Index,
-or LoT. Sect1 must have a Title, which is the text
-of the heading itself, it may have a TitleAbbrev, and must
-include some content other than in-line elements and
-plain text; these must occur in Paras or other
-objects. Sect1--5 have common
-and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect2 is a section beginning with a second-level
-heading, and must be nested within a Sect1.
-Allowable and required content
-for Sect2s are like those for Sect1s.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect3. <EMPHASIS>Cf.</EMPHASIS> Sect2.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect4. <EMPHASIS>Cf.</EMPHASIS> Sect2.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect5. <EMPHASIS>Cf.</EMPHASIS> Sect2. No further subdivisions are
-supplied in the DocBook DTD.
-</PARA></LISTITEM>
-<LISTITEM><PARA>See is part of IndexTerm, indicating, for
-a word or phrase in the text, the index entry to
-which the reader is to be directed when he consults
-the stub index entry for another element within
-the IndexTerm.
-See must be nested within IndexTerm tags and must
-follow a Primary or Secondary element.
-See may contain in-line
-elements and has common and HasRefEntry attributes..
-</PARA></LISTITEM>
-<LISTITEM><PARA>SeeAlso is like See, but indicates
-the index entries to which the reader is <EMPHASIS>also</EMPHASIS>
-to be directed when he consults a full index entry.
-SeeAlso must be nested within IndexTerm tags and must
-follow a Primary or Secondary element.
-SeeAlso may contain in-line
-elements and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SeeAlsoIE is a ``see also'' entry in an Index, not in the
-text, occurring
-unnested within IndexEntry at the PrimaryIE or
-SecondaryIE level.
-It may contain plain text only, and has common
-attributes and a Linkends attribute, which has the
-value of some list of IndexEntry IDs.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SeeIE is a ``see'' entry in an Index, not in the
-text, occurring
-unnested within IndexEntry at the PrimaryIE or
-SecondaryIE level.
-It may contain plain text only, and has common
-attributes and a Linkend attribute, which has the
-value of some IndexEntry ID.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Seg is a component of a SegmentedList. Segs are the only
-content of a SegmentedList's
-SegListItems. They may contain in-line
-elements. Seg has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SegListItem is a list item in a SegmentedList. It consists
-of two or more Segs, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SegmentedList is a list of sets of units without additional text
-(and is thus different from the VarListItem,
-composed of Terms and ListItem,
-in a VariableList). A SegmentedList may be used to represent
-sets of information often presented as simple tables. A SegmentedList
-may have a Title and TitleAbbrev, followed by any number
-of SegTitles, and two or more SegListItems. SegmentedList
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SegTitle is a title that pertains to one Seg in each
-SegListItem: the first SegTitle to the first Seg, the second SegTitle
-to the second Seg, and so on. SegTitles may contain in-line elements,
-and are grouped at the beginning of a SegmentedList, before the SegListItems.
-SegTitle has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Series is part of DocInfo and names the publication series of
-which the book is a part. Series may contain only plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Set is a set of Books. It has an optional DocInfo and
-must contain two or more Books. Set has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sidebar is a segment of text isolated from the narrative flow
-of the main text, typically boxed. A Sidebar may have
-a Title and a TitleAbbrev, and must have text formatted in
-some fashion: allowable contents
-include Paras, lists, Figures, and
-Tables. No Sects allowed. Sidebar has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>StructField is a field in a Structure. It may
-contain plain text only, and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>StructName is the name of a Structure. It may
-contain plain text only, and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Subscript tags subscripts. It may contain plain text
-and another
-Subscript, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Subtitle is for use in BookTitle. It contains plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Superscript tags superscripts.
-It may contain plain text and another Superscript,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Surname is an element of Author in DocInfo, supplied so
-that a group of documents may be indexed
-by their authors's surnames. It may contain
-plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SWapplic specifies the applicability of information
-given a software context.
-RefClass is a good place to put SWapplic information.
-SWapplic contains plain text only and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Symbol is a name that is replaced by a value before processing.
-Symbol contains plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Synopsis marks the line or lines that provide the
-syntax of a command or function. It appears
-within RefSynopsisDiv, and may occur elsewhere in
-a document, too.
-Synopsis may contain in-line elements; within it,
-line breaks and white space are significant. It
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SystemItem may be used for any
-system-related item, as a catch-all.
-It may contain plain text, FunctionParam, VarParam,
-Anchor, and Optional,
-and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SystemName is the name of any system. It may
-contain plain text only, and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Table is an array of text. A Table may have
-a Title, TitleAbbrev, and Graphic; following those
-elements
-it may have a TableSpec (containing such things as troff
-formatting information), any
-number of TableColHeads (containing headings
-for the columns of the Table), and one or more TableRows of
-TableCells. Table has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TableCell is a part of a TableRow in a Table. It may contain
-in-line elements and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TableColHead is an optional part of Table, containing
-headings for the columns of the Table as TableCells.
-It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TableRow is part of Table. A Table has TableRows of TableCells.
-It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TableSpec tags formatting information for a Table; it is
-not the text of a Table's heading. It may contain
-in-line elements and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Task is any set of Paras and lists that
-instructs the reader how to perform a given task. Task
-may have a Title and TitleAbbrev, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Term is the hanging term attached to a ListItem within
-a VarListEntry in a
-VariableList; visually, a VariableList
-is a set of Terms with attached items such as paragraphs. Each
-ListItem may be associated with a set of Terms. Term may contain
-in-line elements or Synopsis, and has
-common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Tertiary is a word or phrase that is to
-appear in the index under a Secondary entry. It must be
-nested within IndexTerm tags and must follow a Secondary element.
-Tertiary may contain in-line elements, and has
-common and
-HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TertiaryIE is part of IndexEntry, like PrimaryIE, <EMPHASIS>q.v.</EMPHASIS>
-</PARA></LISTITEM>
-<LISTITEM><PARA>Tip is a suggestion to the user, set off from the text and supplied
-with a title, which is ``Tip'' unless another Title is
-supplied explicitly. The contents of a Tip
-may include Paras, lists, and so forth.
-Tip has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Title is a string of characters, the text of a heading
-or element title. It is NOT the title of a Book: that is
-BookTitle. Title may contain
-in-line elements, and has common and PageNum attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TitleAbbrev is an optional element of
-anything titled. You may want to employ this element when a
-title is so long that you fear it will be truncated in
-some element of an online display, such as a title bar.
-TitleAbbrev may contain
-in-line elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ToC is a Table of Contents, which may be
-a book component on its own or may
-occur within other book components. It may
-have a DocInfo, Title, and TitleAbbrev,
-and contains ToCentry1s. ToC has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ToCentry1 is the top-level tag for items in a ToC. In
-the manner of
-Sect1, it may contain subsidiary groups (<EMPHASIS>e.g.,</EMPHASIS> for headings and
-subheadings within a chapter), named ToCentry2--5. ToCentry1--5s
-have common attributes and
-a PageNum attribute, for indicating the page numbers on which
-the ToCentries appear in a print book. ToCentry1--5 may contain
-in-line elements.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Token is a unit of information in the context of lexical analysis.
- Token contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Type indicates the classification of a value.
- Type contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>UserInput is an in-line element used to tag data entered by the user.
-You might use this element most frequently in LiteralLayouts and
-Screens. UserInput may contain in-line elements, and has
-common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>VariableList is a list of VarListEntries, which are
-composed of sets of one or more Terms with associated
-ListItems, which contain Paras. Inclusions
-are as for OrderedList, <EMPHASIS>q.v.</EMPHASIS> VariableList has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>VarListEntry is a component of VariableList, <EMPHASIS>q.v.</EMPHASIS>
-</PARA></LISTITEM>
-<LISTITEM><PARA>VarParam tags any character string that is to be
-replaced by a real name or value by the user. In
-``cat filename,'' filename is a VarParam. If a
-VarParam is also, say, a Command, nest the VarParam
-tags within the Command tags: VarParam may contain only
-plain text, Superscript, and Subscript,
-not in-line elements. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>VolumeNumber is the number of a Book in
-relation to a set or Set. It contains plain text
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Warning is an admonition set off from the text and supplied
-with a title, which is ``Warning'' unless another Title is
-supplied explicitly. The contents of a Warning
-may include Paras, lists, and so forth.
-Warning has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>WordAsWord is supplied for use when a word (or letter or
-number) is used not to represent the thing or idea it usually
-represents, but merely as the word itself. For example,
-``The term <WORDASWORD>Gothic</WORDASWORD> means different
-things to art historians and typographers,'' or for a single character,
-``the
-letter <WORDASWORD>X</WORDASWORD>''. WordAsWord may
-contain only plain text, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>XRef is a cross reference link to another part of the document,
-such as a Table, Figure, or Example. An XRef
-may contain text or be empty; it has an Endterm attribute, the value of which
-may be set to the ID of the text to appear in the cross reference if no
-content is supplied.
-An XRef that has both content and an Endterm attribute is faulty.
-XRef also has a Linkend attribute, the value of which is the ID of the
-target of the XRef.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Year is part of DocInfo and BiblioEntry (year of publication of the
-book). Year may contain only plain text, and has common attributes.
-</PARA></LISTITEM>
-</ITEMIZEDLIST>
-</CHAPTER>
-</DOCBOOK>
+++ /dev/null
-<!-- DocBook DTD Release 1.2.1
-
- 13 March 1993 1:00 PST
-
- Copyright 1992, 1993 HaL Computer Systems, Inc., and
- O'Reilly & Associates, Inc.
-
- Permission to use, copy, modify and distribute the DocBook DTD and
- its accompanying documentation for any purpose and without fee is
- hereby granted, provided that this copyright notice appears in all
- copies. If you modify the DocBook DTD, rename your modified
- version. HaL Computer Systems and O'Reilly & Associates make no
- representation about the suitability of the DTD for any purpose.
- It is provided "as is" without expressed or implied warranty.
-
- The DocBook DTD is maintained by O'Reilly & Associates. Please
- direct all questions, bug reports, or suggestions for changes to
- docbook@ora.com or by mail to: Terry Allen, O'Reilly & Associates,
- Inc., 103A Morris Street, Sebastopol, California, 95472.
-
- Please note that an SGML declaration is provided for this DTD.
-
- Public Identifier:
- "-//HaL and O'Reilly//DTD DocBook 1.2.1//EN"
- -->
-
-<!-- ==================================================================
- NOTATIONS -->
-
-<!NOTATION GIF SYSTEM "GIF" >
-<!NOTATION TIFF SYSTEM "TIFF" >
-<!NOTATION CGM SYSTEM "CGM" >
-<!NOTATION DVI SYSTEM "DVI" >
-<!NOTATION EPS SYSTEM "EPS" >
-<!NOTATION TEX SYSTEM "TEX 3.14" >
-<!NOTATION TBL SYSTEM "TBL" >
-<!NOTATION EQN SYSTEM "EQN" >
-<!NOTATION PS SYSTEM "PS" >
-<!NOTATION DITROFF SYSTEM "DITROFF" >
-<!NOTATION PIC SYSTEM "-//AT&T//NOTATION PIC-1//EN" >
-<!NOTATION linespecific SYSTEM "line ends and leading white space
- must be preserved in output" >
-
-<!-- ==================================================================
- PUBLICLY DECLARED EXTERNAL ENTITIES -->
-
-<!-- Uncomment the ENTITY declaration for your application. -->
-
-<!--
-<!ENTITY % ISOamsa PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Arrow Relations//EN">
- %ISOamsa;
- -->
-<!--
-<!ENTITY % ISOamsa SYSTEM "iso-amsa.gml">
- %ISOamsa;
- -->
-
-<!--
-<!ENTITY % ISOamsb PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Binary Operators//EN">
- %ISOamsb;
- -->
-<!--
-<!ENTITY % ISOamsb SYSTEM "iso-amsb.gml">
- %ISOamsb;
- -->
-
-<!--
-<!ENTITY % ISOamsc PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Delimiters//EN">
- %ISOamsc;
- -->
-<!--
-<!ENTITY % ISOamsc SYSTEM "iso-amsc.gml">
- %ISOamsc;
- -->
-
-<!--
-<!ENTITY % ISOamsn PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Negated Relations//EN">
- %ISOamsn;
- -->
-<!--
-<!ENTITY % ISOamsn SYSTEM "iso-amsn.gml">
- %ISOamsn;
- -->
-
-<!--
-<!ENTITY % ISOamso PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Ordinary//EN">
- %ISOamso;
- -->
-<!--
-<!ENTITY % ISOamso SYSTEM "iso-amso.gml">
- %ISOamso;
- -->
-
-<!--
-<!ENTITY % ISOamsr PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Relations//EN">
- %ISOamsr;
- -->
-<!--
-<!ENTITY % ISOamsr SYSTEM "iso-amsr.gml">
- %ISOamsr;
- -->
-
-<!--
-<!ENTITY % ISObox PUBLIC "ISO 8879:1986//ENTITIES Box and Line Drawing//EN">
- %ISObox;
- -->
-<!--
-<!ENTITY % ISObox SYSTEM "iso-box.gml">
- %ISObox;
- -->
-
-<!--
-<!ENTITY % ISOcyr1 PUBLIC "ISO 8879:1986//ENTITIES Russian Cyrillic//EN">
- %ISOcyr1;
- -->
-<!--
-<!ENTITY % ISOcyr1 SYSTEM "iso-cyr1.gml">
- %ISOcyr1;
- -->
-
-<!--
-<!ENTITY % ISOcyr2 PUBLIC "ISO 8879:1986//ENTITIES Non-Russian Cyrillic//EN">
- %ISOcyr2;
- -->
-<!--
-<!ENTITY % ISOcyr2 SYSTEM "iso-cyr2.gml">
- %ISOcyr2;
- -->
-
-<!--
-<!ENTITY % ISOdia PUBLIC "ISO 8879:1986//ENTITIES Diacritical Marks//EN">
- %ISOdia;
- -->
-<!--
-<!ENTITY % ISOdia SYSTEM "iso-dia.gml">
- %ISOdia;
- -->
-
-<!--
-<!ENTITY % ISOgrk1 PUBLIC "ISO 8879:1986//ENTITIES Greek Letters//EN">
- %ISOgrk1;
- -->
-<!--
-<!ENTITY % ISOgrk1 SYSTEM "iso-grk1.gml">
- %ISOgrk1;
- -->
-
-<!--
-<!ENTITY % ISOgrk2 PUBLIC "ISO 8879:1986//ENTITIES Monotoniko Greek//EN">
- %ISOgrk2;
- -->
-<!--
-<!ENTITY % ISOgrk2 SYSTEM "iso-grk2.gml">
- %ISOgrk2;
- -->
-
-<!--
-<!ENTITY % ISOgrk3 PUBLIC "ISO 8879:1986//ENTITIES Greek Symbols//EN">
- %ISOgrk3;
- -->
-<!--
-<!ENTITY % ISOgrk3 SYSTEM "iso-grk3.gml">
- %ISOgrk3;
- -->
-
-<!--
-<!ENTITY % ISOlat1 PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN">
- %ISOlat1;
- -->
-<!--
-<!ENTITY % ISOlat1 SYSTEM "iso-lat1.gml">
- %ISOlat1;
- -->
-
-<!--
-<!ENTITY % ISOlat2 PUBLIC "ISO 8879:1986//ENTITIES Added Latin 2//EN">
- %ISOlat2;
- -->
-<!--
-<!ENTITY % ISOlat2 SYSTEM "iso-lat2.gml">
- %ISOlat2;
- -->
-
-<!--
-<!ENTITY % ISOnum PUBLIC "ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN">
- %ISOnum;
- -->
-<!--
-<!ENTITY % ISOnum SYSTEM "iso-num.gml">
- %ISOnum;
- -->
-
-<!--
-<!ENTITY % ISOpub PUBLIC "ISO 8879:1986//ENTITIES Publishing//EN">
- %ISOpub;
- -->
-<!--
-<!ENTITY % ISOpub SYSTEM "iso-pub.gml">
- %ISOpub;
- -->
-
-<!--
-<!ENTITY % ISOtech PUBLIC "ISO 8879:1986//ENTITIES General Technical//EN">
- %ISOtech;
- -->
-<!--
-<!ENTITY % ISOtech SYSTEM "iso-tech.gml">
- %ISOtech;
- -->
-
-
-<!-- ==================================================================
- PARAMETER ENTITIES to allow inclusion of local modifications.
- To include your local terms, table content model, graphics
- format, or other local item,
-
- 1. At the head of your instance, after the DOCTYPE line,
- include a reference to an external entity file that
- that includes all the local terms, table content models,
- and (or) graphics formats you are using:
-
- <!DOCTYPE docbook SYSTEM "/yourpath/docbook.dtd" [
- <!ENTITY % localmods SYSTEM "/yourpath/localmodfile" >
- %localmods
- ]>
-
- You may need to set up attributes for your local elements.
-
- N.B.: Depending on the flags you set, your parser may report
- as errors that it has found duplicate specifications of
- these parameter entities. This is harmless, as the
- duplicates are those included below, which are unneeded.
-
- 2. In the referenced external entity file, redefine
- the parameter entities for your local modifications.
- Be sure to include the elements currently defined as
- the content of the following entities if you need
- to use them alongside your local modifications.
- -->
-
-<!ENTITY % local.refnav "RefEntry" >
-<!ENTITY % local.terms "Optional" >
-<!ENTITY % local.tables "Table" >
-<!ENTITY % local.notations "TEX" >
-<!ENTITY % local.refclasses "RefClass" >
-<!ENTITY % local.links "Link" >
-<!ENTITY % local.lists "SegmentedList" >
-
-<!-- =====================================================================
- ATTRIBUTE LIST for a set of common attributes. Remap can be
- used to indicate the value of the element in the original
- source. -->
-
-<!ENTITY % commonatts
- "id ID #IMPLIED
- Remap CDATA #IMPLIED">
-
-<!-- ===================================================================
- OTHER PARAMETER ENTITIES -->
-
-<!-- Book Contents: these are pieces it may be convenient to validate
- on their own -->
-
-<!ENTITY % bookcontent.gp "Appendix | Bibliography
- | Chapter | DocInfo | Glossary
- | Index | LoT | Part | Preface
- | RefEntry | Reference | ToC" >
-
-<!-- Contents that can appear almost anywhere -->
-
-<!ENTITY % links.gp "ExternalLink | FootnoteRef
- | %local.links; | XRef" >
-
-<!ENTITY % basechar.gp "%links.gp; | #PCDATA | FunctionParam
- | IndexTerm | VarParam | Anchor" >
-
-<!-- entities to make up inlinechar.gp -->
-
-<!ENTITY % words.gp "Acronym | Character | Charset | Citation
- | CiteBook | CiteChap
- | CiteRefEntry | CiteSect | Comment
- | Emphasis | FirstTerm
- | Font | ForeignPhrase
- | GlossaryDef | GlossaryTerm | Glyph
- | Quote | Subscript | Superscript
- | Trademark | WordAsWord" >
- <!ATTLIST (%words.gp;) %commonatts; >
-
-<!ENTITY % docinfo.content.gp "Author | AuthorInitials
- | BookTitle
- | Copyright | CorpAuthor | CorpName | Date
- | Editor | Edition
- | InvPartNumber | ISBN
- | LegalNotice | OrgName | PrintHistory
- | ProductName | ProductNumber
- | Publisher | PubsNumber | ReleaseInfo
- | RevHistory | Series
- | Subtitle | VolumeNumber" >
- <!ATTLIST (%docinfo.content.gp;) %commonatts; >
-
-<!ENTITY % computerterms.gp "Action | Application | Button
- | Classname | Command
- | ComputerOutput | Constant
- | DbName | DbTable | DbField | DbRecord
- | Error | EventType | EventStructure
- | Filename | Option | Function
- | Hardware | HWapplic | Icon
- | Interface | InterfaceDefinition
- | KeyCap | KeyCode | KeySym
- | LineAnnotation | Literal
- | Macro | Mask | Menu | MenuItem
- | Prompt | Property | OSname
- | ProtocolRequest
- | Resource | ReturnValue
- | StructField | StructName
- | SWapplic | Symbol
- | SystemItem | SystemName
- | Token | Type | UserInput" >
- <!ATTLIST (%computerterms.gp;) %commonatts;
- HasRefEntry (Yes|No) No >
-
-
-<!ENTITY % inlinechar.gp "%basechar.gp; | %computerterms.gp;
- | %docinfo.content.gp;
- | %local.terms; | %words.gp;" >
-
-<!ENTITY % paracontent.gp "%inlinechar.gp; | Graphic | Equation
- | Synopsis" >
-
-<!-- All the varieties of lists -->
-
-<!ENTITY % list.gp "ItemizedList | OrderedList | %local.lists;
- | VariableList | SimpleList" >
-
-<!-- More elements for other parameter entities -->
-
-<!ENTITY % object.gp "BlockQuote | Caution | Equation
- | Example | Footnote | Graphic
- | Important | LiteralLayout
- | %local.tables; | Note | ProgramListing
- | Screen | Synopsis | Task
- | Tip | Warning" >
-
-<!ENTITY % component.gp "Abstract | Anchor | AuthorBlurb | BiblioEntry
- | Epigraph | Figure | Highlights
- | IndexTerm | %links.gp;
- | %list.gp; | %object.gp;
- | Para | Sidebar " >
-
-<!ENTITY % refnav.gp "%local.refnav; | Toc | LoT | Index
- | Glossary | Bibliography | Reference" >
-
-<!-- The sect1.gp parameter entity is used in Chapter, Preface,
- and Appendix -->
-
-<!ENTITY % sect1.gp "((%refnav.gp;)*, (%component.gp;)+, Sect1*, (%refnav.gp;)?)" >
-
-
-
-<!-- ====================================================================
- TOP-LEVEL DOCUMENT STRUCTURE -->
-
-<!-- The intended base document element is DocBook, which has the Version
- attribute so that your instance can specify which version of
- this DTD it conforms to. N.B.: a DocBook instance need
- not be a complete book. DocBooks may be nested within
- other DocBooks -->
-
-<!ELEMENT DocBook - - (BookTitle?, ((((%bookcontent.gp;)+)
- | Book | Set) | Docbook+))>
- <!ATTLIST DocBook Version CDATA "1.2">
-
-<!-- A model for a Set of Books -->
-
-<!ELEMENT Set - - (DocInfo?, Book, Book+)>
- <!ATTLIST Set
- %commonatts; >
-
-<!-- A prescriptive model for a Book -->
-
-<!ELEMENT Book - - (DocInfo, Toc?, LoT*,
- Preface*, (Chapter+ | Part+),
- Reference*, Appendix*,
- Glossary*, Bibliography*, Index*)>
- <!ATTLIST Book
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!-- ===================================================================
- GENERAL STRUCTURES FOR BOOKS. A Part contains two or more
- Chapters or Appendices. A Preface, ToC, LoT, Bibliography,
- Glossary, or Index can be a chapter-level component, while ToC,
- LoT, Bibliography, Glossary, RefEntry, and Index may also appear
- within chapter-level components.
- -->
-
-<!ELEMENT Part - - (Title, TitleAbbrev?, PartIntro?, ((Chapter, Chapter+)
- | (Appendix, Appendix+)))>
- <!ATTLIST Part
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT PartIntro - - ((%component.gp;)+)>
- <!ATTLIST PartIntro
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!-- Most of the book component elements -->
-
-<!ELEMENT DocInfo - - ((%docinfo.content.gp)+)>
- <!ATTLIST DocInfo
- %commonatts; >
-
-<!ELEMENT Preface - - (DocInfo?, Title, TitleAbbrev?, %sect1.gp;)>
- <!ATTLIST Preface
- %commonatts; >
-
-<!ELEMENT Chapter - - (DocInfo?, Title, TitleAbbrev?, %sect1.gp;)>
- <!ATTLIST Chapter
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Appendix - - (DocInfo?, Title, TitleAbbrev?, %sect1.gp;)>
- <!ATTLIST Appendix
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Reference - - (DocInfo?, Title, TitleAbbrev?, PartIntro?, RefEntry+)>
- <!ATTLIST Reference
- %commonatts; >
-
-<!ELEMENT ToC - - (DocInfo?, (Title, TitleAbbrev?)?, ToCentry1+)>
- <!ATTLIST ToC
- %commonatts; >
-
-<!ELEMENT LoT - - (DocInfo?, (Title, TitleAbbrev?)?, LoTentry+)>
- <!ATTLIST LoT
- %commonatts; >
-
-<!ELEMENT Bibliography - - (DocInfo?, (Title, TitleAbbrev?)?, Para*, BiblioEntry+)>
- <!ATTLIST Bibliography
- %commonatts; >
-
-<!ELEMENT Glossary - - (DocInfo?, (Title, TitleAbbrev?)?, Para*, GlossaryEntry+)>
- <!ATTLIST Glossary
- %commonatts; >
-
-<!ELEMENT Index - - (DocInfo?, (Title, TitleAbbrev?)?, Para*, IndexEntry+)>
- <!ATTLIST Index
- %commonatts; >
-
-<!-- ============================================================
- SECTIONS -->
-
-<!ELEMENT Sect1 - - (Title, TitleAbbrev?, (%refnav.gp;)*, (%component.gp;)+,
- Sect2*, (%refnav.gp;)*)>
- <!ATTLIST Sect1
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Sect2 - - (Title, TitleAbbrev?, (%refnav.gp;)*, (%component.gp;)+,
- Sect3*, (%refnav.gp;)*)>
- <!ATTLIST Sect2
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Sect3 - - (Title, TitleAbbrev?, (%refnav.gp;)*, (%component.gp;)+,
- Sect4*, (%refnav.gp;)*)>
- <!ATTLIST Sect3
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Sect4 - - (Title, TitleAbbrev?, (%refnav.gp;)*, (%component.gp;)+,
- Sect5*, (%refnav.gp;)*)>
- <!ATTLIST Sect4
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Sect5 - - (Title, TitleAbbrev?, (%refnav.gp;)*,
- (%component.gp;)+, (%refnav.gp;)*)>
- <!ATTLIST Sect5
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Task - - ((Title, TitleAbbrev?)?, (Para | %list.gp;)+)>
- <!ATTLIST Task %commonatts; >
-
-<!ELEMENT Sidebar - - ((Title, TitleAbbrev?)?, (%component.gp;)+)>
- <!ATTLIST Sidebar %commonatts; >
-
-<!-- ============================================================
- PARAGRAPHS and RELATED ELEMENTS -->
-
-<!ELEMENT Para - - (Title?, (%inlinechar.gp; | %list.gp; | %object.gp;)+)>
- <!ATTLIST Para
- %commonatts; >
-
-<!ELEMENT (Abstract | AuthorBlurb
- | Comment ) - - (Title?, (%paracontent.gp;)+)>
- <!ATTLIST (Abstract | Authorblurb)
- %commonatts; >
-
-<!ELEMENT (Tip | Caution | Warning | Important | Note
- | BlockQuote) - - (Title?, (%component.gp;)+)>
- <!ATTLIST (Tip | Caution | Warning | Important
- | Note | BlockQuote ) %commonatts; >
-
-<!ELEMENT Highlights - - ((%list.gp; | Para
- | (Tip | Caution | Warning | Important | Note))+)>
- <!ATTLIST Highlights %commonatts; >
-
-<!ELEMENT Footnote - - ((%component.gp;)+)>
- <!ATTLIST Footnote
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Epigraph - - ((Para)+)>
- <!ATTLIST Epigraph
- %commonatts; >
-
-<!ELEMENT Title - - ((%inlinechar.gp;)+) >
- <!ATTLIST Title %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT TitleAbbrev - - ((%inlinechar.gp;)+) >
- <!ATTLIST TitleAbbrev %commonatts; >
-
-<!-- ==============================================================
- LISTS -->
-
-<!-- The Mark attribute specifies the mark that should appear before
- each ListItem, such as Bullet, Dash, Box, Check.
- You might want to make these entities (such as •) -->
-
-<!ELEMENT ItemizedList - - (ListItem+)>
- <!ATTLIST ItemizedList
- %commonatts;
- Mark CDATA #IMPLIED>
-
-<!ELEMENT ListItem - - ((Para | %list.gp; | Figure
- | %object.gp;)*)>
- <!ATTLIST ListItem %commonatts; >
-
-<!ELEMENT SegmentedList - - ((Title, TitleAbbrev?)?,
- SegTitle*, SegListItem+)>
- <!ATTLIST SegmentedList %commonatts; >
-
-<!ELEMENT SegTitle - - ((%inlinechar.gp;)+)>
- <!ATTLIST SegTitle %commonatts;
- HasRefEntry (Yes|No) No >
-
-<!ELEMENT SegListItem - - (Seg, Seg+)>
- <!ATTLIST SegListItem %commonatts; >
-
-<!ELEMENT Seg - - ((%inlinechar.gp;)+)>
- <!ATTLIST Seg %commonatts;
- HasRefEntry (Yes|No) No >
-
-<!ELEMENT OrderedList - - (ListItem+)>
- <!ATTLIST OrderedList
- %commonatts;
- Numeration (Arabic | Upperalpha | Loweralpha
- | Upperroman | Lowerroman) Arabic
- InheritNum (Inherit | Ignore) Ignore
- Continuation (Yes | No) No >
-
-<!ELEMENT VariableList - - ((Title, TitleAbbrev?)?, VarListEntry+)>
- <!ATTLIST VariableList %commonatts; >
-
-<!ELEMENT VarListEntry - - (Term+, ListItem)>
- <!ATTLIST VarListEntry %commonatts; >
-
-<!ELEMENT Term - - (((%inlinechar.gp;)+ | Synopsis))>
- <!ATTLIST Term %commonatts;
- HasRefEntry (Yes|No) No >
-
-<!ELEMENT SimpleList - - (Term+)>
- <!ATTLIST SimpleList %commonatts;
- Wrap (Vert | Horiz | None) None>
-
-<!-- ================================================================
- LINKS
- Use of the HyTime terms Linkend and Endterm
- does not indicate that HyTime processing is required.
- Link has both Endterm and Linkend attributes:
- Linkend is the spot linked to, Endterm identifies information
- that may be used by the Link. You might, for example,
- make the Linkend a Sect2 and make the Endterm its Title.
- -->
-
-<!ELEMENT Anchor - O EMPTY>
- <!ATTLIST Anchor
- %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT Link - - ((%inlinechar.gp;)+)>
- <!ATTLIST Link
- Endterm IDREF #IMPLIED
- Linkend IDREF #REQUIRED
- Type CDATA #IMPLIED>
-
-<!-- ExternalLink avoids using IDREFs so you can link to a location
- not available to the SGML parser without incurring parsing errors
- -->
-
-<!ELEMENT ExternalLink - - ((%inlinechar.gp;)+)>
- <!ATTLIST ExternalLink
- Endterm CDATA #IMPLIED
- Linkend CDATA #REQUIRED
- Type CDATA #IMPLIED>
-
-<!ELEMENT FootnoteRef - O (#PCDATA)>
- <!ATTLIST FootnoteRef
- id ID #IMPLIED
- Linkend IDREF #REQUIRED
- Mark CDATA #IMPLIED>
-
-<!ELEMENT XRef - - (#PCDATA)>
- <!ATTLIST XRef
- Endterm IDREF #IMPLIED
- Linkend IDREF #REQUIRED>
-
-<!-- =================================================================
- OBJECTS -->
-
-<!ELEMENT Example - - (Title, TitleAbbrev?,
- (Screen | LiteralLayout | ProgramListing)+)>
- <!ATTLIST Example %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT ProgramListing - - ((%inlinechar.gp;)+)>
- <!ATTLIST ProgramListing %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT LiteralLayout - - ((%inlinechar.gp;)+)>
- <!ATTLIST LiteralLayout %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT Screen - - (((%inlinechar.gp;)+) | (ScreenInfo, Graphic))>
- <!ATTLIST Screen %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT ScreenInfo - - (#PCDATA)>
- <!ATTLIST ScreenInfo %commonatts; >
-
-<!-- Graphic is for in-line use or inclusion in another element.
- Graphical data can be the content of Graphic, or you
- can reference an external file through the
- Fileref attribute, either as an entity or a filename. -->
-
-<!ELEMENT Graphic - - CDATA>
- <!ATTLIST Graphic
- format NOTATION (%local.notations; | GIF | TIFF
- | CGM | DVI | EPS
- | TBL | EQN | PS
- | DITROFF | PIC) #IMPLIED
- Fileref CDATA #IMPLIED
- Entityref ENTITY #IMPLIED
- id ID #IMPLIED>
-
-<!-- N.B.: Graphic occurs in object.gp, so does not appear explicitly
- in Figure. -->
-
-<!ELEMENT Figure - - (Title, TitleAbbrev?,
- (%object.gp; | IndexTerm)*)>
- <!ATTLIST Figure id ID #IMPLIED
- Height CDATA #IMPLIED
- Width CDATA #IMPLIED
- Align (l|c|r) l
- Float (YES | NO) NO >
-
-<!ELEMENT Equation - - ((Title, TitleAbbrev?)?, Graphic)>
- <!ATTLIST Equation %commonatts; >
-
-<!-- ================================================================
- TABLE
- A simple model; you can use any other table model by making
- a local modification. -->
-
-<!ELEMENT Table - - ((Title, TitleAbbrev?)?, Graphic?,
- (TableSpec?, TableColHead*, TableRow+)?)>
- <!ATTLIST Table %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT TableSpec - - (%inlinechar.gp;)>
- <!ATTLIST TableSpec %commonatts; >
-
-<!ELEMENT TableColHead - - (TableCell+)>
- <!ATTLIST TableColHead %commonatts; >
-
-<!ELEMENT TableCell - - ((Para | %inlinechar.gp;)+)>
- <!ATTLIST TableCell %commonatts; >
-
-<!ELEMENT TableRow - - (TableCell+)>
- <!ATTLIST TableRow %commonatts; >
-
-<!-- ===============================================================
- NAVIGATIONAL AND REFERENCE -->
-
-<!ELEMENT ToCentry1 - - ((%inlinechar.gp;)+, ToCentry2*)>
- <!ATTLIST ToCentry1 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT ToCentry2 - - ((%inlinechar.gp;)+, ToCentry3*)>
- <!ATTLIST ToCentry2 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT ToCentry3 - - ((%inlinechar.gp;)+, ToCentry4*)>
- <!ATTLIST ToCentry3 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT ToCentry4 - - ((%inlinechar.gp;)+, ToCentry5*)>
- <!ATTLIST ToCentry4 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT ToCentry5 - - ((%inlinechar.gp;)+)>
- <!ATTLIST ToCentry5 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT GlossaryEntry - - (GlossaryTerm, GlossaryDef)>
- <!ATTLIST GlossaryEntry %commonatts; >
-
-<!ELEMENT BiblioEntry - - (TitleAbbrev?,
- (Author | CorpAuthor | Editor | Title)+,
- Subtitle?, Date?,
- Publisher?, #PCDATA)>
- <!ATTLIST BiblioEntry %commonatts; >
-
-<!-- IndexTerms appear in the text, not in the Index. -->
-
-<!ELEMENT IndexTerm - - (Primary,
- (((Secondary, (Tertiary | See | SeeAlso+)?) | See | SeeAlso+))?)>
- <!ATTLIST IndexTerm
- %commonatts;
- Span (Start|End) #IMPLIED
- Pagenum CDATA #IMPLIED>
-
-<!ELEMENT (Primary | Secondary | Tertiary ) - - ((%inlinechar.gp;
- | IndexAs)+)>
- <!ATTLIST (Primary | Secondary | Tertiary )
- %commonatts;>
-
-<!ELEMENT IndexAs - - ((%inlinechar.gp;)+)>
- <!ATTLIST IndexAs %commonatts;>
-
-<!ELEMENT (See | SeeAlso) - - ((%inlinechar.gp;)+)>
- <!ATTLIST (See | SeeAlso)
- %commonatts;
- HasRefEntry (Yes | No) No >
-
-<!-- IndexEntries appear in the Index, not the text. -->
-
-<!ENTITY % primsee "PrimaryIE, (SeeIE | SeeAlsoIE+)*" >
-
-<!ENTITY % secsee "(SecondaryIE, ((SeeIE | SeeAlsoIE+) | TertiaryIE)*)" >
-
-<!ELEMENT IndexEntry - - (%primsee, (%secsee)*)>
-<!ATTLIST IndexEntry
- %commonatts; >
-
-<!ELEMENT PrimaryIE - - (#PCDATA)>
- <!ATTLIST PrimaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED>
-
-<!ELEMENT SecondaryIE - - (#PCDATA)>
- <!ATTLIST SecondaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED>
-
-<!ELEMENT TertiaryIE - - (#PCDATA) >
- <!ATTLIST TertiaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED>
-
-<!ELEMENT SeeIE - - (#PCDATA) >
- <!ATTLIST SeeIE %commonatts;
- Linkend IDREF #REQUIRED>
-
-<!ELEMENT SeeAlsoIE - - (#PCDATA) >
- <!ATTLIST SeeAlsoIE %commonatts;
- Linkends IDREFS #REQUIRED>
-
-<!ELEMENT LoTentry - - ((%inlinechar.gp;)+ )>
- <!ATTLIST LoTentry %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!-- ==============================================================
- DOCINFO elements; some appear in BiblioEntry, too -->
-
-<!ELEMENT Author - - ((Honorific | Firstname
- | Surname | OtherName)+) >
-
-<!ELEMENT Editor - - ((Honorific | Firstname
- | Surname | OtherName)+) >
-
-<!ELEMENT (AuthorInitials | BookAcronym | CorpAuthor | CorpName
- | Date | Edition
- | Firstname | Holder
- | Honorific | ISBN | InvPartNumber
- | OrgName | OtherName
- | ProductName | ProductNumber
- | Publisher | ReleaseInfo
- | RevNumber | RevRemark
- | Series | Subtitle
- | Surname | Year ) - - (#PCDATA)>
-
-<!ELEMENT Copyright - - (Year+, Holder*)>
-
-<!ELEMENT LegalNotice - - ((Para | BlockQuote)+)>
-
-<!ELEMENT PrintHistory - - (Para+)>
-
-<!ELEMENT RevHistory - - (Revision*)>
-
-<!ELEMENT Revision - - (RevNumber, Date, AuthorInitials+, RevRemark)>
-
-<!ELEMENT BookTitle - - (Title, Subtitle?, TitleAbbrev?,
- ReleaseInfo?, BookAcronym?)>
-
-<!-- ==================================================================
- OTHER IN-LINE ELEMENTS -->
-
-<!ELEMENT (FunctionParam | VarParam) - - ((#PCDATA
- | Superscript | Subscript)+)>
- <!ATTLIST VarParam %commonatts; >
-
-<!ELEMENT Command - - ((%basechar.gp; | Optional | Option)+)>
-
-<!ELEMENT (Action | Filename | Function
- | Hardware | KeyCap | Interface
- | InterfaceDefinition
- | Property | ProtocolRequest
- | SystemItem) - - ((%basechar.gp; | Optional)+)>
-
-<!ELEMENT Option - - ((%basechar.gp; | Optional)+)>
-
-<!ELEMENT (ComputerOutput | Literal) - - (Anchor | #PCDATA)>
-
-<!ELEMENT (CiteBook | CiteChap | CiteSect
- | CiteRefEntry | GlossaryTerm
- | GlossaryDef | UserInput
- | Quote) - - ((%inlinechar.gp;)+)>
-
-
-<!ELEMENT Subscript - - (#PCDATA | Subscript)>
-
-<!ELEMENT Superscript - - (#PCDATA | Superscript)>
-
-<!ELEMENT (Acronym | Application | Button | Character | Charset
- | Citation | Classname | Constant
- | DbName | DbTable | DbField | DbRecord
- | Emphasis | Error
- | EventType | EventStructure | FirstTerm
- | Font | ForeignPhrase | Glyph | HWapplic
- | Icon | KeySym | KeyCode | LineAnnotation
- | Macro | Mask | Menu | MenuItem
- | OSname | Prompt
- | PubsNumber | Resource | ReturnValue
- | StructField | StructName
- | SWapplic | Symbol
- | SystemName | Token | Type
- | VolumeNumber | WordAsWord) - - (#PCDATA)>
-
-<!-- The element named Optional is for use in syntax lines, as in a
- RefEntry, where optional parameters are shown in square
- brackets. Optional should replace those brackets. -->
-
-<!ELEMENT (Optional | Trademark) - - ((%basechar.gp; | %computerterms.gp;
- | Optional)+)>
- <!ATTLIST Optional %commonatts; >
-
-<!-- ================================================================
- REFERENCE ENTRIES -->
-
-<!ELEMENT RefEntry - - (DocInfo?, RefMeta?,
- (Comment | IndexTerm)*,
- RefNameDiv,
- RefSynopsisDiv?,
- RefSect1+)>
- <!ATTLIST RefEntry %commonatts; >
-
-<!ELEMENT RefMeta - - (RefFileName, ManVolNum?, RefMiscInfo*)>
- <!ATTLIST RefMeta %commonatts; >
-
-<!ELEMENT RefFileName - - (#PCDATA)>
- <!ATTLIST RefFileName %commonatts; >
-
-<!ELEMENT ManVolNum - - (#PCDATA)>
- <!ATTLIST ManVolNum %commonatts; >
-
-<!ELEMENT RefMiscInfo - - (#PCDATA)>
- <!ATTLIST RefMiscInfo %commonatts; >
-
-<!ELEMENT RefNameDiv - - (RefDescriptor?, RefName+,
- RefPurpose, (%local.refclasses;)?,
- (Comment | IndexTerm)*)>
- <!ATTLIST RefNameDiv %commonatts; >
-
-<!ELEMENT RefDescriptor - - (#PCDATA)>
- <!ATTLIST RefDescriptor %commonatts; >
-
-<!ELEMENT RefName - - ((#PCDATA | %computerterms.gp;)+)>
- <!ATTLIST RefName %commonatts; >
-
-<!ELEMENT RefPurpose - - ((%inlinechar.gp;)+)>
- <!ATTLIST RefPurpose %commonatts; >
-
-<!-- RefClass includes local.refclasses, as they are meant to
- be subelements, not alternatives, as is the case with
- the other local.* groups -->
-
-<!ELEMENT RefClass - - ((%inlinechar.gp;)+)>
-
-<!ELEMENT RefSynopsisDiv - - ((Synopsis, RefSect2*)
- | (RefSect2+))>
- <!ATTLIST RefSynopsisDiv %commonatts;
- Name (Synopsis | Syntax) Synopsis >
-
-<!ELEMENT Synopsis - - ((%inlinechar.gp;)+)>
- <!ATTLIST Synopsis %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT RefSect1 - - (Title,
- (((%component.gp;)+, RefSect2*) | RefSect2+))>
- <!ATTLIST RefSect1 %commonatts; >
-
-<!ELEMENT RefSect2 - - (Title, (%component.gp;)+)>
- <!ATTLIST RefSect2 %commonatts; >
-
-<!-- end of the DocBook DTD -->
+++ /dev/null
-<DOCBOOK
-<CHAPTER>
-<TITLE>DocBook DTD 1.2: The Elements Alphabetized</TITLE>
-<ITEMIZEDLIST>
-<LISTITEM><PARA>Abstract is a summary of a document's content. It
-contains Paras and may bear a Title. Abstract
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Acronym is a pseudoword made up of the initials or
-initial parts of a conventional series of words. For
-purposes of the DocBook DTD Acronym may also be a string
-of initials. Acronym contains plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Action is a function to be invoked in response to a user event.
-It contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Anchor marks a target for a Link, and may appear almost anywhere.
-Anchor has no content, and no end tag.
-Anchor has common and Pagenum attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Appendix may contain anything
-found in a Chapter.
-It may have a DocInfo and
-must have a Title and may have a TitleAbbrev.
-Appendix has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Application is the name of a software program that does something
-useful. Application may contain
-plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Author is part of DocInfo and consists of
-one or more optional Firstnames and an optional Surname element.
-Author also occurs in BiblioEntry. It has
-common attributes.
-<LITERALLAYOUT>
-<AUTHOR><FIRSTNAME>Marmaduke Anthony</FIRSTNAME>
-<SURNAME>Pickthall</SURNAME></AUTHOR>
-</LITERALLAYOUT>
-</PARA></LISTITEM>
-<LISTITEM><PARA>AuthorBlurb is a short description of a document's
-author. It
-contains Paras and may bear a Title. AuthorBlurb
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>AuthorInitials indicate the author of
-a Revision or Comment.
-AuthorInitials contains plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>BiblioEntry is an entry in a Bibliography. For
-flexibility, it may contain a TitleAbbrev, must
-contain at least one of Author, CorpAuthor, OtherAuthor,
-Editor, or Title, may
-have any or all of
-Subtitle, Date, and Publisher,
-and following all of that, plain text. BiblioEntry
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Bibliography may be a book
-component on its own, or it may appear within a Preface, Chapter,
-or Appendix. It may have a DocInfo,
-a Title and a TitleAbbrev, may have one or more introductory Paras,
-and contains BiblioEntries. No provision
-has been made for bibliographies that are divided into sections.
-Bibliography has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>BlockQuote is a quotation set off from the main text,
-rather than occurring in-line. It may be titled, and
-may contain anything found in a Sect except another
-Sect---that
-is, it may contain Paras, lists, and so forth. BlockQuote has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Book is <EMPHASIS>NOT THE SAME AS DOCBOOK.</EMPHASIS>
-A Book is loosely
-defined as having a required DocInfo, then an optional ToC,
-any number of LoTs, any number of Prefaces, one or more Chapters,
-the following: Appnedix, Bibliography, and
-then, in order, any number of References, Appendixes,
-Glossaries, Bibliographies, and Indexes.
-Book has common and Number
-attributes (you can supply the number of a Book through
-this attribute or as the content of the VolumeNumber
-element in DocInfo).
-</PARA></LISTITEM>
-<LISTITEM><PARA>BookAcronym is an optional part of BookTitle, part of
-DocInfo, and
-may be used alongside or in preference to TitleAbbrev.
-BookAcronym contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>BookTitle is part of DocInfo, and contains, in order,
-a mandatory Title and optional Subtitle, TitleAbbrev, ReleaseInfo,
-and Book Acronym. BookTitle may also appear as the first element
-of DocBook. BookTitle has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Button is a button in a graphical user interface. It
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Caution is an admonition set off from the text and supplied
-with a title, which is ``Caution'' unless another Title is
-supplied explicitly. The contents of a Caution
-may include Paras, lists, and so forth.
-Caution has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Chapter may contain anything except
-higher-level elements
-such as Part, Book, and Set. It may have a DocInfo,
-must have a Title, and may have a TitleAbbrev.
-Chapter has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Character is a character, that is, an element of a writing
-system. Characters may belong to Charsets, and in some contexts
-one may speak of fonts as representing characters. But <EMPHASIS>cf.</EMPHASIS>
-Glyph, Font.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Charset is a conventionally defined
-set of characters, (not a font). Charset
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Citation is any in-line bibliographic
-reference to another published work that uses a reference
-string, such as an abbreviation in a Bibliography.
-Citation may contain plain text only, and has
-common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CiteBook is the name of another book (or journal)
-cited in the text. CiteBook may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CiteChap is a reference to a specific chapter
-(or other component) of any
-book cited in the text, including the book in which
-the CiteChap appears. CiteChap may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CiteRefEntry is a reference to a RefEntry
-in any
-book cited in the text, including the book in which
-the CiteRefEntry
-appears. CiteRefEntry may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CiteSect is a reference to a specific section of another
-document cited in the text, including the document in which
-the CiteSect appears. CiteSect may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Classname is the name of the class to which a
-program component belongs.
-Classname contains plain text and has common
-and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Command is the name of an executable program, or
-the entry a user makes to execute a command.
-Command may contain
-plain text, FunctionParam, VarParam, Anchor, Optional,
-and Option,
-and has common and HasRefEntry
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Comment is a remark made within the document file that
-is intended for use during interim stages of production. A
-finished piece of computer documentation intended for an
-end user would have no visible Comments. Comment may
-appear almost anywhere, and may contain almost anything
-below the Section level;
-it has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ComputerOutput is data presented to the user by a
-computer. It may contain plain text and Anchors,
-and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Constant is a fixed value. Constant contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Copyright is part of DocInfo and consists of one or
-more Years and any number of Holders. Copyright has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CorpAuthor is the corporate author of a book, for use
-in DocInfo or BiblioEntry. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>CorpName is the name of a corporation. It contains
-plain text and has common attributes.
-
-<LISTITEM><PARA>Date appears in DocInfo, BiblioEntry, and Revision, and
-contains plain text. It has common attributes. No provision
-has been made for representing eras; you could include this
-information along with the date data.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DbField is the name of a field in a database.
-DBField contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DbName is the name of a database or database file.
-DbName contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DbRecord is the name of a record in a database.
-DbRecord contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DbTable is the name of a database table. DbTable contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DocBook is the base document element for this DTD.
-It is only a wrapper and has no semantic value.
-</PARA></LISTITEM>
-<LISTITEM><PARA>DocInfo is a book component, containing one or more of the
-following: Author, AuthorInitials, BookAcronym,
-BookTitle, Copyright, CorpAuthor, CorpName, Date,
-Editor, Edition, InvPartNumber, ISBN, LegalNotice,
-OrgName, OtherAuthor, PrintHistory, ProductName, ProductNumber,
-Publisher, PubsNumber, RevHistory, Series,
-and VolumeNumber. No order is enforced among these
-elements, but you are urged to begin with BookTitle and Author(s).
-DocInfo has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Edition is the edition of a document. It contains
-plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Editor is like Author, an element of DocInfo and
-BiblioEntry. It consists of
-one or more optional Firstnames and an optional Surname element.
-It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Emphasis is provided for use where one would traditionally employ italics
-(more rarely, bold) to emphasize a word or phrase. Emphasis
-may contain only plain text; it has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Epigraph is to be used for a brief section of poetry or prose
-at the start of a chapter. It contains Paras, and has and
-common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Equation is a mathematical equation set off on a line
-by itself, or occurring in-line. An Equation has an optional
-Title and TitleAbbrev, and contains a Graphic, <EMPHASIS>q.v.</EMPHASIS>
-Equation has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Error is an error reported by a computer. Error
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>EventStructure is the code that defines an Event.
-EventStructure contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>EventType is a classification of an event.
-EventType
-contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Example is intended for sections of program source code
-that are provided as examples in the text.
-A Example has an optional Title,
-optional TitleAbbrev, and one or more Screens, LiteralLayouts, or
-ProgramListings, in any combination. Example has common
-attributes and bears the
-``linespecific'' Notation attribute.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ExternalLink is like Link, <EMPHASIS>q.v.,</EMPHASIS> except that its
-Linkend and Endlink attributes are not defined as
-SGML IDREFs; this is so you can make reference to
-external documents without
-incurring parsing errors.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Figure is an illustration. A Figure must have a Title, and may have a
-TitleAbbrev; it may then contain
-one or more of the following:
-BlockQuote, Comment, Equation, Example,
-FigureFileRef, Graphic, IndexTerm,
-LiteralLayout, ProgramListing, Screen, Synopsis,
-and Table.
-It has an ID attribute, and also
-Height, Width, Align, and Float attributes. To
-reference an external file containing graphical
-content use the Graphic element.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Filename is the name of a file, including pathname if this
-information is present. Filename may contain
-plain text, FunctionParam, VarParam, and Anchor,
-and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Firstname is part of Author and Editor, <EMPHASIS>q.q.v.</EMPHASIS> It contains
-plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>FirstTerm is to be used for the first occurrence
-of a word in a given context, when
-the style of the document is such that these first occurrences are
-differentiated in some manner. A FirstTerm may contain
-plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Footnote is the text of a footnote.
-The point in the text where the mark for a specific
-footnote goes is indicated by FootnoteRef; the text of
-the Footnote may appear somewhere else in the file.
-A Footnote may contain all of the
-permissible contents of Paras.
-Footnote has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Font is a collection of Glyphs, <EMPHASIS>q.v.</EMPHASIS> Font
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>FootnoteRef indentifies the location for a footnote mark.
-It may contain plain text, which is the mark to be displayed,
-or it may be empty. It has ID, Linkend, and Mark
-attributes: the Linkend attribute has as its value the ID of
-the associated Footnote, and the Mark attribute provides
-another way of indicating the contents of the mark (such as an asterisk, *).
-</PARA></LISTITEM>
-<LISTITEM><PARA>ForeignPhrase is any word or words
-from a language other than
-that of the document which it is desired to mark off
-in some way. In English, <FOREIGNPHRASE>inter alia</FOREIGNPHRASE> and
-<FOREIGNPHRASE>c'est la vie</FOREIGNPHRASE> are ForeignPhrases.
-ForeignPhrase contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Function is a subroutine in a program or external
-library. Function may contain
-plain text, FunctionParam, VarParam, and Anchor, and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>FunctionParam identifies an argument for a Function.
-It may contain plain text, Subscript, and Superscript,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Glossary may occur within a Chapter, Appendix, or Preface,
-or may be a book component in its own right.
-It contains an optional DocInfo,
-optional Title and TitleAbbrev, may contain
-any number of Paras, and then consists of GlossaryEntries.
-No provision has been made for Glossaries divided into sections.
-Glossary has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>GlossaryDef is the definition attached to a GlossaryTerm
-in a GlossaryEntry, which occurs in a Glossary. It may
-contain in-line elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>GlossaryEntry is an entry in a Glossary, containing
-a GlossaryTerm and GlossaryDef. Please note that GlossaryEntry occurs
-in a Glossary, not in the text of (<EMPHASIS>e.g.</EMPHASIS>) a Chapter
-(although a Glossary may be included within a
-Chapter). GlossaryEntry
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>GlossaryTerm is an in-line element for tagging terms in the
-text of a Chapter (for example) that are glossed in a Glossary,
-and also for tagging those terms in GlossaryEntries, in the
-Glossary itself. As you may not want to tag all occurrences
-of these words outside of Glossaries, you might consider
-GlossaryTerm, when used outside of Glossaries, to be similar
-to FirstTerm, except that GlossaryTerm may contain other
-in-line
-elements. GlossaryTerm has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Glyph is a mark, a component of a font. A character
-or ligature might be made up of one, two, or more Glyphs.
-Glyph contains plain text and has common attributes.
-<EMPHASIS>Cf.</EMPHASIS> Character.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Graphic may occur within a Figure, Table, Screen,
-Paragraph, or Equation, to enclose graphical data or to
-point to an external file containing the contents of one of these
-elements. Graphic contains CDATA (data in which
-SGML entities and tags, other than the Graphic end tag, are not
-recognized by the SGML parser) and has format,
-Fileref, Entityref, and ID attributes.
-The format attribute may have the value of
-GIF, TIFF, CGM, DVI, EPS, TEX, TBL, EQN, DITROFF, or PS.
-If it is desired to point to an external file, a filename may
-be supplied as the value of the Fileref attribute, or an
-external entity may be supplied as the value of the
-Entityref attribute.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Hardware is any name for a physical part of a computer system. It
-may contain plain text, FunctionParam, VarParam, and Anchor,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Highlights is a list of main points that are discussed
-a book component such as a Chapter. It may contain
-Paras and lists, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Holder is part of Copyright and is the name of the
-holder of the copyright of the document. It may contain
-plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Honorific is a person's title, to be used as part of Author
-or Editor. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>HWapplic describes the hardware to which
-given context (such as a RefEntry) is relevant. RefClass is
-a good place to put HWapplic information. HWapplic
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Icon is the name of an icon or image
-presented on a computer screen.
-Icon contains plaint text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Important
-is an admonition set off from the text and supplied
-with a title, which is ``Important'' unless another Title is
-supplied explicitly. The contents of an Important
-may include Paras, lists, and so forth.
-Important has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Index may occur within a Chapter, Appendix, or
-Preface, or may be a book
-component on its own.
-It contains an optional DocInfo, Title, and TitleAbbrev, may contain
-any number of Paras, and then consists of IndexEntries.
-No provision has been made for Indices divided into sections. Index has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>IndexAs may be nested within the IndexTerm components
-Primary, Secondary, and Tertiary to indicate an
-alternate string by which the indexed term (the other
-content of Primary, Secondary, or Tertiary) should be
-indexed in the Index. You might want to use this element
-if you tag IndexTerms in the body of the text, rather
-than as separate elements. IndexAs contains in-line
-elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>IndexEntry is a part of Index, and contains a
-PrimaryIE, which may be accompanied by SecondaryIE,
-TertiaryIE, SeeIE, and SeeAlsoIE. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>IndexTerm is a word or phrase to be indexed.
-IndexTerm appears in the text, not in the Index; you
-can apply IndexTerm
-to words in the flow of text or include
-IndexTerms as separate elements.
-Primary, Secondary, and Tertiary
-index items are nested within this tag, as are See and
-SeeAlso items. IndexTerm has common, Span, and PageNum
- attributes.
-The Span attribute, which may have the value
-Start or End, may be used for showing a span
-of text to be indexed.
-The PageNum attribute may be used to
-indicate the page on which the indexed term is found in print.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Interface is the name of any part of a graphical user
-interface,
-such as a button, icon, menu, menu selection, or window; a more
-specific element may be used instead. Interface
-plain text, FunctionParam, VarParam, and
-Anchor, and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>InterfaceDefinition is a specification for a graphical user
-interface. It contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>InvPartNumber is an inventory part number, which
-may occur in DocInfo. It contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ISBN is part of DocInfo, and should be used for the International
-Standard Book Number of the document if it has one. (You could use
-it for an ISSN, also.) ISBN contains plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ItemizedList is a list in which each item is marked with
-a bullet, dash, or other dingbat (or no mark at all). It
-consists of one or more ListItems. A ListItem in an
-ItemizedList contains Paras and other objects, which
-may in turn contain other lists; an ItemizedList may be
-nested within other lists, too. ItemizedList
-has common attributes and
-a Mark attribute. Your application might supply the mark to be used
-for an ItemizedList, but you can use this attribute to
-indicate the mark you desire to be used (such as
-•); for no mark at all, use the attribute but give it
-no value.
-ItemizedList may be nested within Task, so as to provide a
-Title and introductory matter.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Keycap is the text printed on a physical key on a
-computer keyboard, not necessarily the same thing as a
-Keycode. Keycap contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Keycode is the computer's numeric designation of a key on
-a computer keyboard. Keycode contains plain text and has common and HasRefEntry
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Keysym is a key symbol name, which is not necessarily the same thing
-as a Keycap. The Keysym for the H key (Keycap H) is h, for
-example. Keysym contains plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LegalNotice is part of DocInfo, for
-acknowledgement of trademarks and so forth. It consists of
-Paras and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LineAnnotation is a writer's or editor's comment on
-a line of program code within an Example, ProgramListing,
-or Screen. The code's own comments are not
-LineAnnotations. LineAnnotation contains plain text
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Link is a hypertext link. It may contain in-line elements
-and has Endterm, Linkend, and Type attributes. The required
-Linkend attribute specifies the target of the link,
-and the optional Endterm attribute specifies
-text that is to be fetched from elsewhere in the document
-to appear in the Link. You can also supply this text directly as
-the content of the Link.
-The use of the optional Type attribute is undefined, allowing
-you to create local link types.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ListItem is a wrapper for the elements of
-item in an ItemizedList or OrderedList; it also
-occurs within VarListEntry in VariableList.
-It may contain just about anything except Sects and book
-components.
-ListItem has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Literal is any literal string, used in-line, that is part of
-data in a computer. This may be as precise as
-the value of an argument, but Literal may also be used
-as a catch-all element. Literal may contain plain text
-and Anchor; it is not meant as a wrapper for in-line
-elements. Literal
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LiteralLayout is the wrapper for lines set off from
-the main text that are not tagged as Screens, Examples,
-or ProgramListing, in which line breaks and leading
-white space are to be regarded as significant.
-LiteralLayout
-contains in-line elements; it has common attributes
-and the ``linespecific'' Notation attribute.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LoT is the generic tag for such things as a List
-of Figures or List of Tables. An LoT may occur within a Chapter,
-or Appendix, or may be a book
-component on its own.
-It contains an optional DocInfo, Title, and TitleAbbrev,
-followed by multiple LoTentries. LoT has
-common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>LoTentry is an element of LoT, and contains
-the text of the thing to be listed,
-including, if desired, in-line elements. LoTentry has
-common and PageNum attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Macro is the name of a computer macro. It contains plain
-text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ManVolNum, which is specific to UNIX man pages,
- designates the section of a complete set of
-reference pages that a reference page belongs to. It appears
-within RefMeta, contains plain text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Mask specifies which values in a specified structure should
-be read when updating resource values. Mask contains plain text
-and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Menu is part of a graphical user interface, containing
-choices of actions for the user. Menu contains
-plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>MenuItem is a choice in a menu. MenuItem contains
-plain text and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Note is a message to the user, set off from the text and supplied
-with a title, which is ``Note'' unless another Title is
-supplied explicitly. The contents of a Note
-may include Paras, lists, and so forth.
-Note has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Option is a option to a Command (in the Command ``ls -l''
-``-l'' is an Option), but is not nested within Command. It may
-contain plain text, FunctionParam, VarParam, and Anchor, and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Optional is for use in Synopsis, as in a
-RefEntry, where optional parameters
-conventionally are shown in square
-brackets. Optional should replace those brackets; it may contain
-any element listed in the parameter
-entity computerterms.gp, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>OrderedList is a numbered or lettered list, consisting of
-ListItems. A ListItem in an
-OrderedList contains Paras and other objects, which
-may in turn contain other lists; an OrderedList may be
-nested within
-other lists, too.
-OrderedList has common attributes, along with
-a Numeration attribute, which
-may have the value Arabic, Upperalpha, Loweralpha,
-Upperroman, or Lowerroman. The default is Arabic.
- OrderedList
-also has an InheritNum attribute, specifying that for a
-nested list the numbering of ListItems should include the
-number of the item within which they are nested (2a, 2b, etc.,
-rather than a, b, etc.). Orderedlist also has
-a Continuation attribute, with values Yes or No,
-which may be used to
-indicate whether the numbering of a list begins afresh (No)
-or continues that of the immediately preceding list (Yes). The
-default is No, so you need supply the Continuation attribute only
-if your list continues the numbering of the preceding list.
-</PARA></LISTITEM>
-<LISTITEM><PARA>OrgName is the name of an organization that is not
-a corporation (<EMPHASIS>cf.</EMPHASIS> CorpName), for use in DocInfo.
-It contains plain text
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>OSname is the name of an operating system.
-It contains plain text
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>OtherAuthor is provided as an alternative to Author and
-CorpAuthor. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Para is a paragraph. It may have a Title, by means of which
-authors may evade the Sect hierarchy, as with a ``bridgehead.''
-Para may contain any in-line element, any list, Graphic, Equation,
-Synopsis, Table, BlockQuote, ProgramListing, LiteralLayout,
-Screen, and Figure. Abstract, AuthorBlurb, Caution, Important, Note, and
-Warning are excluded, as are Sects and higher-level elements.
-Para has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Part may be used to compose a Book. It
-contains a Title, an optional TitleAbbrev, an optional PartIntro,
-followed by two or more Chapters or Appendices.
-Part has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>PartIntro is a part of Part, and may also appear in
-Reference. In Part, it should introduce the
-contents of the Part. It may contain just about anything except
-Sects. PartIntro has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Preface is a book component, just like a Chapter,
-<EMPHASIS>q.v.</EMPHASIS> Use the Title element to provide the word ``Preface''
-or other string as desired. Preface has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Primary is a word or phrase occurring in
-the text that is to
-appear in the index under as a primary entry. It must be
-nested within IndexTerm tags. Primary may contain in-line elements and IndexAs, <EMPHASIS>q.v.</EMPHASIS> Primary. Primary has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>PrimaryIE is a primary entry in an Index, not in the
-text. It may contain only plain text, and has common
-attributes and a Linkends attribute, which has the
-value of some list of element IDs.
-</PARA></LISTITEM>
-<LISTITEM><PARA>PrintHistory is part of DocInfo, <EMPHASIS>q.v.</EMPHASIS> It contains Paras
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ProductName is a formal name for any product, part
-of DocInfo. It contains plain text and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ProductNumber is a number assigned to a product,
-part of DocInfo. It contains plain text and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ProgramListing contains a listing of a program, including
-LineAnnotations.
-Line breaks and leading
-white space are significant in a ProgramListing. Programlisting
-may contain in-line elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Prompt is a prompt appearing on a computer screen,
-such as the percent sign (%),
-including any other text appearing there (marmaduke%).
-Prompt may contain only plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Property is the name of a defined set of data
-associated with a window. Property may contain
-in-line elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ProtocolRequest is a message sent from a program to the
-server. ProtocolRequest contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>PubsNumber is a number assigned to a publication
-other than ISBN, for use
-in DocInfo. <EMPHASIS>Cf.</EMPHASIS> also InvPartNumber. PubsNumber
-contains plain text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Publisher is an element of DocInfo and BiblioEntry. It may contain
-plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Quote is supplied for in-line quotations. For block quotes
-use BlockQuote. Quote may contain in-line elements and has
-common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefClass is an element of RefNameDiv, in which the
-applicability or scope of the topic of a RefEntry may be
-indicated (such as the element SWapplic or
-a string such as ``LocalBlocking''). It may contain
-in-line elements and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefDescriptor is a substitute for RefName to be used when a
-RefEntry covers more than one topic and none of the topic name
-is to be used as the sort name. RefDescriptor contains plain
-text and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefEntry is a reference page. RefEntry
-has common attributes. For more on RefEntries see
-version 1.0 of the <CITEBOOK>Guide to the DocBook DTD.</CITEBOOK>
-</PARA></LISTITEM>
-<LISTITEM><PARA>Reference is a collection of RefEntries. It may
-be a book
-component on its own,
-or it may appear within a Preface, Chapter, or Appendix.
-Reference has an optional DocInfo,
-a required Title,
-an optional TitleAbbrev, an optional PartIntro, and
-one or more RefEntries.
-Reference has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefFileName is the primary name given to the reference page for
-sorting and indexing. It may be the same as the first of
-the RefNames, or it may be the same as the
-RefDescriptor.
-RefFileName may contain only plain text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefMeta is the first major division of a reference page,
-in which metainformation about the reference page is supplied.
-RefMeta is optional, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefMiscInfo marks information in RefMeta that may be
-supplied by vendors, such as copyright, release date, revision
-date, print status, operating system, hardware architecture,
-or a descriptive phrase for use in a print header. It
-may contain only plain text, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefName is the name of the subject or subjects of a
-reference page, and appears within RefNameDiv. It
-may contain plain text and in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefNameDiv is the second major division of a reference page,
-in which the name (RefName) or names of the subject or subjects of the
-reference page are given, along with a RefPurpose.
-RefNameDiv has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefPurpose is a short phrase describing the subject of
-the reference page. It follows the RefNames in
-the RefNameDiv division. It may contain in-line elements,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefSect1 is equivalent to a Sect1 in the DocBook DTD.
-It contains a Title, followed by any of the allowable contents
-of a Sect, except that only one level of subsection
-is allowed, called RefSect2. RefSect1 has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefSect2 is equivalent to a Sect2 in the DocBook DTD, and may
-occur within RefSect1 or RefSynopsisDiv. It may contain any of the
-allowable contents of a Sect, except that no further subsections
-are allowed. RefSect2 has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RefSynopsisDiv is the third major division of a reference page,
-in which the syntax of the subject of the reference page is
-indicated. It contains a Synopsis, and may have
-subdivisions, which must be RefSect2s, not RefSect1s (that is,
-RefSynopsisDiv counts as a RefSect1).
-RefSynopsisDiv has common attributes and a Name
-attribute, which may be either Synopsis or Syntax;
-the default is Synopsis.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ReleaseInfo is an element of DocInfo, in which
-information about a particular version of a document may
-occur. It may contain only plain text, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Resource is a configurable setting available to a program
-that controls its behavior or appearance.
-Resource
-may contain plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ReturnValue is a value returned by a function.
-ReturnValue may contain plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RevHistory is a section of DocInfo
-consisting of Revisions. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Revision is an entry in RevHistory, describing some
-revision made to the text. A Revision has a mandatory
-Revisionnumber and Date, one or more sets of AuthorInitials, and a
-Revisionremark. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RevNumber is an element of Revision, <EMPHASIS>q.v.</EMPHASIS>
-It may contain only plain text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>RevRemark is an element
-of Revision, describing the Revision.
-It may contain only plain text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Screen is intended to represent what the user sees or
-might see on a computer screen.
-A Screen may
-consist of in-line elements (in which line breaks
-and leading white space are considered
-significant) or a ScreenInfo and a Graphic. Screen has common attributes and the Notation attribute
-``linespecific.''
-</PARA></LISTITEM>
-<LISTITEM><PARA>ScreenInfo is a part of Screen, <EMPHASIS>q.v.</EMPHASIS> A ScreenInfo
-indicates how the Graphic with which it is paired was created
-as a guide for future revisions. It may contain only plain
-text, and has common
-attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Secondary is a word or phrase in the text that is to
-appear in the index beneath a Primary entry. It must be
-nested within IndexTerm tags and must follow a Primary element.
-Secondary may contain in-line elements
-and IndexAs, and has common and
-HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SecondaryIE is part of IndexEntry, like PrimaryIE, <EMPHASIS>q.v.</EMPHASIS>
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect1 marks a section of a document that
-begins with a first-level heading. Anything may occur
-within a Sect1 except a DocInfo, Preface,
-Chapter, Appendix, or
-another Sect1, including a Glossary, Bibliography, RefEntry, Reference, Toc, Index,
-or LoT. Sect1 must have a Title, which is the text
-of the heading itself, it may have a TitleAbbrev, and must
-include some content other than in-line elements and
-plain text; these must occur in Paras or other
-objects. Sect1--5 have common
-and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect2 is a section beginning with a second-level
-heading, and must be nested within a Sect1.
-Allowable and required content
-for Sect2s are like those for Sect1s.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect3. <EMPHASIS>Cf.</EMPHASIS> Sect2.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect4. <EMPHASIS>Cf.</EMPHASIS> Sect2.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sect5. <EMPHASIS>Cf.</EMPHASIS> Sect2. No further subdivisions are
-supplied in the DocBook DTD.
-</PARA></LISTITEM>
-<LISTITEM><PARA>See is part of IndexTerm, indicating, for
-a word or phrase in the text, the index entry to
-which the reader is to be directed when he consults
-the stub index entry for another element within
-the IndexTerm.
-See must be nested within IndexTerm tags and must
-follow a Primary or Secondary element.
-See may contain in-line
-elements and has common and HasRefEntry attributes..
-</PARA></LISTITEM>
-<LISTITEM><PARA>SeeAlso is like See, but indicates
-the index entries to which the reader is <EMPHASIS>also</EMPHASIS>
-to be directed when he consults a full index entry.
-SeeAlso must be nested within IndexTerm tags and must
-follow a Primary or Secondary element.
-SeeAlso may contain in-line
-elements and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SeeAlsoIE is a ``see also'' entry in an Index, not in the
-text, occurring
-unnested within IndexEntry at the PrimaryIE or
-SecondaryIE level.
-It may contain plain text only, and has common
-attributes and a Linkends attribute, which has the
-value of some list of IndexEntry IDs.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SeeIE is a ``see'' entry in an Index, not in the
-text, occurring
-unnested within IndexEntry at the PrimaryIE or
-SecondaryIE level.
-It may contain plain text only, and has common
-attributes and a Linkend attribute, which has the
-value of some IndexEntry ID.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Seg is a component of a SegmentedList. Segs are the only
-content of a SegmentedList's
-SegListItems. They may contain in-line
-elements. Seg has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SegListItem is a list item in a SegmentedList. It consists
-of two or more Segs, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SegmentedList is a list of sets of units without additional text
-(and is thus different from the VarListItem,
-composed of Terms and ListItem,
-in a VariableList). A SegmentedList may be used to represent
-sets of information often presented as simple tables. A SegmentedList
-may have a Title and TitleAbbrev, followed by any number
-of SegTitles, and two or more SegListItems. SegmentedList
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SegTitle is a title that pertains to one Seg in each
-SegListItem: the first SegTitle to the first Seg, the second SegTitle
-to the second Seg, and so on. SegTitles may contain in-line elements,
-and are grouped at the beginning of a SegmentedList, before the SegListItems.
-SegTitle has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Series is part of DocInfo and names the publication series of
-which the book is a part. Series may contain only plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Set is a set of Books. It has an optional DocInfo and
-must contain two or more Books. Set has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Sidebar is a segment of text isolated from the narrative flow
-of the main text, typically boxed. A Sidebar may have
-a Title and a TitleAbbrev, and must have text formatted in
-some fashion: allowable contents
-include Paras, lists, Figures, and
-Tables. No Sects allowed. Sidebar has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>StructField is a field in a Structure. It may
-contain plain text only, and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>StructName is the name of a Structure. It may
-contain plain text only, and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Subscript tags subscripts. It may contain plain text
-and another
-Subscript, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Subtitle is for use in BookTitle. It contains plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Superscript tags superscripts.
-It may contain plain text and another Superscript,
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Surname is an element of Author in DocInfo, supplied so
-that a group of documents may be indexed
-by their authors's surnames. It may contain
-plain text only, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SWapplic specifies the applicability of information
-given a software context.
-RefClass is a good place to put SWapplic information.
-SWapplic contains plain text only and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Symbol is a name that is replaced by a value before processing.
-Symbol contains plain text and
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Synopsis marks the line or lines that provide the
-syntax of a command or function. It appears
-within RefSynopsisDiv, and may occur elsewhere in
-a document, too.
-Synopsis may contain in-line elements; within it,
-line breaks and white space are significant. It
-has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SystemItem may be used for any
-system-related item, as a catch-all.
-It may contain plain text, FunctionParam, VarParam,
-Anchor, and Optional,
-and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>SystemName is the name of any system. It may
-contain plain text only, and has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Table is an array of text. A Table may have
-a Title, TitleAbbrev, and Graphic; following those
-elements
-it may have a TableSpec (containing such things as troff
-formatting information), any
-number of TableColHeads (containing headings
-for the columns of the Table), and one or more TableRows of
-TableCells. Table has common and Number attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TableCell is a part of a TableRow in a Table. It may contain
-in-line elements and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TableColHead is an optional part of Table, containing
-headings for the columns of the Table as TableCells.
-It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TableRow is part of Table. A Table has TableRows of TableCells.
-It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TableSpec tags formatting information for a Table; it is
-not the text of a Table's heading. It may contain
-in-line elements and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Task is any set of Paras and lists that
-instructs the reader how to perform a given task. Task
-may have a Title and TitleAbbrev, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Term is the hanging term attached to a ListItem within
-a VarListEntry in a
-VariableList; visually, a VariableList
-is a set of Terms with attached items such as paragraphs. Each
-ListItem may be associated with a set of Terms. Term may contain
-in-line elements or Synopsis, and has
-common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Tertiary is a word or phrase that is to
-appear in the index under a Secondary entry. It must be
-nested within IndexTerm tags and must follow a Secondary element.
-Tertiary may contain in-line elements, and has
-common and
-HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TertiaryIE is part of IndexEntry, like PrimaryIE, <EMPHASIS>q.v.</EMPHASIS>
-</PARA></LISTITEM>
-<LISTITEM><PARA>Tip is a suggestion to the user, set off from the text and supplied
-with a title, which is ``Tip'' unless another Title is
-supplied explicitly. The contents of a Tip
-may include Paras, lists, and so forth.
-Tip has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Title is a string of characters, the text of a heading
-or element title. It is NOT the title of a Book: that is
-BookTitle. Title may contain
-in-line elements, and has common and PageNum attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>TitleAbbrev is an optional element of
-anything titled. You may want to employ this element when a
-title is so long that you fear it will be truncated in
-some element of an online display, such as a title bar.
-TitleAbbrev may contain
-in-line elements, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ToC is a Table of Contents, which may be
-a book component on its own or may
-occur within other book components. It may
-have a DocInfo, Title, and TitleAbbrev,
-and contains ToCentry1s. ToC has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>ToCentry1 is the top-level tag for items in a ToC. In
-the manner of
-Sect1, it may contain subsidiary groups (<EMPHASIS>e.g.,</EMPHASIS> for headings and
-subheadings within a chapter), named ToCentry2--5. ToCentry1--5s
-have common attributes and
-a PageNum attribute, for indicating the page numbers on which
-the ToCentries appear in a print book. ToCentry1--5 may contain
-in-line elements.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Token is a unit of information in the context of lexical analysis.
- Token contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Type indicates the classification of a value.
- Type contains plain text and
-has common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>UserInput is an in-line element used to tag data entered by the user.
-You might use this element most frequently in LiteralLayouts and
-Screens. UserInput may contain in-line elements, and has
-common and HasRefEntry attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>VariableList is a list of VarListEntries, which are
-composed of sets of one or more Terms with associated
-ListItems, which contain Paras. Inclusions
-are as for OrderedList, <EMPHASIS>q.v.</EMPHASIS> VariableList has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>VarListEntry is a component of VariableList, <EMPHASIS>q.v.</EMPHASIS>
-</PARA></LISTITEM>
-<LISTITEM><PARA>VarParam tags any character string that is to be
-replaced by a real name or value by the user. In
-``cat filename,'' filename is a VarParam. If a
-VarParam is also, say, a Command, nest the VarParam
-tags within the Command tags: VarParam may contain only
-plain text, Superscript, and Subscript,
-not in-line elements. It has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>VolumeNumber is the number of a Book in
-relation to a set or Set. It contains plain text
-and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Warning is an admonition set off from the text and supplied
-with a title, which is ``Warning'' unless another Title is
-supplied explicitly. The contents of a Warning
-may include Paras, lists, and so forth.
-Warning has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>WordAsWord is supplied for use when a word (or letter or
-number) is used not to represent the thing or idea it usually
-represents, but merely as the word itself. For example,
-``The term <WORDASWORD>Gothic</WORDASWORD> means different
-things to art historians and typographers,'' or for a single character,
-``the
-letter <WORDASWORD>X</WORDASWORD>''. WordAsWord may
-contain only plain text, and has common attributes.
-</PARA></LISTITEM>
-<LISTITEM><PARA>XRef is a cross reference link to another part of the document,
-such as a Table, Figure, or Example. An XRef
-may contain text or be empty; it has an Endterm attribute, the value of which
-may be set to the ID of the text to appear in the cross reference if no
-content is supplied.
-An XRef that has both content and an Endterm attribute is faulty.
-XRef also has a Linkend attribute, the value of which is the ID of the
-target of the XRef.
-</PARA></LISTITEM>
-<LISTITEM><PARA>Year is part of DocInfo and BiblioEntry (year of publication of the
-book). Year may contain only plain text, and has common attributes.
-</PARA></LISTITEM>
-</ITEMIZEDLIST>
-</CHAPTER>
-</DOCBOOK>
+++ /dev/null
-<!-- DocBook DTD Release 1.2
-
- 2 March 1993 2:00 PST
-
- Copyright 1992, 1993 HaL Computer Systems, Inc., and
- O'Reilly & Associates, Inc.
-
- Permission to use, copy, modify and distribute the DocBook DTD and
- its accompanying documentation for any purpose and without fee is
- hereby granted, provided that this copyright notice appears in all
- copies. If you modify the DocBook DTD, rename your modified
- version. HaL Computer Systems and O'Reilly & Associates make no
- representation about the suitability of the DTD for any purpose.
- It is provided "as is" without expressed or implied warranty.
-
- The DocBook DTD is maintained by O'Reilly & Associates. Please
- direct all questions, bug reports, or suggestions for changes to
- docbook@ora.com or by mail to: Terry Allen, O'Reilly & Associates,
- Inc., 103A Morris Street, Sebastopol, California, 95472.
-
- Please note that an SGML declaration is provided for this DTD.
-
- Public Identifier:
- "-//HaL and O'Reilly//DTD DocBook 1.1.1//EN"
- -->
-
-<!-- ==================================================================
- NOTATIONS -->
-
-<!NOTATION GIF SYSTEM "GIF" >
-<!NOTATION TIFF SYSTEM "TIFF" >
-<!NOTATION CGM SYSTEM "CGM" >
-<!NOTATION DVI SYSTEM "DVI" >
-<!NOTATION EPS SYSTEM "EPS" >
-<!NOTATION TEX SYSTEM "TEX 3.14" >
-<!NOTATION TBL SYSTEM "TBL" >
-<!NOTATION EQN SYSTEM "EQN" >
-<!NOTATION PS SYSTEM "PS" >
-<!NOTATION DITROFF SYSTEM "DITROFF" >
-<!NOTATION PIC SYSTEM "-//AT&T//NOTATION PIC-1//EN" >
-<!NOTATION linespecific SYSTEM "line ends and leading white space
- must be preserved in output" >
-
-<!-- ==================================================================
- PUBLICLY DECLARED EXTERNAL ENTITIES -->
-
-<!-- Uncomment the ENTITY declaration for your application. -->
-
-<!--
-<!ENTITY % ISOamsa PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Arrow Relations//EN">
- %ISOamsa;
- -->
-<!--
-<!ENTITY % ISOamsa SYSTEM "iso-amsa.gml">
- %ISOamsa;
- -->
-
-<!--
-<!ENTITY % ISOamsb PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Binary Operators//EN">
- %ISOamsb;
- -->
-<!--
-<!ENTITY % ISOamsb SYSTEM "iso-amsb.gml">
- %ISOamsb;
- -->
-
-<!--
-<!ENTITY % ISOamsc PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Delimiters//EN">
- %ISOamsc;
- -->
-<!--
-<!ENTITY % ISOamsc SYSTEM "iso-amsc.gml">
- %ISOamsc;
- -->
-
-<!--
-<!ENTITY % ISOamsn PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Negated Relations//EN">
- %ISOamsn;
- -->
-<!--
-<!ENTITY % ISOamsn SYSTEM "iso-amsn.gml">
- %ISOamsn;
- -->
-
-<!--
-<!ENTITY % ISOamso PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Ordinary//EN">
- %ISOamso;
- -->
-<!--
-<!ENTITY % ISOamso SYSTEM "iso-amso.gml">
- %ISOamso;
- -->
-
-<!--
-<!ENTITY % ISOamsr PUBLIC "ISO 8879:1986//ENTITIES Added Math Symbols: Relations//EN">
- %ISOamsr;
- -->
-<!--
-<!ENTITY % ISOamsr SYSTEM "iso-amsr.gml">
- %ISOamsr;
- -->
-
-<!--
-<!ENTITY % ISObox PUBLIC "ISO 8879:1986//ENTITIES Box and Line Drawing//EN">
- %ISObox;
- -->
-<!--
-<!ENTITY % ISObox SYSTEM "iso-box.gml">
- %ISObox;
- -->
-
-<!--
-<!ENTITY % ISOcyr1 PUBLIC "ISO 8879:1986//ENTITIES Russian Cyrillic//EN">
- %ISOcyr1;
- -->
-<!--
-<!ENTITY % ISOcyr1 SYSTEM "iso-cyr1.gml">
- %ISOcyr1;
- -->
-
-<!--
-<!ENTITY % ISOcyr2 PUBLIC "ISO 8879:1986//ENTITIES Non-Russian Cyrillic//EN">
- %ISOcyr2;
- -->
-<!--
-<!ENTITY % ISOcyr2 SYSTEM "iso-cyr2.gml">
- %ISOcyr2;
- -->
-
-<!--
-<!ENTITY % ISOdia PUBLIC "ISO 8879:1986//ENTITIES Diacritical Marks//EN">
- %ISOdia;
- -->
-<!--
-<!ENTITY % ISOdia SYSTEM "iso-dia.gml">
- %ISOdia;
- -->
-
-<!--
-<!ENTITY % ISOgrk1 PUBLIC "ISO 8879:1986//ENTITIES Greek Letters//EN">
- %ISOgrk1;
- -->
-<!--
-<!ENTITY % ISOgrk1 SYSTEM "iso-grk1.gml">
- %ISOgrk1;
- -->
-
-<!--
-<!ENTITY % ISOgrk2 PUBLIC "ISO 8879:1986//ENTITIES Monotoniko Greek//EN">
- %ISOgrk2;
- -->
-<!--
-<!ENTITY % ISOgrk2 SYSTEM "iso-grk2.gml">
- %ISOgrk2;
- -->
-
-<!--
-<!ENTITY % ISOgrk3 PUBLIC "ISO 8879:1986//ENTITIES Greek Symbols//EN">
- %ISOgrk3;
- -->
-<!--
-<!ENTITY % ISOgrk3 SYSTEM "iso-grk3.gml">
- %ISOgrk3;
- -->
-
-<!--
-<!ENTITY % ISOlat1 PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN">
- %ISOlat1;
- -->
-<!--
-<!ENTITY % ISOlat1 SYSTEM "iso-lat1.gml">
- %ISOlat1;
- -->
-
-<!--
-<!ENTITY % ISOlat2 PUBLIC "ISO 8879:1986//ENTITIES Added Latin 2//EN">
- %ISOlat2;
- -->
-<!--
-<!ENTITY % ISOlat2 SYSTEM "iso-lat2.gml">
- %ISOlat2;
- -->
-
-<!--
-<!ENTITY % ISOnum PUBLIC "ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN">
- %ISOnum;
- -->
-<!--
-<!ENTITY % ISOnum SYSTEM "iso-num.gml">
- %ISOnum;
- -->
-
-<!--
-<!ENTITY % ISOpub PUBLIC "ISO 8879:1986//ENTITIES Publishing//EN">
- %ISOpub;
- -->
-<!--
-<!ENTITY % ISOpub SYSTEM "iso-pub.gml">
- %ISOpub;
- -->
-
-<!--
-<!ENTITY % ISOtech PUBLIC "ISO 8879:1986//ENTITIES General Technical//EN">
- %ISOtech;
- -->
-<!--
-<!ENTITY % ISOtech SYSTEM "iso-tech.gml">
- %ISOtech;
- -->
-
-
-<!-- ==================================================================
- PARAMETER ENTITIES to allow inclusion of local modifications.
- To include your local terms, table content model, graphics
- format, or other local item,
-
- 1. At the head of your instance, after the DOCTYPE line,
- include a reference to an external entity file that
- that includes all the local terms, table content models,
- and (or) graphics formats you are using:
-
- <!DOCTYPE docbook SYSTEM "/yourpath/docbook.dtd" [
- <!ENTITY % localmods SYSTEM "/yourpath/localmodfile" >
- %localmods
- ]>
-
- You may need to set up attributes for your local elements.
-
- N.B.: Depending on the flags you set, your parser may report
- as errors that it has found duplicate specifications of
- these parameter entities. This is harmless, as the
- duplicates are those included below, which are unneeded.
-
- 2. In the referenced external entity file, redefine
- the parameter entities for your local modifications.
- Be sure to include the elements currently defined as
- the content of the following entities if you need
- to use them alongside your local modifications.
- -->
-
-<!ENTITY % local.refnav "RefEntry" >
-<!ENTITY % local.terms "Optional" >
-<!ENTITY % local.tables "Table" >
-<!ENTITY % local.notations "TEX" >
-<!ENTITY % local.refclasses "RefClass" >
-<!ENTITY % local.links "Link" >
-<!ENTITY % local.lists "SegmentedList" >
-
-<!-- =====================================================================
- ATTRIBUTE LIST for a set of common attributes. Remap can be
- used to indicate the value of the element in the original
- source. -->
-
-<!ENTITY % commonatts
- "id ID #IMPLIED
- Remap CDATA #IMPLIED">
-
-<!-- ===================================================================
- OTHER PARAMETER ENTITIES -->
-
-<!-- Book Contents: these are pieces it may be convenient to validate
- on their own -->
-
-<!ENTITY % bookcontent.gp "Appendix | Bibliography
- | Chapter | DocInfo | Glossary
- | Index | LoT | Part | Preface
- | RefEntry | Reference | ToC" >
-
-<!-- Contents that can appear almost anywhere -->
-
-<!ENTITY % links.gp "ExternalLink | FootnoteRef
- | %local.links; | XRef" >
-
-<!ENTITY % basechar.gp "%links.gp; | #PCDATA | FunctionParam
- | IndexTerm | VarParam | Anchor" >
-
-<!-- entities to make up inlinechar.gp -->
-
-<!ENTITY % words.gp "Acronym | Character | Charset | Citation
- | CiteBook | CiteChap
- | CiteRefEntry | CiteSect | Comment
- | Emphasis | FirstTerm
- | Font | ForeignPhrase
- | GlossaryDef | GlossaryTerm | Glyph
- | Quote | Subscript | Superscript
- | Trademark | WordAsWord" >
- <!ATTLIST (%words.gp;) %commonatts; >
-
-<!ENTITY % docinfo.content.gp "Author | AuthorInitials
- | BookAcronym | BookTitle
- | Copyright | CorpAuthor | CorpName | Date
- | Editor | Edition | Firstname
- | Holder | InvPartNumber | ISBN
- | LegalNotice | OrgName | OtherAuthor
- | PrintHistory
- | ProductName | ProductNumber
- | Publisher | PubsNumber | ReleaseInfo
- | RevHistory | Revision
- | RevNumber | RevRemark | Series
- | Subtitle | Surname | VolumeNumber
- | Year" >
- <!ATTLIST (%docinfo.content.gp) %commonatts; >
-
-<!ENTITY % computerterms.gp "Action | Application | Button
- | Classname | Command
- | ComputerOutput | Constant
- | DbName | DbTable | DbField | DbRecord
- | Error | EventType | EventStructure
- | Filename | Option | Function
- | Hardware | HWapplic | Icon
- | Interface | InterfaceDefinition
- | KeyCap | KeyCode | KeySym
- | LineAnnotation | Literal
- | Macro | Mask | Menu | MenuItem
- | Prompt | Property | OSname
- | ProtocolRequest
- | Resource | ReturnValue
- | StructField | StructName
- | SWapplic | Symbol
- | SystemItem | SystemName
- | Token | Type | UserInput" >
- <!ATTLIST (%computerterms.gp;) %commonatts;
- HasRefEntry (Yes|No) No >
-
-
-<!ENTITY % inlinechar.gp "%basechar.gp; | %computerterms.gp;
- | %docinfo.content.gp
- | %local.terms; | %words.gp;" >
-
-<!ENTITY % paracontent.gp "%inlinechar.gp; | Graphic | Equation
- | Synopsis" >
-
-<!-- All the varieties of lists -->
-
-<!ENTITY % list.gp "ItemizedList | OrderedList | %local.lists;
- | VariableList" >
-
-<!-- More elements for other parameter entities -->
-
-<!ENTITY % object.gp "BlockQuote | Caution | Equation
- | Example | Footnote | Graphic
- | Important | LiteralLayout
- | %local.tables; | Note | ProgramListing
- | Screen | Synopsis | Task
- | Tip | Warning" >
-
-<!ENTITY % component.gp "Abstract | Anchor | AuthorBlurb | BiblioEntry
- | Epigraph | Figure | Highlights
- | IndexTerm | %links.gp
- | %list.gp; | %object.gp;
- | Para | Sidebar " >
-
-<!ENTITY % refnav.gp "%local.refnav; | Toc | LoT | Index
- | Glossary | Bibliography | Reference" >
-
-<!-- The sect1.gp parameter entity is used in Chapter, Preface,
- and Appendix -->
-
-<!ENTITY % sect1.gp "((%refnav.gp;)*, (%component.gp;)+, Sect1*, (%refnav.gp;)?)" >
-
-
-
-<!-- ====================================================================
- TOP-LEVEL DOCUMENT STRUCTURE -->
-
-<!-- The intended base document element is DocBook, which has the Version
- attribute so that your instance can specify which version of
- this DTD it conforms to. N.B.: a DocBook instance need
- not be a complete book. DocBooks may be nested within
- other DocBooks -->
-
-<!ELEMENT DocBook - - (BookTitle?, ((((%bookcontent.gp;)+)
- | Book | Set) | Docbook+))>
- <!ATTLIST DocBook Version CDATA "1.2">
-
-<!-- A model for a Set of Books -->
-
-<!ELEMENT Set - - (DocInfo?, Book, Book+)>
- <!ATTLIST Set
- %commonatts; >
-
-<!-- A prescriptive model for a Book -->
-
-<!ELEMENT Book - - (DocInfo, Toc?, LoT*,
- Preface*, Chapter+,
- Reference*, Appendix*,
- Glossary*, Bibliography*, Index*)>
- <!ATTLIST Book
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!-- ===================================================================
- GENERAL STRUCTURES FOR BOOKS. A Part contains two or more
- Chapters or Appendices. A Preface, ToC, LoT, Bibliography,
- Glossary, or Index can be a chapter-level component, while ToC,
- LoT, Bibliography, Glossary, RefEntry, and Index may also appear
- within chapter-level components.
- -->
-
-<!ELEMENT Part - - (Title, TitleAbbrev?, PartIntro?, ((Chapter, Chapter+)
- | (Appendix, Appendix+)))>
- <!ATTLIST Part
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT PartIntro - - ((%component.gp;)+)>
- <!ATTLIST PartIntro
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!-- Most of the book component elements -->
-
-<!ELEMENT DocInfo - - ((%docinfo.content.gp)+)>
- <!ATTLIST DocInfo
- %commonatts; >
-
-<!ELEMENT Preface - - (DocInfo?, Title, TitleAbbrev?, %sect1.gp)>
- <!ATTLIST Preface
- %commonatts; >
-
-<!ELEMENT Chapter - - (DocInfo?, Title, TitleAbbrev?, %sect1.gp)>
- <!ATTLIST Chapter
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Appendix - - (DocInfo?, Title, TitleAbbrev?, %sect1.gp)>
- <!ATTLIST Appendix
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Reference - - (DocInfo?, Title, TitleAbbrev?, PartIntro?, RefEntry+)>
- <!ATTLIST Reference
- %commonatts; >
-
-<!ELEMENT ToC - - (DocInfo?, (Title, TitleAbbrev?)?, ToCentry1+)>
- <!ATTLIST ToC
- %commonatts; >
-
-<!ELEMENT LoT - - (DocInfo?, (Title, TitleAbbrev?)?, LoTentry+)>
- <!ATTLIST LoT
- %commonatts; >
-
-<!ELEMENT Bibliography - - (DocInfo?, (Title, TitleAbbrev?)?, Para*, BiblioEntry+)>
- <!ATTLIST Bibliography
- %commonatts; >
-
-<!ELEMENT Glossary - - (DocInfo?, (Title, TitleAbbrev?)?, Para*, GlossaryEntry+)>
- <!ATTLIST Glossary
- %commonatts; >
-
-<!ELEMENT Index - - (DocInfo?, (Title, TitleAbbrev?)?, Para*, IndexEntry+)>
- <!ATTLIST Index
- %commonatts; >
-
-<!-- ============================================================
- SECTIONS -->
-
-<!ELEMENT Sect1 - - (Title, TitleAbbrev?, (%refnav.gp;)*, (%component.gp;)+,
- Sect2*, (%refnav.gp;)*)>
- <!ATTLIST Sect1
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Sect2 - - (Title, TitleAbbrev?, (%refnav.gp;)*, (%component.gp;)+,
- Sect3*, (%refnav.gp;)*)>
- <!ATTLIST Sect2
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Sect3 - - (Title, TitleAbbrev?, (%refnav.gp;)*, (%component.gp;)+,
- Sect4*, (%refnav.gp;)*)>
- <!ATTLIST Sect3
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Sect4 - - (Title, TitleAbbrev?, (%refnav.gp;)*, (%component.gp;)+,
- Sect5*, (%refnav.gp;)*)>
- <!ATTLIST Sect4
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Sect5 - - (Title, TitleAbbrev?, (%refnav.gp;)*,
- (%component.gp;)+, (%refnav.gp;)*)>
- <!ATTLIST Sect5
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Task - - ((Title, TitleAbbrev?)?, (Para | %list.gp;)+)>
- <!ATTLIST Task %commonatts; >
-
-<!ELEMENT Sidebar - - ((Title, TitleAbbrev?)?, (%component.gp;)+)>
- <!ATTLIST Sidebar %commonatts; >
-
-<!-- ============================================================
- PARAGRAPHS and RELATED ELEMENTS -->
-
-<!ELEMENT Para - - (Title?, (%inlinechar.gp; | %list.gp; | %object.gp;)+)>
- <!ATTLIST Para
- %commonatts; >
-
-<!ELEMENT (Abstract | AuthorBlurb
- | Comment) - - (Title?, (%paracontent.gp;)+)>
- <!ATTLIST (Abstract | Authorblurb)
- %commonatts; >
-
-<!ELEMENT (Tip | Caution | Warning | Important | Note
- | BlockQuote) - - (Title?, (%component.gp;)+)>
- <!ATTLIST (Tip | Caution | Warning | Important
- | Note | BlockQuote ) %commonatts; >
-
-<!ELEMENT Highlights - - ((%list.gp; | Para
- | (Tip | Caution | Warning | Important | Note))+)>
- <!ATTLIST Highlights %commonatts; >
-
-<!ELEMENT Footnote - - ((%component.gp;)+)>
- <!ATTLIST Footnote
- %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT Epigraph - - ((Para)+)>
- <!ATTLIST Epigraph
- %commonatts; >
-
-<!ELEMENT Title - - ((%inlinechar.gp;)+) >
- <!ATTLIST Title %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT TitleAbbrev - - ((%inlinechar.gp;)+) >
- <!ATTLIST TitleAbbrev %commonatts; >
-
-<!-- ==============================================================
- LISTS -->
-
-<!-- The Mark attribute specifies the mark that should appear before
- each ListItem, such as Bullet, Dash, Box, Check.
- You might want to make these entities (such as •) -->
-
-<!ELEMENT ItemizedList - - (ListItem+)>
- <!ATTLIST ItemizedList
- %commonatts;
- Mark CDATA #IMPLIED>
-
-<!ELEMENT ListItem - - ((Para | %list.gp; | Figure
- | %object.gp;)*)>
- <!ATTLIST ListItem %commonatts; >
-
-<!ELEMENT SegmentedList - - ((Title, TitleAbbrev?)?,
- SegTitle*, SegListItem+)>
- <!ATTLIST SegmentedList %commonatts; >
-
-<!ELEMENT SegTitle - - ((%inlinechar.gp;)+)>
- <!ATTLIST SegTitle %commonatts;
- HasRefEntry (Yes|No) No >
-
-<!ELEMENT SegListItem - - (Seg, Seg+)>
- <!ATTLIST SegListItem %commonatts; >
-
-<!ELEMENT Seg - - ((%inlinechar.gp;)+)>
- <!ATTLIST Seg %commonatts;
- HasRefEntry (Yes|No) No >
-
-<!ELEMENT OrderedList - - (ListItem+)>
- <!ATTLIST OrderedList
- %commonatts;
- Numeration (Arabic | Upperalpha | Loweralpha
- | Upperroman | Lowerroman) Arabic
- InheritNum (Inherit | Ignore) Ignore
- Continuation (Yes | No) No >
-
-<!ELEMENT VariableList - - ((Title, TitleAbbrev?)?, VarListEntry+)>
- <!ATTLIST VariableList %commonatts; >
-
-<!ELEMENT VarListEntry - - (Term+, ListItem)>
- <!ATTLIST VarListEntry %commonatts; >
-
-<!ELEMENT Term - - (((%inlinechar.gp;)+ | Synopsis))>
- <!ATTLIST Term %commonatts;
- HasRefEntry (Yes|No) No >
-
-<!-- ================================================================
- LINKS
- Use of the HyTime terms Linkend and Endterm
- does not indicate that HyTime processing is required.
- Link has both Endterm and Linkend attributes:
- Linkend is the spot linked to, Endterm identifies information
- that may be used by the Link. You might, for example,
- make the Linkend a Sect2 and make the Endterm its Title.
- -->
-
-<!ELEMENT Anchor - O EMPTY>
- <!ATTLIST Anchor
- %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT Link - - ((%inlinechar.gp;)+)>
- <!ATTLIST Link
- Endterm IDREF #IMPLIED
- Linkend IDREF #REQUIRED
- Type CDATA #IMPLIED>
-
-<!-- ExternalLink avoids using IDREFs so you can link to a location
- not available to the SGML parser without incurring parsing errors
- -->
-
-<!ELEMENT ExternalLink - - ((%inlinechar.gp;)+)>
- <!ATTLIST ExternalLink
- Endterm CDATA #IMPLIED
- Linkend CDATA #REQUIRED
- Type CDATA #IMPLIED>
-
-<!ELEMENT FootnoteRef - O (#PCDATA)>
- <!ATTLIST FootnoteRef
- id ID #IMPLIED
- Linkend IDREF #REQUIRED
- Mark CDATA #IMPLIED>
-
-<!ELEMENT XRef - - (#PCDATA)>
- <!ATTLIST XRef
- Endterm IDREF #IMPLIED
- Linkend IDREF #REQUIRED>
-
-<!-- =================================================================
- OBJECTS -->
-
-<!ELEMENT Example - - (Title, TitleAbbrev?,
- (Screen | LiteralLayout | ProgramListing)+)>
- <!ATTLIST Example %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT ProgramListing - - ((%inlinechar.gp;)+)>
- <!ATTLIST ProgramListing %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT LiteralLayout - - ((%inlinechar.gp;)+)>
- <!ATTLIST LiteralLayout %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT Screen - - (((%inlinechar.gp;)+) | (ScreenInfo, Graphic))>
- <!ATTLIST Screen %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT ScreenInfo - - (#PCDATA)>
- <!ATTLIST ScreenInfo %commonatts; >
-
-<!-- Graphic is for in-line use or inclusion in another element.
- Graphical data can be the content of Graphic, or you
- can reference an external file through the
- Fileref attribute, either as an entity or a filename. -->
-
-<!ELEMENT Graphic - - CDATA>
- <!ATTLIST Graphic
- format NOTATION (%local.notations; | GIF | TIFF
- | CGM | DVI | EPS
- | TBL | EQN | PS
- | DITROFF | PIC) #IMPLIED
- Fileref CDATA #IMPLIED
- Entityref ENTITY #IMPLIED
- id ID #IMPLIED>
-
-<!-- N.B.: Graphic occurs in object.gp, so does not appear explicitly
- in Figure. -->
-
-<!ELEMENT Figure - - (Title, TitleAbbrev?,
- (%object.gp; | IndexTerm)*)>
- <!ATTLIST Figure id ID #IMPLIED
- Height CDATA #IMPLIED
- Width CDATA #IMPLIED
- Align (l|c|r) l
- Float (YES | NO) NO >
-
-<!ELEMENT Equation - - ((Title, TitleAbbrev?)?, Graphic)>
- <!ATTLIST Equation %commonatts; >
-
-<!-- ================================================================
- TABLE
- A simple model; you can use any other table model by making
- a local modification. -->
-
-<!ELEMENT Table - - ((Title, TitleAbbrev?)?, Graphic?,
- (TableSpec?, TableColHead*, TableRow+)?)>
- <!ATTLIST Table %commonatts;
- Number CDATA #IMPLIED >
-
-<!ELEMENT TableSpec - - (%inlinechar.gp;)>
- <!ATTLIST TableSpec %commonatts; >
-
-<!ELEMENT TableColHead - - (TableCell+)>
- <!ATTLIST TableColHead %commonatts; >
-
-<!ELEMENT TableCell - - ((Para | %inlinechar.gp;)+)>
- <!ATTLIST TableCell %commonatts; >
-
-<!ELEMENT TableRow - - (TableCell+)>
- <!ATTLIST TableRow %commonatts; >
-
-<!-- ===============================================================
- NAVIGATIONAL AND REFERENCE -->
-
-<!ELEMENT ToCentry1 - - ((%inlinechar.gp;)+, ToCentry2*)>
- <!ATTLIST ToCentry1 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT ToCentry2 - - ((%inlinechar.gp;)+, ToCentry3*)>
- <!ATTLIST ToCentry2 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT ToCentry3 - - ((%inlinechar.gp;)+, ToCentry4*)>
- <!ATTLIST ToCentry3 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT ToCentry4 - - ((%inlinechar.gp;)+, ToCentry5*)>
- <!ATTLIST ToCentry4 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT ToCentry5 - - ((%inlinechar.gp;)+)>
- <!ATTLIST ToCentry5 %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!ELEMENT GlossaryEntry - - (GlossaryTerm, GlossaryDef)>
- <!ATTLIST GlossaryEntry %commonatts; >
-
-<!ELEMENT BiblioEntry - - (TitleAbbrev?,
- (Author | CorpAuthor | OtherAuthor | Editor | Title)+,
- Subtitle?, Date?,
- Publisher?, #PCDATA)>
- <!ATTLIST BiblioEntry %commonatts; >
-
-<!-- IndexTerms appear in the text, not in the Index. -->
-
-<!ELEMENT IndexTerm - - (Primary,
- (((Secondary, (Tertiary | See | SeeAlso+)?) | See | SeeAlso+))?)>
- <!ATTLIST IndexTerm
- %commonatts;
- Span (Start|End) #IMPLIED
- Pagenum CDATA #IMPLIED>
-
-<!ELEMENT (Primary | Secondary | Tertiary ) - - ((%inlinechar.gp;
- | IndexAs)+)>
- <!ATTLIST (Primary | Secondary | Tertiary )
- %commonatts;
- HasRefEntry (Yes | No) No >
-
-<!ELEMENT IndexAs - - ((%inlinechar.gp;)+)>
- <!ATTLIST IndexAs %commonatts;>
-
-<!ELEMENT (See | SeeAlso) - - ((%inlinechar.gp;)+)>
- <!ATTLIST (See | SeeAlso)
- %commonatts;
- HasRefEntry (Yes | No) No >
-
-<!-- IndexEntries appear in the Index, not the text. -->
-
-<!ENTITY % primsee "PrimaryIE, (SeeIE | SeeAlsoIE+)*" >
-
-<!ENTITY % secsee "(SecondaryIE, ((SeeIE | SeeAlsoIE+) | TertiaryIE)*)" >
-
-<!ELEMENT IndexEntry - - (%primsee, (%secsee)*)>
-<!ATTLIST IndexEntry
- %commonatts; >
-
-<!ELEMENT PrimaryIE - - (#PCDATA)>
- <!ATTLIST PrimaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED>
-
-<!ELEMENT SecondaryIE - - (#PCDATA)>
- <!ATTLIST SecondaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED>
-
-<!ELEMENT TertiaryIE - - (#PCDATA) >
- <!ATTLIST TertiaryIE
- %commonatts;
- Linkends IDREFS #REQUIRED>
-
-<!ELEMENT SeeIE - - (#PCDATA) >
- <!ATTLIST SeeIE %commonatts;
- Linkend IDREF #REQUIRED>
-
-<!ELEMENT SeeAlsoIE - - (#PCDATA) >
- <!ATTLIST SeeAlsoIE %commonatts;
- Linkends IDREFS #REQUIRED>
-
-<!ELEMENT LoTentry - - ((%inlinechar.gp;)+ )>
- <!ATTLIST LoTentry %commonatts;
- Pagenum CDATA #IMPLIED >
-
-<!-- ==============================================================
- DOCINFO elements; some appear in BiblioEntry, too -->
-
-<!ELEMENT Author - - ((Honorific | Firstname | Surname)+) >
-
-<!ELEMENT Editor - - ((Honorific | Firstname | Surname?)+) >
-
-<!ELEMENT (AuthorInitials | BookAcronym | CorpAuthor | CorpName
- | Date | Edition
- | Firstname | Holder
- | Honorific | ISBN | InvPartNumber
- | OrgName | OtherAuthor
- | ProductName | ProductNumber
- | Publisher | ReleaseInfo
- | RevNumber | RevRemark
- | Series | Subtitle
- | Surname | Year ) - - (#PCDATA)>
-
-<!ELEMENT Copyright - - (Year+, Holder*)>
-
-<!ELEMENT LegalNotice - - ((Para | BlockQuote)+)>
-
-<!ELEMENT PrintHistory - - (Para+)>
-
-<!ELEMENT RevHistory - - (Revision*)>
-
-<!ELEMENT Revision - - (RevNumber, Date, AuthorInitials+, RevRemark)>
-
-<!ELEMENT BookTitle - - (Title, Subtitle?, TitleAbbrev?,
- ReleaseInfo?, BookAcronym?)>
-
-<!-- ==================================================================
- OTHER IN-LINE ELEMENTS -->
-
-<!ELEMENT (FunctionParam | VarParam) - - ((#PCDATA
- | Superscript | Subscript)+)>
- <!ATTLIST VarParam %commonatts; >
-
-<!ELEMENT Command - - ((%basechar.gp; | Optional | Option)+)>
-
-<!ELEMENT (Action | Filename | Function
- | Hardware | KeyCap | Interface
- | InterfaceDefinition
- | Property | ProtocolRequest
- | SystemItem) - - ((%basechar.gp; | Optional)+)>
-
-<!ELEMENT Option - - ((%basechar.gp; | Optional)+)>
-
-<!ELEMENT (ComputerOutput | Literal) - - (Anchor | #PCDATA)>
-
-<!ELEMENT (CiteBook | CiteChap | CiteSect
- | CiteRefEntry | GlossaryTerm
- | GlossaryDef | UserInput
- | Quote) - - ((%inlinechar.gp;)+)>
-
-
-<!ELEMENT Subscript - - (#PCDATA | Subscript)>
-
-<!ELEMENT Superscript - - (#PCDATA | Superscript)>
-
-<!ELEMENT (Acronym | Application | Button | Character | Charset
- | Citation | Classname | Constant
- | DbName | DbTable | DbField | DbRecord
- | Emphasis | Error
- | EventType | EventStructure | FirstTerm
- | Font | ForeignPhrase | Glyph | HWapplic
- | Icon | KeySym | KeyCode | LineAnnotation
- | Macro | Mask | Menu | MenuItem
- | OSname | Prompt
- | PubsNumber | Resource | ReturnValue
- | StructField | StructName
- | SWapplic | Symbol
- | SystemName | Token | Type
- | VolumeNumber | WordAsWord) - - (#PCDATA)>
-
-<!-- The element named Optional is for use in syntax lines, as in a
- RefEntry, where optional parameters are shown in square
- brackets. Optional should replace those brackets. -->
-
-<!ELEMENT (Optional | Trademark) - - ((%basechar.gp; | %computerterms.gp;
- | Optional)+)>
- <!ATTLIST Optional %commonatts; >
-
-<!-- ================================================================
- REFERENCE ENTRIES -->
-
-<!ELEMENT RefEntry - - (DocInfo?, RefMeta?,
- (Comment | IndexTerm)*,
- RefNameDiv,
- RefSynopsisDiv?,
- RefSect1+)>
- <!ATTLIST RefEntry %commonatts; >
-
-<!ELEMENT RefMeta - - (RefFileName, ManVolNum?, RefMiscInfo*)>
- <!ATTLIST RefMeta %commonatts; >
-
-<!ELEMENT RefFileName - - (#PCDATA)>
- <!ATTLIST RefFileName %commonatts; >
-
-<!ELEMENT ManVolNum - - (#PCDATA)>
- <!ATTLIST ManVolNum %commonatts; >
-
-<!ELEMENT RefMiscInfo - - (#PCDATA)>
- <!ATTLIST RefMiscInfo %commonatts; >
-
-<!ELEMENT RefNameDiv - - (RefDescriptor?, RefName+,
- RefPurpose, (%local.refclasses;)?,
- (Comment | IndexTerm)*)>
- <!ATTLIST RefNameDiv %commonatts; >
-
-<!ELEMENT RefDescriptor - - (#PCDATA)>
- <!ATTLIST RefDescriptor %commonatts; >
-
-<!ELEMENT RefName - - ((#PCDATA | %computerterms.gp;)+)>
- <!ATTLIST RefName %commonatts; >
-
-<!ELEMENT RefPurpose - - ((%inlinechar.gp;)+)>
- <!ATTLIST RefPurpose %commonatts; >
-
-<!-- RefClass includes local.refclasses, as they are meant to
- be subelements, not alternatives, as is the case with
- the other local.* groups -->
-
-<!ELEMENT RefClass - - ((%inlinechar.gp;)+)>
-
-<!ELEMENT RefSynopsisDiv - - ((Synopsis, RefSect2*)
- | (RefSect2+))>
- <!ATTLIST RefSynopsisDiv
- Name (Synopsis | Syntax) Synopsis >
-
-<!ELEMENT Synopsis - - ((%inlinechar.gp;)+)>
- <!ATTLIST Synopsis %commonatts;
- format NOTATION (linespecific) linespecific >
-
-<!ELEMENT RefSect1 - - (Title,
- (((%component.gp;)+, RefSect2*) | RefSect2+))>
- <!ATTLIST RefSect1 %commonatts; >
-
-<!ELEMENT RefSect2 - - (Title, (%component.gp;)+)>
- <!ATTLIST RefSect2 %commonatts; >
-
-<!-- end of the DocBook DTD -->
+++ /dev/null
- <!SGML "ISO 8879:1986"
-
- CHARSET
-
- BASESET "ISO 646:1983//CHARSET
- International Reference Version (IRV)//ESC 2/5 4/0"
- DESCSET 0 9 UNUSED
- 9 2 9
- 11 2 UNUSED
- 13 1 13
- 14 18 UNUSED
- 32 95 32
- 127 1 UNUSED
-
- BASESET "ISO Registration Number 100//CHARSET
- ECMA-94 Right Part of Latin Alphabet Nr. 1//ESC 2/13 4/1"
- DESCSET 128 32 UNUSED
- 160 5 32
- 165 1 UNUSED
- 166 88 38
- 254 1 127
- 255 1 UNUSED
-
-
- CAPACITY SGMLREF
-
- TOTALCAP 4000000
- ATTCAP 256000
- AVGRPCAP 256000
- ENTCAP 300000
- ENTCHCAP 350000
- GRPCAP 300000
- IDCAP 2000000
-
- SCOPE DOCUMENT
-
- SYNTAX
-
- SHUNCHAR CONTROLS 0 1 2 3 4 5 6 7 8 9
- 10 11 12 13 14 15 16 17 18 19
- 20 21 22 23 24 25 26 27 28 29
- 30 31 127 255
-
- BASESET "ISO 646:1983//CHARSET
- International Reference Version (IRV)//ESC 2/5 4/0"
- DESCSET 0 128 0
-
- FUNCTION RE 13
- RS 10
- SPACE 32
- TAB SEPCHAR 9
-
- NAMING LCNMSTRT ""
- UCNMSTRT ""
- LCNMCHAR ".-"
- UCNMCHAR ".-"
- NAMECASE GENERAL YES
- ENTITY NO
-
- DELIM GENERAL SGMLREF
- SHORTREF SGMLREF
-
- NAMES SGMLREF
-
- QUANTITY SGMLREF
- ATTCNT 256
- GRPCNT 253
- GRPGTCNT 253
- LITLEN 8092
- NAMELEN 44
- TAGLVL 100
-
- FEATURES
- MINIMIZE
- DATATAG NO
- OMITTAG NO
- RANK NO
- --
- While SHORTTAG is set to YES to accomodate FIXED attribute
- values, the use of short tagging in instances is deprecated
- --
- SHORTTAG YES
-
- LINK
- SIMPLE NO
- IMPLICIT NO
- EXPLICIT NO
-
- OTHER
- CONCUR NO
- SUBDOC NO
- FORMAL NO
-
- APPINFO
- NONE
->
-
-<!--
- Reference Concrete Syntax modifications for the DocBook DTD,
- $Revision$
- -->
-
+++ /dev/null
-<DOCBOOK>
-<DOCINFO><BOOKTITLE><TITLE>X Window System User's Guide</TITLE>
-</BOOKTITLE></DOCINFO>
-<REFENTRY ID="RE-1015-XLSCLIENTS-1">
-<REFMETA>
-<REFFILENAME>xlsclients</REFFILENAME>
-<REFMISCINFO>List Running Clients</REFMISCINFO></REFMETA>
-<INDEXTERM ID="IX-1015-XLSCLIENTS-1" SPAN="START"><PRIMARY>xlsclients (list running clients)</PRIMARY><SECONDARY>reference page for</SECONDARY></INDEXTERM>
-<REFNAMEDIV ID="RN-1015-XLSCLIENTS-1"><REFNAME>xlsclients</REFNAME>
-<REFPURPOSE>list client applications running on a display.</REFPURPOSE>
-</REFNAMEDIV>
-<REFSYNOPSISDIV NAME="Syntax"><SYNOPSIS><USERINPUT>xlsclients <OPTIONAL><VARPARAM>options</VARPARAM></OPTIONAL></USERINPUT>
-</SYNOPSIS></REFSYNOPSISDIV>
-<REFSECT1 ID="R1-1015-XLSCLIENTS-1"><TITLE>Description</TITLE>
-<PARA><COMMAND>xlsclients</COMMAND>
-is a utility for listing information about the client applications
-running on a display. It may be used to generate scripts representing
-a snapshot of the user's current session.
-Note, however, that <COMMAND>xlsclients</COMMAND> will not list a window manager
-process. See &cmtf08;, for more information.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-1015-XLSCLIENTS-2"><TITLE>Options</TITLE>
-<PARA><COMMAND>xlsclients</COMMAND> accepts the following options:
-</PARA>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM><OPTION>-a</OPTION></TERM>
-<LISTITEM>
-<PARA>Specifies that clients on all screens should be listed. By
-default, only those clients on the default screen are listed.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY>
-<TERM><OPTION>-display[</OPTION><VARPARAM>host</VARPARAM><LITERAL>:</LITERAL><VARPARAM>server</VARPARAM>[<LITERAL>.</LITERAL><VARPARAM>screen</VARPARAM>]</TERM>
-<LISTITEM>
-<PARA>Allows you to specify the display, server, and screen to connect to.
-<VARPARAM>host</VARPARAM> is the hostname of the physical display,
-<VARPARAM>server</VARPARAM> specifies the server number, and <VARPARAM>screen</VARPARAM> specifies
-the screen number. For example,
-</PARA>
-<SCREEN ID="SC-1015-XLSCLIENTS-1"><PROMPT>%</PROMPT> <USERINPUT>xlsclients -display <VARPARAM>your_node</VARPARAM>:0.10</USERINPUT>
-</SCREEN>
-<PARA>specifies screen 1 of server 0 on the display named by <VARPARAM>your_node</VARPARAM>.
-Either or both the <VARPARAM>host</VARPARAM> and <VARPARAM>screen</VARPARAM>
-can be omitted. If <VARPARAM>host</VARPARAM>
-is omitted, the local display is assumed. If <VARPARAM>screen</VARPARAM> is omitted,
-screen 0 is assumed (and the period is unnecessary).
-The colon and <VARPARAM>server</VARPARAM> are necessary in all cases.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY>
-<TERM><OPTION>-l</OPTION></TERM>
-<LISTITEM>
-<PARA>Requests a long listing showing the window name, icon name,
-and class hints in addition to the machine name and command string in
-the default listing.
-</PARA></LISTITEM></VARLISTENTRY>
-<VARLISTENTRY>
-<TERM><OPTION>-m</OPTION><VARPARAM>max_cmd_length</VARPARAM></TERM>
-<LISTITEM>
-<PARA>Specifies the maximum number of characters in a command to
-list. The default is 10000.
-</PARA></LISTITEM>
-</VARLISTENTRY></VARIABLELIST>
-</REFSECT1>
-<REFSECT1 ID="R1-1015-XLSCLIENTS-3"><TITLE>See Also</TITLE>
-<PARA>X, xprop, xwininfo; &cmtf08;.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-1015-XLSCLIENTS-4"><TITLE>Author</TITLE>
-<PARA>Jim Fulton, MIT X Consortium.
-<INDEXTERM ID="IX-1015-XLSCLIENTS-2" SPAN="END"><PRIMARY>xlsclients (list running clients)</PRIMARY><SECONDARY>reference page for</SECONDARY></INDEXTERM>
-</PARA>
-</REFSECT1></REFENTRY></DOCBOOK>
projects / docbook-dsssl / commitdiff