|
| |
Basic Markup Tags Paragraph Tag <>
 | Unlike word processors, carriage returns in HTML files aren't significant.
|
| Multiple spaces are collapsed into one
|
| You must separate paragraphs with <>. The browser ignores any indentations or blank lines in the source text.
|
| HTML relies almost entirely on the tags for formatting instructions
 | NCSA Mosaic handles <> by ending the current paragraph and inserting a blank line. | |
Notes:
Unlike documents in most word processors, carriage returns in HTML files aren't significant. Word wrapping can occur at any point in your source file, and multiple spaces are collapsed into a single space. (There are couple of exceptions; space following a <> or <> tag, for example, is ignored.) Notice that in the bare-bones example, the first paragraph is coded as
This is the first paragraph. <>
In the source file, there is a line break between the sentences. A Web browser ignores this line break and starts a new paragraph only when it reaches a <> tag.
Important: You must separate paragraphs with <>. The browser ignores any indentations or blank lines in the source text. HTML relies almost entirely on the tags for formatting instructions, and without the <> tags, the document becomes one large paragraph. (The exception is text tagged as ``preformatted,'' which is explained below.) For instance, the following would produce identical output as the first bare-bones HTML example:
<> simplest HTML example</TITLE><> is a level
one heading</H1> to the world of HTML. This is one
paragraph.<> this is a second.<>
However, to preserve readability in HTML files, headings should be on separate lines, and paragraphs should be separated by blank lines (in addition to the <> tags).
NCSA Mosaic handles <> by ending the current paragraph and inserting a blank line.
In HTML+, a successor to HTML currently in development, <> becomes a ``container'' of text.
|
