Level sections

A level section command specifies the section header for HTML as well as the section level. The command should be followed by the section heading followed by a full-stop. The full-stop will be omitted from the heading when it is formatted by weav. The heading will appear both in the table of contents and as a running-header at the top of each page containing part of that section or sub-section so you should be careful about what to put into such a header.

The following table shows the Web 68 code in the first column and the code output by weav in the second column:-

Web 68 code Output HTML code
@1Heading 1. <h1>Heading 1</h1>
@2Heading 2. <h2>Heading 2</h2>
@3Heading 3. <h3>Heading 3</h3>

The text for the section should follow on the next line, not preceded by any spaces.

For example:-

@1 Introduction.
This program ...

Level sections introduce major parts of the program. Level 1 sections are disallowed in included files to ensure the integrity of the indexes output by weav.

When tang and weav meet a level sectioning command, they both output the current section to the console in the form

[section.subsection.subsubsection.paragraph]
unless the current file is an included file when the current section will appear as
[Ifile number.subsection.subsubsection.paragraph]
So the second subsection of the third section will appear on the console as [3.2.1.1].

Sian Mountbatten 2012-01-05