<s1>...<s9>
Subsection (<s1>, <s2>, ... , <s9>): Starts a topic in the hierarchy.
Syntax
<sn [id=name]>heading topic text...
Where n is the level number (1, 2,..., or 9).
Topics entered with <chapter> can have subtopics entered with <s1>, <s1> topics can have <s2> subtopics, and so on. You cannot skip a level.
The heading for a section can be on the same line as the <sn> tag or on the next line; a heading is required. Text within a section is optional.
The end tag is usually omitted, but in some instances the end tag may be necessary. For example, when a section is followed by an <rsect> element that is on the same level, an end tag for the section is required. Without the end tag, the <rsect> element would be considered a subsection of the section preceding it.
Examples
-
The following illustrates a three-level hierarchy within a topic.
<chapter>Running the Processor topic text... <s1>Getting Started To run the program, type in the usercode and your password. <s1>Customizing You may now set up this conversion program to change your computer from beige to red. <s2>Configuration Use either the disk drive or the tape drive to archive your files. <s3>Disk Drive Advantages See data sheet for specifications. <s3>Tape Drive Advantages See data sheet for specifications. <s2>Support If you really need help, call technical support.
-
In the following markup, a section end tag (<\s1>) is used to make the <rsect> section be at the same level in the hierarchy.
<s1>first-level heading text <s1>first-level heading text <\s1> <rsect>first-level heading text In contrast, leaving out the end tag causes the <rsect> section to become a subtopic of the second <s1> section: <s1>first-level heading text <s1>first-level heading text <rsect>second- level heading text
See Also
- © 2010, Oracle Corporation and/or its affiliates