aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Terriberry <tterribe@xiph.org>2016-07-22 20:16:14 +0000
committerTim Terriberry <tterribe@xiph.org>2016-07-22 20:16:14 +0000
commit786f14951fc43648265233ab52a045b9e32d8470 (patch)
treeac4c6453d10c714ca1f4416af8c86f8af4d6b757
parent1bca48e69de420c5e9e8f1a788fdc81d81ae3b78 (diff)
downloadlibvorbis-upstream-mirror.tar.gz
Add ids to v-comment.htmlupstream-mirror
This allows linking to specific sections. Patch from Christian Weiske <cweiske@cweiske.de>. git-svn-id: http://svn.xiph.org/trunk/vorbis@19572 0101bb08-14d6-0310-b084-bc0e0c8e3800
-rw-r--r--doc/v-comment.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/v-comment.html b/doc/v-comment.html
index 4b64d27..aad5e88 100644
--- a/doc/v-comment.html
+++ b/doc/v-comment.html
@@ -72,7 +72,7 @@ li {
<h1>Ogg Vorbis I format specification: comment field and header specification</h1>
-<h1>Overview</h1>
+<h1 id="overview">Overview</h1>
<p>The Vorbis text comment header is the second (of three) header
packets that begin a Vorbis bitstream. It is meant for short, text
@@ -92,9 +92,9 @@ they turn out to be, eg:</p>
opening for Moxy Fr&uuml;vous, 1997"
</p></blockquote>
-<h1>Comment encoding</h1>
+<h1 id="commentencoding">Comment encoding</h1>
-<h2>Structure</h2>
+<h2 id="structure">Structure</h2>
<p>The comment header logically is a list of eight-bit-clean vectors; the
number of vectors is bounded to 2^32-1 and the length of each vector
@@ -122,7 +122,7 @@ set the vendor string to "Xiph.Org libVorbis I 20020717".</p>
9) done.
</pre>
-<h2>Content vector format</h2>
+<h2 id="vectorformat">Content vector format</h2>
<p>The comment vectors are structured similarly to a UNIX environment variable.
That is, comment fields consist of a field name and a corresponding value and
@@ -144,7 +144,7 @@ this equals sign is used to terminate the field name.</li>
field contents to the end of the field.</li>
</ul>
-<h3>Field names</h3>
+<h3 id="fieldnames">Field names</h3>
<p>Below is a proposed, minimal list of standard field names with a
description of intended use. No single or group of field names is
@@ -216,7 +216,7 @@ ISRC intro page</a> for more information on ISRC numbers.</dd>
</dl>
-<h3>Implications</h3>
+<h3 id="implications">Implications</h3>
<ul>
<li>Field names should not be 'internationalized'; this is a
@@ -244,7 +244,7 @@ well know artists; the following is permissible, and encouraged:
</pre></li>
</ul>
-<h2>Encoding</h2>
+<h2 id="encoding">Encoding</h2>
<p>The comment header comprises the entirety of the second bitstream
header packet. Unlike the first bitstream header packet, it is not