Whitespace-only fixes. Translators, please ignore.
This commit is contained in:
Warren Block
parent
fa7c4cfd5c
commit
9ff3abbffa
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=42275
1 changed files with 58 additions and 49 deletions
|
|
@ -91,8 +91,8 @@
|
|||
<para>There are a number of <acronym>XHTML</acronym>
|
||||
<acronym>FPI</acronym>s, depending upon the version, or
|
||||
<emphasis>level</emphasis> of <acronym>XHTML</acronym> to which
|
||||
a document conforms. Most <acronym>XHTML</acronym> documents on the FreeBSD web
|
||||
site comply with the transitional version of
|
||||
a document conforms. Most <acronym>XHTML</acronym> documents on
|
||||
the FreeBSD web site comply with the transitional version of
|
||||
<acronym>XHTML</acronym> 1.0.</para>
|
||||
|
||||
<programlisting>PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"</programlisting>
|
||||
|
|
@ -173,8 +173,8 @@
|
|||
<para>Generally, an <acronym>XHTML</acronym> page should have
|
||||
one first level heading (<sgmltag>h1</sgmltag>). This can
|
||||
contain many second level headings (<sgmltag>h2</sgmltag>),
|
||||
which can in turn contain many third level headings.
|
||||
Do not leave gaps in the numbering.</para>
|
||||
which can in turn contain many third level headings. Do not
|
||||
leave gaps in the numbering.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="xhtml-markup-block-elements-paragraphs">
|
||||
|
|
@ -197,8 +197,7 @@
|
|||
<title>Block Quotations</title>
|
||||
|
||||
<para>A block quotation is an extended quotation from another
|
||||
document that will appear in a separate
|
||||
paragraph.</para>
|
||||
document that will appear in a separate paragraph.</para>
|
||||
|
||||
<example>
|
||||
<title><sgmltag>blockquote</sgmltag></title>
|
||||
|
|
@ -222,11 +221,11 @@
|
|||
<para><acronym>XHTML</acronym> can present the user with three
|
||||
types of lists: ordered, unordered, and definition.</para>
|
||||
|
||||
<para>Entries in an ordered list will be
|
||||
numbered, while entries in an unordered list will be
|
||||
preceded by bullet points. Definition lists have
|
||||
two sections for each entry. The first section is the term
|
||||
being defined, and the second section is the definition.</para>
|
||||
<para>Entries in an ordered list will be numbered, while entries
|
||||
in an unordered list will be preceded by bullet points.
|
||||
Definition lists have two sections for each entry. The first
|
||||
section is the term being defined, and the second section is
|
||||
the definition.</para>
|
||||
|
||||
<para>Ordered lists are indicated by the <sgmltag>ol</sgmltag>
|
||||
element, unordered lists by the <sgmltag>ul</sgmltag>
|
||||
|
|
@ -303,13 +302,13 @@
|
|||
<sect2 id="xhtml-markup-block-elements-preformatted-text">
|
||||
<title>Pre-formatted Text</title>
|
||||
|
||||
<para>Pre-formatted text is shown to the user exactly as it
|
||||
is in the file. Text is shown in a fixed font.
|
||||
Multiple spaces and line breaks are shown exactly as they are
|
||||
in the file.</para>
|
||||
<para>Pre-formatted text is shown to the user exactly as it is
|
||||
in the file. Text is shown in a fixed font. Multiple spaces
|
||||
and line breaks are shown exactly as they are in the
|
||||
file.</para>
|
||||
|
||||
<para>Wrap pre-formatted text in the
|
||||
<sgmltag>pre</sgmltag> element.</para>
|
||||
<para>Wrap pre-formatted text in the <sgmltag>pre</sgmltag>
|
||||
element.</para>
|
||||
|
||||
<example>
|
||||
<title><sgmltag>pre</sgmltag></title>
|
||||
|
|
@ -376,13 +375,14 @@
|
|||
<sgmltag class="endtag">table</sgmltag></programlisting>
|
||||
</example>
|
||||
|
||||
<para>A cell can span multiple rows and columns by adding
|
||||
the <sgmltag class="attribute">rowspan</sgmltag> or
|
||||
<sgmltag class="attribute">colspan</sgmltag> attributes with values for
|
||||
the number of rows or columns to be spanned.</para>
|
||||
<para>A cell can span multiple rows and columns by adding the
|
||||
<sgmltag class="attribute">rowspan</sgmltag> or
|
||||
<sgmltag class="attribute">colspan</sgmltag> attributes with
|
||||
values for the number of rows or columns to be spanned.</para>
|
||||
|
||||
<example>
|
||||
<title>Using <sgmltag class="attribute">rowspan</sgmltag></title>
|
||||
<title>Using
|
||||
<sgmltag class="attribute">rowspan</sgmltag></title>
|
||||
|
||||
<para>Usage:</para>
|
||||
|
||||
|
|
@ -403,7 +403,8 @@
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Using <sgmltag class="attribute">colspan</sgmltag></title>
|
||||
<title>Using
|
||||
<sgmltag class="attribute">colspan</sgmltag></title>
|
||||
|
||||
<para>Usage:</para>
|
||||
|
||||
|
|
@ -424,7 +425,8 @@
|
|||
|
||||
<example>
|
||||
<title>Using <sgmltag class="attribute">rowspan</sgmltag> and
|
||||
<sgmltag class="attribute">colspan</sgmltag> Together</title>
|
||||
<sgmltag class="attribute">colspan</sgmltag>
|
||||
Together</title>
|
||||
|
||||
<para>Usage:</para>
|
||||
|
||||
|
|
@ -466,14 +468,14 @@
|
|||
|
||||
<para>Two levels of emphasis are available in
|
||||
<acronym>XHTML</acronym>, <sgmltag>em</sgmltag> and
|
||||
<sgmltag>strong</sgmltag>. <sgmltag>em</sgmltag> is for a
|
||||
<sgmltag>strong</sgmltag>. <sgmltag>em</sgmltag> is for a
|
||||
normal level of emphasis and <sgmltag>strong</sgmltag>
|
||||
indicates stronger emphasis.</para>
|
||||
|
||||
<para><sgmltag>em</sgmltag> is typically rendered in italic
|
||||
and <sgmltag>strong</sgmltag> is rendered in bold. This is
|
||||
not always the case, and should not be relied upon.
|
||||
According to best practices, web pages only hold structural and
|
||||
not always the case, and should not be relied upon. According
|
||||
to best practices, web pages only hold structural and
|
||||
semantical information, and stylesheets are later applied to
|
||||
them. Think of semantics, not formatting, when using these
|
||||
tags.</para>
|
||||
|
|
@ -518,14 +520,16 @@
|
|||
|
||||
<para>A link points to the <acronym>URL</acronym> of a
|
||||
document on the web. The link is indicated with
|
||||
<sgmltag>a</sgmltag>, and the <sgmltag class="attribute">href</sgmltag>
|
||||
attribute contains the <acronym>URL</acronym> of the target
|
||||
document. The content of the element becomes the link,
|
||||
indicated to the user by showing it in
|
||||
a different color or with an underline.</para>
|
||||
<sgmltag>a</sgmltag>, and the
|
||||
<sgmltag class="attribute">href</sgmltag> attribute contains
|
||||
the <acronym>URL</acronym> of the target document. The
|
||||
content of the element becomes the link, indicated to the
|
||||
user by showing it in a different color or with an
|
||||
underline.</para>
|
||||
|
||||
<example>
|
||||
<title>Using <sgmltag class="starttag">a href="..."</sgmltag></title>
|
||||
<title>Using
|
||||
<sgmltag class="starttag">a href="..."</sgmltag></title>
|
||||
|
||||
<para>Usage:</para>
|
||||
|
||||
|
|
@ -541,11 +545,13 @@
|
|||
<title>Linking to Specific Parts of Documents</title>
|
||||
|
||||
<para>To link to a specific point within a document, that
|
||||
document must include an
|
||||
<emphasis>anchor</emphasis> at the desired point. Anchors are included by setting the
|
||||
<sgmltag class="attribute">id</sgmltag> attribute of an element to a name.
|
||||
This example creates an anchor by setting the <sgmltag class="attribute">id</sgmltag> attribute
|
||||
of a <sgmltag class="element">p</sgmltag> element.</para>
|
||||
document must include an <emphasis>anchor</emphasis> at the
|
||||
desired point. Anchors are included by setting the
|
||||
<sgmltag class="attribute">id</sgmltag> attribute of an
|
||||
element to a name. This example creates an anchor by
|
||||
setting the <sgmltag class="attribute">id</sgmltag>
|
||||
attribute of a <sgmltag class="element">p</sgmltag>
|
||||
element.</para>
|
||||
|
||||
<example>
|
||||
<title>Creating an Anchor</title>
|
||||
|
|
@ -556,26 +562,29 @@
|
|||
in other links with the name <sgmltag class="starttag">tt</sgmltag>samplepara<sgmltag class="endtag">tt</sgmltag>.<sgmltag class="endtag">p</sgmltag></programlisting>
|
||||
</example>
|
||||
|
||||
<para>Links to anchors are similar to plain links,
|
||||
but include a <literal>#</literal> symbol and the anchor's <acronym>ID</acronym>
|
||||
at the end of the <acronym>URL</acronym>.</para>
|
||||
<para>Links to anchors are similar to plain links, but include
|
||||
a <literal>#</literal> symbol and the anchor's
|
||||
<acronym>ID</acronym> at the end of the
|
||||
<acronym>URL</acronym>.</para>
|
||||
|
||||
<example>
|
||||
<title>Linking to a Named Part of a Different Document</title>
|
||||
<title>Linking to a Named Part of a Different
|
||||
Document</title>
|
||||
|
||||
<para>The <literal>samplepara</literal> example
|
||||
is part of a document called
|
||||
<filename>foo.html</filename>. A link to that specific
|
||||
paragraph in the document is constructed in this example.</para>
|
||||
<para>The <literal>samplepara</literal> example is part of a
|
||||
document called <filename>foo.html</filename>. A link to
|
||||
that specific paragraph in the document is constructed in
|
||||
this example.</para>
|
||||
|
||||
<programlisting><sgmltag class="starttag">p</sgmltag>More information can be found in the
|
||||
<sgmltag class="starttag">a href="foo.html#samplepara"</sgmltag>sample paragraph<sgmltag class="endtag">a</sgmltag> of
|
||||
<sgmltag class="starttag">tt</sgmltag>foo.html<sgmltag class="endtag">tt</sgmltag>.<sgmltag class="endtag">p</sgmltag></programlisting>
|
||||
</example>
|
||||
|
||||
<para>To link to a named anchor within the same
|
||||
document, omit the document's <acronym>URL</acronym>, and just
|
||||
use the <literal>#</literal> symbol followed by the name of the anchor.</para>
|
||||
<para>To link to a named anchor within the same document, omit
|
||||
the document's <acronym>URL</acronym>, and just use the
|
||||
<literal>#</literal> symbol followed by the name of the
|
||||
anchor.</para>
|
||||
|
||||
<example>
|
||||
<title>Linking to a Named Part of the Same Document</title>
|
||||
|
|
|
|||
Loading…
Reference in a new issue