Author: robux4
Date: 2004-11-11 20:39:02 +0300 (Thu, 11 Nov 2004)
New Revision: 781
Modified:
trunk/www.matroska.org/data/contact/index.html.en
trunk/www.matroska.org/data/contact/index.html.ru
trunk/www.matroska.org/data/team/svn.html
trunk/www.matroska.org/data/team/todo.html
trunk/www.matroska.org/data/technical/menu/index.html
trunk/www.matroska.org/data/technical/specs/channelposition/index.html
trunk/www.matroska.org/data/technical/specs/chapters/index.html
trunk/www.matroska.org/data/technical/specs/index.html
trunk/www.matroska.org/data/technical/specs/notes.html
trunk/www.matroska.org/data/technical/specs/profiles/index.html
trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html
trunk/www.matroska.org/data/technical/specs/tagging/example-video.html
trunk/www.matroska.org/data/technical/specs/tagging/index.html
Log:
content: name="" to id=""
Modified: trunk/www.matroska.org/data/contact/index.html.en
===================================================================
--- trunk/www.matroska.org/data/contact/index.html.en 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/contact/index.html.en 2004-11-11 17:39:02 UTC (rev 781)
@@ -40,13 +40,13 @@
have some other contribution to the project or if you plan to support
<em><strong>matroska</strong></em> in your video encoding/editing software,
here is how to talk to us:</p>
- <p><font size="+1"><strong><a name="ml"/>Mailing Lists:</strong></font></p>
+ <p id="ml"><font size="+1"><strong>Mailing Lists:</strong></font></p>
<p><em><strong>matroska</strong></em> User ML: <a href="mailto:[email protected]">[email protected]</a></p>
<p><em><strong>matroska</strong></em> General ML: <a href="mailto:[email protected]">[email protected]</a></p>
<p> <em><strong>matroska</strong></em> Development ML: <a href="mailto:[email protected]">[email protected]</a></p>
<p><em><strong>matroska</strong></em> CVS ML: <a href="mailto:[email protected]">[email protected]</a></p>
<p>To subscribe to these mailing lists go here: <a href="http://lists.matroska.org/cgi-bin/mailman/listinfo">http://lists.matroska.org/cgi-bin/mailman/listinfo</a></p>
- <p><font size="+1"><strong><a name="usenet"/>UseNet:</strong></font></p>
+ <p id="usenet"><font size="+1"><strong>UseNet:</strong></font></p>
<p>All <em><strong>matroska</strong></em> Mailing lists are accessible
(read and reply) via the mail to <strong>NNTP</strong><br/>
interface of <a href="http://www.gmane.org">gmane.org</a> also:</p>
@@ -55,7 +55,7 @@
add <em><strong>news.gmane.org</strong></em> as newsserver manually in
your newsreader setup)</p>
<p><em><strong>matroska</strong></em> groups are: <em><strong>gmane.comp.multimedia.matroska.xxxxx</strong></em></p>
- <p><font size="+1"><strong><a name="irc"/>IRC:</strong></font></p>
+ <p id="irc"><font size="+1"><strong>IRC:</strong></font></p>
<p>Our developers meet on an IRC channel on <a href="irc://irc.corecodec.com:6667/matroska">irc.corecodec.com</a>
, channel #matroska</p>
<p>IRC clients for Microsoft (TM) Windows (TM) are to be found <a href="http://www.mirc.com">here</a>,
@@ -63,7 +63,7 @@
for Linux BitchX and <a href="http://www.xchat.org">X-chat</a> can be used, latter
is available for Windows (TM)<br/>
and MacOS-X (TM) also.</p>
- <p><font size="+1"><strong><a name="email"/>Email:</strong></font></p>
+ <p id="email"><font size="+1"><strong>Email:</strong></font></p>
<p>If you have any comments on the site please drop me a mail to chris at
matroska.org</p>
<!-- InstanceEndEditable -->
Modified: trunk/www.matroska.org/data/contact/index.html.ru
===================================================================
--- trunk/www.matroska.org/data/contact/index.html.ru 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/contact/index.html.ru 2004-11-11 17:39:02 UTC (rev 781)
@@ -39,13 +39,13 @@
желаете как-то иначе помочь проекту,<br/> или собираетесь встроить поддержку
<em><strong>matroska</strong></em> в ваших приложениях сжатия/редактирования видео,
вот способы связаться с нами:</p>
- <p><font size="+1"><strong><a name="ml"/>Рассылки:</strong></font></p>
+ <p id="ml"><font size="+1"><strong>Рассылки:</strong></font></p>
<p>Рассылка пользователей: <a href="mailto:[email protected]">[email protected]</a></p>
<p>Общая рассылка: <a href="mailto:[email protected]">[email protected]</a></p>
<p>Рассылка разработчиков: <a href="mailto:[email protected]">[email protected]</a></p>
<p>Рассылка обновлений CVS: <a href="mailto:[email protected]">[email protected]</a></p>
<p>Подписаться на эти e-mail рассылки можно здесь: <a href="http://lists.matroska.org/cgi-bin/mailman/listinfo">http://lists.matroska.org/cgi-bin/mailman/listinfo</a></p>
- <p><font size="+1"><strong><a name="usenet"/>Usenet</strong></font></p>
+ <p id="usenet"><font size="+1"><strong>Usenet</strong></font></p>
<p>Все рассылки проекта <em><strong>matroska</strong></em> также доступны
(для чтения и ответов) через <br/>e-mail to <strong>NNTP</strong>
гейт на <a href="http://www.gmane.org/">gmane.org</a> по адресу:</p>
@@ -53,12 +53,12 @@
не работает, попробуйте вручную<br/>
добавить сервер новостей <em><strong>news.gmane.org</strong></em> в настройках вашей программы чтения новостей)</p>
<p>Группы новостей проекта <em><strong>matroska</strong></em>: <em><strong>gmane.comp.multimedia.matroska.xxxxx</strong></em></p>
- <p><font size="+1"><strong><a name="irc"/>IRC:</strong></font></p>
+ <p id="irc"><font size="+1"><strong>IRC:</strong></font></p>
<p>Наши разработчики собираются на канале #matroska IRC сервера <a href="irc://irc.corecodec.com:6667/matroska">irc.corecodec.com</a>.</p>
<p>IRC клиенты под ОС Microsoft (TM) Windows (TM) вы можете найти <a href="http://www.mirc.com/">здесь</a>,
<a href="http://www.mozilla.org/">здесь</a>, и <a href="http://www.trillian.cc/">здесь</a>,<br/>
под ОС Linux можно использовать BitchX и <a href="http://www.xchat.org">X-chat</a>, последний также существует в версиях под Windows (TM) и MacOS-X (TM).</p>
- <p><font size="+1"><strong><a name="email"/>Email:</strong></font></p>
+ <p id="email"><font size="+1"><strong>Email:</strong></font></p>
<p>Если у вас есть какие-либо пожелания или предложения относительно этого сайта, напишите мне по адресу chris (at)
matroska.org</p>
Modified: trunk/www.matroska.org/data/team/svn.html
===================================================================
--- trunk/www.matroska.org/data/team/svn.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/team/svn.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -25,7 +25,7 @@
</div>
<div id="content">
-<h2><a name="libs">Source Code</a></h2>
+<h2 id="source">Source Code</h2>
<p>There are many ways to get access to the source code. As a 3rd party developper (user) you can download <a href="http://dl.matroska.org/downloads/libmatroska/">libmatroska</a> and <a href="http://dl.matroska.org/downloads/libebml/">libebml</a> from there official location in .tar.bz2 format.</p>
@@ -43,7 +43,7 @@
<p>You can also browse the source code using our integrated <a href="http://svn.matroska.org/viewsvn/">ViewCVS</a> or <a href="http://svn.matroska.org/svn/matroska/">Subversion</a> tools.</p>
-<h2><a name="libs">Website</a></h2>
+<h2 id="website">Website</h2>
<p>If you want to participate to the website maintainance/enhancement, you should <a href="../contact/index.html">request</a> a web developer access. And then you just checkout the SVN source code with the following command:</p>
<pre>
@@ -54,7 +54,7 @@
<p>You can also browse the source code using our integrated <a href="http://svn.matroska.org/viewsvn/?root=www">ViewCVS</a> or <a href="http://svn.matroska.org/svn/www/">Subversion</a> tools.</p>
-<h2><a name="libs">Internal Access</a></h2>
+<h2 id="internal">Internal Access</h2>
<p>And any user with an SVN access can modify his/her password on <a href="https://svn.matroska.org/my/">their page</a>.</p>
Modified: trunk/www.matroska.org/data/team/todo.html
===================================================================
--- trunk/www.matroska.org/data/team/todo.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/team/todo.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -27,7 +27,7 @@
<p id="define"><acronym class="time" title="1-fast / 5-long">duration</acronym><acronym class="ease" title="1-easy / 5-complicated">ease</acronym><acronym class="assign" title="person assigned with this task">assigned</acronym></p>
<div id="content">
-<h2><a name="libs">Specifications</a></h2>
+<h2 id="specs">Specifications</h2>
<ul>
<li><span class="time">5</span><span class="ease">3</span>make a <a href="http://www.docbook.org/">DocBook</a> out of the specs, with details about each element.</li>
@@ -38,7 +38,7 @@
</ul>
-<h2><a name="libs">libebml/libmatroska</a></h2>
+<h2 id="libs">libebml/libmatroska</h2>
<ul>
<li><span class="time">0</span><span class="ease">0</span>add support for tags in the library (at least contain the list of official ones and their type checking). Including i18n names for each tags (optionally depends on intl/iconv).</li>
@@ -47,10 +47,10 @@
-<h2><a name="DirectShow">DirectShow</a></h2>
+<h2 id="DirectShow">DirectShow</h2>
-<h3><a name="MatroskaSplitter">MatroskaSplitter</a></h3>
+<h3 id="MatroskaSplitter">MatroskaSplitter</h3>
<ul>
<li><span class="time">0</span><span class="ease">0</span>MatroskaSplitter output mediatype for mpeg1-layer2 is not complete, the Microsoft decoder doesn't want to connect.</li>
@@ -59,7 +59,7 @@
</ul>
-<h3><a name="MatroskaMuxer">MatroskaMuxer</a></h3>
+<h3 id="MatroskaMuxer">MatroskaMuxer</h3>
<ul>
<li><span class="time">0</span><span class="ease">0</span>MatroskaMuxer use some reference with audio stream ( <a href="http://forum.doom9.org/showthread.php?s=&postid=514437#post514437" class="external">http://forum.doom9.org/showthread.php?s=&postid=514437#post514437</a> )</li>
@@ -67,7 +67,7 @@
-<h3><a name="VSFilter">VSFilter</a></h3>
+<h3 id="VSFilter">VSFilter</h3>
<ul>
<li><span class="time">0</span><span class="ease">0</span>VSFilter doesn't respect the default flag (select the default track, hide all subtitles when no default track)</li>
@@ -76,13 +76,13 @@
-<h3><a name="Unverified">Unverified</a></h3>
+<h3 id="Unverified">Unverified</h3>
<ul>
<li><span class="time">0</span><span class="ease">0</span>When using embedded SSA/ASS style name with accent are b0rked and not displayed correctly.</li>
</ul>
-<h2><a name="Matroska_Shell_Extension">Matroska Shell Extension</a></h2>
+<h2 id="Matroska_Shell_Extension">Matroska Shell Extension</h2>
<ul>
<li><span class="time">0</span><span class="ease">0</span>writes b0rked tags</li>
@@ -93,7 +93,7 @@
-<h2><a name="Winamp">Winamp</a></h2>
+<h2 id="Winamp">Winamp</h2>
<ul>
<li><span class="time">0</span><span class="ease">0</span>basic support for .mka files in Winamp, probably using DirectShow for codecs</li>
@@ -101,11 +101,11 @@
-<h2><a name="AVI_mux_GUI">AVI mux GUI</a></h2>
+<h2 id="AVI_mux_GUI">AVI mux GUI</h2>
-<h2><a name="Tags">Tags</a></h2>
+<h2 id="Tags">Tags</h2>
<ul>
<li><span class="time">0</span><span class="ease">0</span>some <a href="http://www.hydrogenaudio.org/index.php?showtopic=20459&st=25&" class="external">pending issues</a> should be revolved</li>
@@ -118,13 +118,13 @@
-<h2><a name="Native_MPEG4_with_B_frames">Native MPEG4 with B frames</a></h2>
+<h2 id="Native_MPEG4_with_B_frames">Native MPEG4 with B frames</h2>
<p><span class="time">0</span><span class="ease">0</span>Apparently mkvmerge is close to be able to mux native MPEG4. So it would be nice to finish this and add support in the different players (DirectShow, VLC, MPlayer).</p>
-<h2><a name="Native_MPEG12">Native MPEG1/2</a></h2>
+<h2 id="Native_MPEG12">Native MPEG1/2</h2>
<p><span class="time">0</span><span class="ease">0</span>Spyder worked on something that was almost usable but it was never finished and used. So I don't think we are far but it should be done in a <strong>usable way</strong>.</p>
@@ -134,13 +134,13 @@
-<h2><a name="DV">DV</a></h2>
+<h2 id="DV">DV</h2>
<p><span class="time">0</span><span class="ease">0</span>We have already <a href="http://thread.gmane.org/gmane.comp.multimedia.matroska.devel/1817" class="external">talked about this some time ago</a>. So it might be time to actually implement it at least in MKVMerge and DirectShow or GStreamer... The source code of <a href="http://libdv.sourceforge.net/" class="external" title="http://libdv.sourceforge.net/">libdv</a> also gives some valuable information about the DV framing (mostly for PAL systems).</p>
-<h2><a name="Menu_system_ripped_from_DVDs">Menu system ripped from DVDs</a></h2>
+<h2 id="Menu_system_ripped_from_DVDs">Menu system ripped from DVDs</h2>
<ul>
<li><span class="time">4</span><span class="ease">3</span><span class="assign">robUx4/Haali</span>get the DVD specs and find out how to map the DVD menu system to Matroska</li>
@@ -149,7 +149,7 @@
-<h2><a name="TTA">TTA</a></h2>
+<h2 id="TTA">TTA</h2>
<p><span class="time">0</span><span class="ease">0</span>As the framing of <a href="http://tta.iszf.irk.ru/" class="external" title="http://tta.iszf.irk.ru/">TTA</a> is <a href="http://tta.iszf.irk.ru/index.php?menu=format" class="external" title="http://tta.iszf.irk.ru/index.php?menu=format">documented</a> it should be added in the usual muxing (from an original .tta file), demuxing tools :</p>
@@ -162,7 +162,7 @@
-<h2><a name="Wavpack">Wavpack</a></h2>
+<h2 id="Wavpack">Wavpack</h2>
<p><span class="time">0</span><span class="ease">0</span>David Bryant is working on a library version of his lossless audio codec. The format is also probably <a href="http://wavpack.com/lib_use.txt">documented</a> and <a href="http://wavpack.com/wvparser.c">container friendly</a>, so it should be added in the usual muxing (from an original .wv file), demuxing tools :</p>
@@ -179,7 +179,7 @@
-<h2><a name="GSTreamer_support">GSTreamer support</a></h2>
+<h2 id="GSTreamer_support">GSTreamer support</h2>
<ul>
<li><span class="time">0</span><span class="ease">0</span>find out what Matroska features GST support (and does not)</li>
@@ -191,20 +191,20 @@
-<h2><a name="Matroska_Everywhere">Matroska Everywhere</a></h2>
+<h2 id="Matroska_Everywhere">Matroska Everywhere</h2>
<p><span class="time">0</span><span class="ease">0</span>One of our initial goal was to make everything possible to avoid people to use AVI. We managed to make something better and that has the same features (and more). But we don't have all softwares supporting Matroska the way they support MKV. Of course it's impossible in closed applications. But all DirectShow, QuickTime, <a href="https://helixcommunity.org/forum/forum.php?forum_id=128" class="external" title="https://helixcommunity.org/forum/forum.php?forum id=128">Real applications</a> could support Matroska the same way they support AVI. AVI is still popular because you can run it on all platforms with the default player. So we should work in all these defaults players at least.</p>
<p>PS: It <a href="http://www.hydrogenaudio.org/index.php?showtopic=22686&hl=" class="external" title="http://www.hydrogenaudio.org/index.php?showtopic=22686&hl=">IS possible to play Vorbis</a> <a href="http://www.illadvised.com/~jordy/">in iTunes</a> so I guess support for Matroska can be added too.</p>
-<h3><a name="Matroska_Audio">Matroska Audio</a></h3>
+<h3 id="Matroska_Audio">Matroska Audio</h3>
<p><span class="time">0</span><span class="ease">0</span>As we'll soon have support for a large variety of audio formats (PCM, MP3, AAC, HE-AAC, Vorbis, FLAC, TTA, WavPack) it would be nice to work more on audio applications. We'll probably need a program to rip CDs and keep tags (a command-line application should be OK, using DirectShow for encoders) with these different codecs. We would also need support in Winamp (in_mka using DirectShow for decoders) and fb2k (half-done).</p>
-<h2><a name="matroska.org">Matroska.org</a></h2>
+<h2 id="matroska.org">Matroska.org</h2>
<ul>
<li><span class="time">0</span><span class="ease">0</span>Add more description of how each codec is muxed <a href="http://www.matroska.org/technical/specs/codecid/index.html" class="external">in the codec page</a>.</li>
@@ -213,14 +213,14 @@
</ul>
-<h2><a name="dl.matroska.org">dl.matroska.org</a></h2>
+<h2 id="dl.matroska.org">dl.matroska.org</h2>
<ul>
<li><span class="time">0</span><span class="ease">0</span>it would be nice to know/define all the links that should perpertually be there</li>
<li><span class="time">0</span><span class="ease">0</span>make some meaningful samples than span the various codec and features Matroska can support</li>
</ul>
-<h2><a name="packs.matroska.org">packs.matroska.org</a></h2>
+<h2 id="packs.matroska.org">packs.matroska.org</h2>
<ul>
<li><span class="time">2</span><span class="ease">1</span>add a japanese translation, one of the most popular visiting country</li>
Modified: trunk/www.matroska.org/data/technical/menu/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/menu/index.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/menu/index.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -46,7 +46,7 @@
<p>When a highlight is activated by the user, the player has to send the UID of the action to the Control Track. Then the Control Track codec will handle the action and possibly give new orders to the player.</p>
<p>The format used for storing images should be extensible. For the moment we'll use PNG and BMP, both with alpha channel.</p>
-<h2><a name="feat">Playback features</a></h2>
+<h2 id="feat">Playback features</h2>
<p>All the following features will be sent from the Control Track to the Player :</p>
<ul>
<li>Jump to chapter (UID, prev, next, number)</li>
Modified: trunk/www.matroska.org/data/technical/specs/channelposition/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/channelposition/index.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/specs/channelposition/index.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -17,7 +17,7 @@
<!--#include virtual="/include/page-head.html" -->
-<div id="pagetitle"><a name="channelposition" id="channelposition">Audio Channel Position</a></h2>
+<div id="pagetitle"><span id="channelposition">Audio Channel Position</span></h2>
<div id="content"><!-- InstanceBeginEditable name="Content" -->
<p>All successive (audio) channels are specified by their horizontal angle position. The position is coded using a signed int8 which represents the fraction of 180/x, the 0 reference is the center (front).</p>
Modified: trunk/www.matroska.org/data/technical/specs/chapters/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/chapters/index.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/specs/chapters/index.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -90,10 +90,11 @@
<td>-</td>
<td>sub-elements</td>
<td>A system to define basic menus and partition data. For more detailed
- information, look at the <a href="index.html">Chapters Explanation</a>.</td>
+ information, look at the <a href="chapters/index.html">Chapters
+ Explanation</a>.</td>
</tr>
-<tr>
- <td>EditionEntry<a name="EditionEntry"/></td>
+<tr id="EditionEntry">
+ <td>EditionEntry</td>
<td>2</td>
<td>[45][B9]</td>
<td>*</td>
@@ -103,8 +104,8 @@
<td>sub-elements</td>
<td>Contains all information about a segment edition.</td>
</tr>
-<tr>
- <td>EditionUID<a name="EditionUID"/></td>
+<tr id="EditionUID">
+ <td>EditionUID</td>
<td>3</td>
<td>[45][BC]</td>
<td>-</td>
@@ -114,8 +115,8 @@
<td>u-integer</td>
<td>A unique ID to identify the edition. It's useful for tagging an edition.</td>
</tr>
-<tr>
- <td>EditionFlagHidden<a name="EditionFlagHidden"/></td>
+<tr id="EditionFlagHidden">
+ <td>EditionFlagHidden</td>
<td>3</td>
<td>[45][BD]</td>
<td>*</td>
@@ -125,8 +126,8 @@
<td>u-integer (1 bit)</td>
<td>If an edition is hidden (1), it should not be available to the user interface (but still to Control Tracks).</td>
</tr>
-<tr>
- <td>EditionFlagDefault<a name="EditionFlagDefault"/></td>
+<tr id="EditionFlagDefault">
+ <td>EditionFlagDefault</td>
<td>3</td>
<td>[45][DB]</td>
<td>*</td>
@@ -136,19 +137,19 @@
<td>u-integer (1 bit)</td>
<td>If a flag is set (1) the edition should be used as the default one.</td>
</tr>
-<tr>
- <td>EditionProcessed<a name="EditionProcessed"/></td>
+<tr id="EditionProcessed">
+ <td>EditionProcessed</td>
<td>3</td>
<td>[45][DD]</td>
- <td>*</td>
<td>-</td>
<td>-</td>
+ <td>-</td>
<td>0</td>
<td>u-integer</td>
<td>The type of edition defined: 0 is a standard chapter definition, 1 is an edition with chapters defined multiple times and the order to play them is enforced.</td>
</tr>
-<tr>
- <td>ChapterAtom<a name="ChapterAtom"/></td>
+<tr id="ChapterAtom">
+ <td>ChapterAtom</td>
<td>3+</td>
<td>[B6]</td>
<td>*</td>
@@ -159,9 +160,9 @@
<td>Contains the atom information to use as the chapter atom (apply to all
tracks).</td>
</tr>
-<tr><td>ChapterUID<a name="ChapterUID"/></td><td>4+</td><td>[73][C4]</td><td>*</td><td>-</td><td>>0</td><td>-</td><td>u-integer</td><td>A unique ID to identify the Chapter.</td></tr>
-<tr>
- <td>ChapterTimeStart<a name="ChapterTimeStart"/></td>
+<tr id="ChapterUID"><td>ChapterUID</td><td>4+</td><td>[73][C4]</td><td>*</td><td>-</td><td>>0</td><td>-</td><td>u-integer</td><td>A unique ID to identify the Chapter.</td></tr>
+<tr id="ChapterTimeStart">
+ <td>ChapterTimeStart</td>
<td>4+</td>
<td>[91]</td>
<td>*</td>
@@ -171,8 +172,8 @@
<td>u-integer</td>
<td>Timecode of the start of Chapter (not scaled).</td>
</tr>
-<tr>
- <td>ChapterTimeEnd<a name="ChapterTimeEnd"/></td>
+<tr id="ChapterTimeEnd">
+ <td>ChapterTimeEnd</td>
<td>4+</td>
<td>[92]</td>
<td>-</td>
@@ -182,8 +183,8 @@
<td>u-integer</td>
<td>Timecode of the end of Chapter (timecode excluded, not scaled).</td>
</tr>
-<tr>
- <td>ChapterFlagHidden<a name="ChapterHidden"></a></td>
+<tr id="ChapterHidden">
+ <td>ChapterFlagHidden</td>
<td>4+</td>
<td>[98]</td>
<td>*</td>
@@ -193,8 +194,8 @@
<td>u-integer (1 bit)</td>
<td>If a chapter is hidden (1), it should not be available to the user interface (but still to Control Tracks).</td>
</tr>
-<tr>
- <td>ChapterFlagEnabled<a name="ChapterEnable"></a></td>
+<tr id="ChapterEnable">
+ <td>ChapterFlagEnabled</td>
<td>4+</td>
<td>[45][98]</td>
<td>*</td>
@@ -204,8 +205,8 @@
<td>u-integer (1 bit)</td>
<td>Specify wether the chapter is enabled. It can be enabled/disabled by a Control Track. When disabled, the movie should skip all the content between the TimeStart and TimeEnd of this chapter.</td>
</tr>
-<tr>
- <td>ChapterPhysicalEquiv<a name="ChapterPhysicalEquiv"></a></td>
+<tr id="ChapterPhysicalEquiv">
+ <td>ChapterPhysicalEquiv</td>
<td>4+</td>
<td>[63][C3]</td>
<td>-</td>
@@ -213,10 +214,10 @@
<td>-</td>
<td>-</td>
<td>u-integer</td>
- <td>Specify the physical equivalent of this ChapterAtom like "DVD" (60) or "SIDE" (50), see <a href="../index.html#physical">complete list of values</a>.</td>
+ <td>Specify the physical equivalent of this ChapterAtom like "DVD" (60) or "SIDE" (50), see <a href="#physical">complete list of values</a>.</td>
</tr>
-<tr>
- <td>ChapterProcessPrivate<a name="ChapterProcessPrivate"/></td>
+<tr id="ChapterProcessPrivate">
+ <td>ChapterProcessPrivate</td>
<td>4+</td>
<td>[45][0D]</td>
<td>-</td>
@@ -226,8 +227,8 @@
<td>binary</td>
<td>Some optional data attached to the EditionProcessed information. <a href="#dvd">For EditionProcessed = 1</a>, it is the "DVD level" equivalent.</td>
</tr>
-<tr>
- <td>ChapterTrack<a name="ChapterTrack"/></td>
+<tr id="ChapterTrack">
+ <td>ChapterTrack</td>
<td>4+</td>
<td>[8F]</td>
<td>-</td>
@@ -237,8 +238,8 @@
<td>sub-elements</td>
<td>List of tracks on which the chapter applies. If this element is not present, all tracks apply</td>
</tr>
-<tr>
- <td>ChapterTrackNumber<a name="ChapterTrackNumber"/></td>
+<tr id="ChapterTrackNumber">
+ <td>ChapterTrackNumber</td>
<td>5+</td>
<td>[89]</td>
<td>*</td>
@@ -251,8 +252,8 @@
unlisted tracks. Absense of this element indicates that the Chapter should
be applied to any currently used Tracks.</td>
</tr>
-<tr>
- <td>ChapterDisplay<a name="ChapterDisplay"/></td>
+<tr id="ChapterDisplay">
+ <td>ChapterDisplay</td>
<td>4+</td>
<td>[80]</td>
<td>-</td>
@@ -262,8 +263,8 @@
<td>sub-elements</td>
<td>Contains all possible strings to use for the chapter display.</td>
</tr>
-<tr>
- <td>ChapString<a name="ChapString"/></td>
+<tr id="ChapString">
+ <td>ChapString</td>
<td>5+</td>
<td>[85]</td>
<td>*</td>
@@ -273,8 +274,8 @@
<td>UTF-8</td>
<td>Contains the string to use as the chapter atom.</td>
</tr>
-<tr>
- <td>ChapLanguage<a name="ChapLanguage"/></td>
+<tr id="ChapLanguage">
+ <td>ChapLanguage</td>
<td>5+</td>
<td>[43][7C]</td>
<td>*</td>
@@ -284,8 +285,8 @@
<td>string</td>
<td>The languages corresponding to the string, in the <a href="http://lcweb.loc.gov/standards/iso639-2/englangn.html#two">bibliographic ISO-639-2 form</a>.</td>
</tr>
-<tr>
- <td>ChapCountry<a name="ChapCountry"/></td>
+<tr id="ChapCountry">
+ <td>ChapCountry</td>
<td>5+</td>
<td>[43][7E]</td>
<td>-</td>
@@ -295,8 +296,8 @@
<td>string</td>
<td>The countries corresponding to the string, same 2 octets as in <a href="http://www.iana.org/cctld/cctld-whois.htm">Internet domains</a>.</td>
</tr>
-<tr>
- <td>ChapProcess<a name="ChapProcess"/></td>
+<tr id="ChapProcess">
+ <td>ChapProcess</td>
<td>4+</td>
<td>[69][44]</td>
<td>-</td>
@@ -306,8 +307,8 @@
<td>sub-elements</td>
<td>Contains all the commands associated to the Atom (<a href="#dvd">For EditionProcessed = 1</a> The order of sub elements matter).</td>
</tr>
-<tr>
- <td>ChapProcessTime<a name="ChapProcessTime"/></td>
+<tr id="ChapProcessTime">
+ <td>ChapProcessTime</td>
<td>5+</td>
<td>[69][22]</td>
<td>*</td>
@@ -317,8 +318,8 @@
<td>u-integer</td>
<td>Defines when the process command should be handled (0: during the whole chapter, 1: before starting playback, 2: after playback of the chapter).</td>
</tr>
-<tr>
- <td>ChapProcessCommand<a name="ChapProcessCommand"/></td>
+<tr id="ChapProcessCommand">
+ <td>ChapProcessCommand</td>
<td>5+</td>
<td>[69][33]</td>
<td>*</td>
@@ -491,13 +492,13 @@
<tr><td colspan="5"> </td><td class="level6" colspan="3">ChapterString</td><td align="right" class="level6">Bleeper</td></tr>
</tbody></table>
-<h2><a name="menu"/>Menu features</h2>
+<h2 id="menu">Menu features</h2>
<p>The menu features are handled like a <em>chapter codec</em>. That means each codec has a type, some private data and some data in the chapters.</p>
<p>The type of the menu system is defined by the EditionProcessed parameter. For now only 2 values are supported : 0 no menu, 1 menu borrowed from the DVD. The private data depend on the type of menu system (stored in ChapterProcessPrivate), idem for the data in the chapters (stored in ChapProcessCommand).</p>
-<h3><a name="dvd"/>DVD menu</h3>
+<h3 id="dvd">DVD menu</h3>
<p>This is the case when EditionProcessed = 1. Each level of a chapter corresponds to a logical level in the DVD system that is stored in the first octet of the ChapterProcessPrivate. This DVD hierarchy is as follows:</p>
Modified: trunk/www.matroska.org/data/technical/specs/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/index.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/specs/index.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -1786,8 +1786,8 @@
<td>u-integer (1 bit)</td>
<td>If a flag is set (1) the edition should be used as the default one.</td>
</tr>
-<tr id="EditionManaged">
- <td>EditionManaged</td>
+<tr id="EditionProcessed">
+ <td>EditionProcessed</td>
<td>3</td>
<td>[45][DD]</td>
<td>-</td>
@@ -1863,8 +1863,19 @@
<td>-</td>
<td>-</td>
<td>u-integer</td>
- <td>Specify the physical equivalent of this ChapterAtom like "DVD" (60) or "SIDE" (50), see <a href="#physical">complete list of values</a>.</td>
+ <td>Specify the physical equivalent of this ChapterAtom like "DVD" (60) or "SIDE" (50), see <a href="chapter/index.html#physical">complete list of values</a>.</td>
</tr>
+<tr id="ChapterProcessPrivate">
+ <td>ChapterProcessPrivate</td>
+ <td>4+</td>
+ <td>[45][0D]</td>
+ <td>-</td>
+ <td>-</td>
+ <td>-</td>
+ <td>-</td>
+ <td>binary</td>
+ <td>Some optional data attached to the EditionProcessed information. <a href="#dvd">For EditionProcessed = 1</a>, it is the "DVD level" equivalent.</td>
+</tr>
<tr id="ChapterTrack">
<td>ChapterTrack</td>
<td>4+</td>
@@ -1934,6 +1945,39 @@
<td>string</td>
<td>The countries corresponding to the string, same 2 octets as in <a href="http://www.iana.org/cctld/cctld-whois.htm">Internet domains</a>.</td>
</tr>
+<tr id="ChapProcess">
+ <td>ChapProcess</td>
+ <td>4+</td>
+ <td>[69][44]</td>
+ <td>-</td>
+ <td>*</td>
+ <td>-</td>
+ <td>-</td>
+ <td>sub-elements</td>
+ <td>Contains all the commands associated to the Atom (<a href="#dvd">For EditionProcessed = 1</a> The order of sub elements matter).</td>
+</tr>
+<tr id="ChapProcessTime">
+ <td>ChapProcessTime</td>
+ <td>5+</td>
+ <td>[69][22]</td>
+ <td>*</td>
+ <td>-</td>
+ <td>-</td>
+ <td>-</td>
+ <td>u-integer</td>
+ <td>Defines when the process command should be handled (0: during the whole chapter, 1: before starting playback, 2: after playback of the chapter).</td>
+</tr>
+<tr id="ChapProcessCommand">
+ <td>ChapProcessCommand</td>
+ <td>5+</td>
+ <td>[69][33]</td>
+ <td>*</td>
+ <td>-</td>
+ <td>-</td>
+ <td>-</td>
+ <td>binary</td>
+ <td>Contains the command information. The data should be interpreted depending on the EditionProcessed value. <a href="chapter/index.html#dvd">For EditionProcessed = 1</a>, the data correspond to the binary DVD cell pre/post commands.</td>
+</tr>
<tr id="Tagging">
<th colspan="9">Tagging</th>
</tr>
@@ -1950,7 +1994,7 @@
tags can be found <a href="tagging/index.html">here.</a></td>
</tr>
<tr id="Tag">
- <td>Tag</td>
+ <td>Tag</a></td>
<td>2</td>
<td>[73][73]</td>
<td>*</td>
@@ -1994,8 +2038,19 @@
<td>string</td>
<td>An <strong>informational</strong> string that can be used to display the logical level of the target like "ALBUM", "TRACK", "MOVIE", "CHAPTER", etc (see <a href="tagging/index.html#targettypes">TargetType</a>).</td>
</tr>
+<tr id="TTrackUID">
+ <td>TrackUID</td>
+ <td>4</td>
+ <td>[63][C5]</td>
+ <td>-</td>
+ <td>*</td>
+ <td>-</td>
+ <td>0</td>
+ <td>u-integer</td>
+ <td>A unique ID to identify the Track(s) the tags belong to. If the value is 0 at this level, the tags apply to all tracks in the Segment.</td>
+</tr>
<tr id="TEditionUID">
- <td>EditionUID</td>
+ <td>EditionUID</a></td>
<td>4</td>
<td>[63][C9]</td>
<td>-</td>
@@ -2064,12 +2119,12 @@
<tr id="TagDefault">
<td>TagDefault</td>
<td>4+</td>
- <td>[44][B4]</td>
+ <td>[44][84]</td>
<td>*</td>
<td>-</td>
<td>0-1</td>
<td>1</td>
- <td>u-integer (1 bit)</td>
+ <td style="white-space: nowrap">u-integer (1 bit)</td>
<td>Indication to know if this is the default/original language to use for the given tag.</td>
</tr>
<tr id="TagString">
@@ -2092,7 +2147,7 @@
<td>-</td>
<td>-</td>
<td>binary</td>
- <td>The values of the Tag if it is binary. Note that this cannot be used in the same Tag as TagString or TagInteger.</td>
+ <td>The values of the Tag if it is binary. Note that this cannot be used in the same SimpleTag as TagString.</td>
</tr>
<!--
<tr><th colspan="9">Playback Control / Menu</th></tr>
Modified: trunk/www.matroska.org/data/technical/specs/notes.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/notes.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/specs/notes.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -35,7 +35,7 @@
<div id="content"><!-- InstanceBeginEditable name="Content" -->
-<h3><a name="Beginning of File"/>Beginning of File</h3>
+<h3 id="Beginning_of_File">Beginning of File</h3>
<p>An EBML file always starts with 0x1A. The 0x1A makes the DOS command "type"
ends display. That way you can include ASCII text before the EBML data and it
can be displayed. The EBML parser is safe from false-alarm with these ASCII
@@ -43,7 +43,7 @@
<p>Next the EBML header is stored. This allows the the parser to know what type
of EBML file it is parsing.</p>
<p></p>
-<h3><a name="Block_Timecodes"/>Block Timecodes</h3>
+<h3 id="Block_Timecodes">Block Timecodes</h3>
<p>The Block's timecode is signed interger that represents the Raw Timecode
relative to the <a href="index.html#Cluster">Cluster's</a> <a href="index.html#Timecode">Timecode</a>,
multiplied by the TimecodeScale. (see the <a href="notes.html#TimecodeScale">TimecodeScale
@@ -57,16 +57,16 @@
possible to have Blocks with a negative Raw Timecode. Blocks with a negative
Raw Timecode are not valid.</p>
<p></p>
-<h3><a name="Default_Values"/>Default Values</h3>
+<h3 id="Default_Values">Default Values</h3>
<p>The default value of an element is assumed when not present in the data stream.
It is assumed only in the scope of its upper-element (for example Language in
the scope of the Track element). If the upper element is not present or assumed,
then the element cannot be assumed.</p>
<p></p>
-<h3><a name="DRM"/>DRM</h3>
+<h3 id="DRM">DRM</h3>
<p>Digital Rights Management. See <a href="#Encryption">Encryption</a>.</p>
<p></p>
-<h3><a name="EBML Class"/>EBML Class</h3>
+<h3 id="EBML_Class">EBML Class</h3>
<p>A larger EBML class typically means the element has a lower probability/importance.
A larger Class-ID can be used as a synch word in case the file is damaged. Elements
that are used frequently, but do not need to act as a synch word, should have
@@ -75,7 +75,7 @@
if the file is damaged. However, the every common element in the BlockGroup
has a single octet ID to conserve space because of how frequently it is used.</p>
<p></p>
-<h3><a name="Encryption"/>Encryption</h3>
+<h3 id="Encryption">Encryption</h3>
<p>Encryption in Matroska is designed in a very generic style that allows people
to implement whatever form of encryption is best for them. It is easily possible
to use the encryption framework in Matroska as a type of DRM.</p>
@@ -90,13 +90,13 @@
<p>Encryption information is stored in the ContentEncodings section under the
ContentEncryption element.</p>
<p></p>
-<h3><a name="Octet"/>Octet</h3>
+<h3 id="Octet">Octet</h3>
<p>An Octet refers to a byte made of 8 bits.</p>
<p></p>
-<h3><a name="Overlay Track"/>Overlay Track</h3>
+<h3 id="Overlay_Track">Overlay Track</h3>
<p>Overlay tracks should be rendered in the same 'channel' as the track it's linked to. When content is found in such a track it is play on the rendering channel instead of the original track.</p>
<p></p>
-<h3><a name="Position References"/>Position References</h3>
+<h3 id="Position_References">Position References</h3>
<p>The position in some elements refers to the position, in octets, from the beginning
of an element. The reference is the beginning of the first Segment element.
0 = first level 1 element in the segment. When data is spanned over mutiple
@@ -106,25 +106,25 @@
size + second segment total size + offset of the element in the third segment.
</p>
<p></p>
-<h3><a name="Raw_Timecode"/>Raw Timecode</h3>
+<h3 id="Raw_Timecode">Raw Timecode</h3>
<p>The exact time of an object represented in nanoseconds. To find out a Block's
Raw Timecode, you need the Block's timecode, the <a href="index.html#Cluster">Cluster's</a> <a href="index.html#Timecode">Timecode</a>, and
the TimecodeScale. For calculation, please see the see the <a href="notes.html#TimecodeScale">TimecodeScale
notes.</a></p>
<p></p>
-<h3><a name="SegmentUID"/>SegmentUID</h3>
+<h3 id="SegmentUID">SegmentUID</h3>
<p>The 128 bits UIDs must be as unique as possible. It is suggested to compute the MD5 sum of some data parts of the file (the checksum of the Cluster level if you use one). </p>
<p></p>
<p></p>
<p></p>
<p></p>
-<h3><a name="Timecode_Types"/>Timecode Types</h3>
+<h3 id="Timecode_Types">Timecode Types</h3>
<p>Absolute Timecode = Block+Cluster<br>
Relative Timecode = Block<br>
Scaled Timecode = Block+Cluster<br>
Raw Timecode = (Block+Cluster)*TimecodeScale*TrackTimecodeScale</p>
<p></p>
-<h3><a name="TimecodeScale"/>TimecodeScale</h3>
+<h3 id="TimecodeScale">TimecodeScale</h3>
<p>The <a href="index.html#TimecodeScale">TimecodeScale</a> is used to calculate
the Raw Timecode of a Block. The timecode is obtained by adding the Block's
timecode to the <a href="index.html#Cluster">Cluster's</a> <a href="index.html#Timecode">Timecode</a>,
@@ -141,7 +141,7 @@
<p>So, the Block in this example has a specific time of 565497000000 in nanoseconds.
In milliseconds this would be 565497ms. </p>
<p> </p>
-<h3><a name="TimecodeScale_Rounding"/>TimecodeScale Rounding</h3>
+<h3 id="TimecodeScale_Rounding">TimecodeScale Rounding</h3>
<p>Because the default value of TimecodeScale is 1000000, which makes each
integer in the Cluster and Block timecodes equal 1ms, this is the most commonly
used. When dealing with audio, this causes innaccuracy with where you are seeking
@@ -219,7 +219,7 @@
rate it will iterate over each sample, calculate the AbsoluteTimestamp and
then re-calculate the sample number.</p>
<p></p>
-<h3><a name="TrackTimecodeScale"/>TrackTimecodeScale</h3>
+<h3 id="TrackTimecodeScale">TrackTimecodeScale</h3>
<p>The <a href="index.html#TrackTimeCodeScale">TrackTimecodeScale</a> is used align tracks that would otherwise be played at different speeds. An example of this would be if you have a film that was originally recorded at 24fps video. When playing this back through a PAL broadcasting system, it is standard to speed up the film to 25fps to match the 25fps display speed of the PAL broadcasting standard. However, when broadcasting the video through NTSC, it is typical to leave the film at its original speed. If you wanted to make a single file where there was one video stream, and an audio stream used from the PAL broadcast, as well as an audio stream used from the NTSC broadcast, you would have the problem that the PAL audio stream would be 1/24th faster than the NTSC audio stream, quickly leading to problems. It is possible to stretch out the PAL audio track and reencode it at a slower speed, however when dealing with lossy audio codecs, this often results in a loss of audio!
quality and/or larger file sizes. </p>
<p>This is the type of problem that TrackTimecodeScale was designed to fix. Using it, the video can be played back at a speed that will synch with either the NTSC or the PAL audio stream, depending on which is being used for playback.</p>
<p>To continue the above example: </p>
Modified: trunk/www.matroska.org/data/technical/specs/profiles/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/profiles/index.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/specs/profiles/index.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -14,7 +14,7 @@
<!--#include virtual="/include/page-head.html" -->
-<h2 id="pagetitle"><a name="Profiles"/>Profiles Grid</h2>
+<h2 id="pagetitle"><span id="Profiles">Profiles Grid</a></h2>
<div id="subnavbar">
Modified: trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -44,7 +44,7 @@
<li><a href="#volumes">Collection of CD sets</a></li>
</ul>
-<h2><a name="intro"/>Introduction</h2>
+<h2 id="intro">Introduction</h2>
<p>Audio content is usually found with tags, ie meta information about the content you can listen to like the artist name, the track title, the year of release, etc. The problem is that people are now ripping their CDs in just one file for consistency on their hard-drive and usually avoiding gap problems on live/classical/mixes albums. So now you can find many tracks in just one file, and the usual flat structure to tag content doesn't work anymore.</p>
@@ -69,7 +69,7 @@
-<h2><a name="whole"/>One file with all tracks</h2>
+<h2 id="whole">One file with all tracks</h2>
<p>In this case the file contains one continuous audio track of 44:28. Chapters are used to virtually split the content in many parts, ie the CD tracks. A basic ripping application would rip the CD tracks as follows :</p>
@@ -406,7 +406,7 @@
</li>
</ul>
-<h2><a name="cd"/>One file per CD track</h2>
+<h2 id="cd">One file per CD track</h2>
<p>Now let's split this one file in pieces :</p>
@@ -546,7 +546,7 @@
<p>etc...</p>
-<h2><a name="meaningful"/>One file per "meaningful" track</h2>
+<h2 id="meaningful">One file per "meaningful" track</h2>
<p>In this case the 4 first tracks appear in one file.</p>
@@ -791,7 +791,7 @@
<p>etc...</p>
-<h2><a name="two_cds"/>Album on 2 CDs</h2>
+<h2 id="two_cds">Album on 2 CDs</h2>
<p>Many albums contain 2 CD in the box. Here is an example of a real-life case and how to keep the information about the physical source: Future Sound Of London "<a href="http://www.discogs.com/release/8067">Lifeforms</a>". In this example we'll have one file per CD track.</p>
@@ -1016,7 +1016,7 @@
<p>etc...</p>
-<h2><a name="diff_cds"/>Album with 2 different CDs</h2>
+<h2 id="diff_cds">Album with 2 different CDs</h2>
<p>This is almost the same as the previous example. But this time each CD in the pack is related to a different logical level: DJ Hell "<a href="http://www.discogs.com/release/63287">Electronicbody-Housemusic</a>". In this example we'll have one file per CD track.</p>
@@ -1353,7 +1353,7 @@
-<h2><a name="volumes"/>Collection of CD sets</h2>
+<h2 id="volumes">Collection of CD sets</h2>
<p>Sometimes an album can contain many CDs. And sometimes an album can be part of a bigger collection, like a CD series. Here is one example of such a real-life case and how it should be tagged. We'll <strong>only cover the case of 1 file per CD</strong>. Other cases could be deduced from the previous examples.</p>
Modified: trunk/www.matroska.org/data/technical/specs/tagging/example-video.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/example-video.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/specs/tagging/example-video.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -39,11 +39,11 @@
<li><a href="#episode">One file per episode</a></li>
</ul>
-<h2><a name="intro"/>Introduction</h2>
+<h2 id="intro">Introduction</h2>
<p>Video content usually doesn't have tags in the file. But that doesn't mean it's a good thing. Here are some real-life examples where it makes sense to have tags. As for <a href="example-audio.html">audio</a> you can have all video parts of a bigger ensemble in the same file or in smaller files.</p>
-<h2><a name="basic"/>Basic movie</h2>
+<h2 id="basic">Basic movie</h2>
<p>Here is a very basic example of how you would add the title, director, date of release and comment about a movie on one DVD.</p>
@@ -82,7 +82,7 @@
</li>
</ul>
-<h2><a name="simpsons"/>Bigger example</h2>
+<h2 id="simpsons">Bigger example</h2>
<p>Let's consider <a href="http://www2.foxstore.com/detail.html?item=361&u=987698787">the Simpsons DVDs</a>. You have a set of DVDs, each containing a few episodes of a whole season. The episodes would be spanned as follows :</p>
@@ -159,7 +159,7 @@
-<h2><a name="whole"/>One file with all DVDs</h2>
+<h2 id="whole">One file with all DVDs</h2>
<p>In this case the file contains one continuous video track with all episodes one after the other. Chapters are used to virtually split the content in many parts, ie the DVDs, the episodes and chapters. A good ripping application would rip the DVDs with the same structure as above as nested chapters.</p>
@@ -366,7 +366,7 @@
</li>
</ul>
-<h2><a name="dvd"/>One file per DVD</h2>
+<h2 id="dvd">One file per DVD</h2>
<p>Now let's split this one file in pieces. The big difference is that the SEASON info are repeated in each files :</p>
@@ -640,7 +640,7 @@
</ul>
-<h2><a name="episode"/>One file per episode</h2>
+<h2 id="episode">One file per episode</h2>
<p>In this case we have 8 files, one for each episode.</p>
Modified: trunk/www.matroska.org/data/technical/specs/tagging/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-11-11 17:09:05 UTC (rev 780)
+++ trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-11-11 17:39:02 UTC (rev 781)
@@ -40,8 +40,8 @@
<th>Element Type</th>
<th>Description</th>
</tr>
-<tr>
- <td>Tags<a name="Tags" id="Tags"/></td>
+<tr id="Tags">
+ <td>Tags</td>
<td>1</td>
<td>[12][54][C3][67]</td>
<td>-</td>
@@ -52,8 +52,8 @@
<td>Element containing elements specific to Tracks/Chapters. A list of valid
tags can be found <a href="index.html">here.</a></td>
</tr>
-<tr>
- <td>Tag<a name="Tag" id="Tag"></a></td>
+<tr id="Tag">
+ <td>Tag</a></td>
<td>2</td>
<td>[73][73]</td>
<td>*</td>
@@ -63,9 +63,8 @@
<td>sub-elements</td>
<td>Element containing elements specific to Tracks/Chapters.</td>
</tr>
-<tr>
- <td>Targets<a name="Targets" id="Targets"
- ></a></td>
+<tr id="Targets">
+ <td>Targets</td>
<td>3</td>
<td>[63][C0]</td>
<td>*</td>
@@ -76,8 +75,8 @@
<td>Contain all UIDs where the specified meta data apply. It is void to
describe everything in the segment.</td>
</tr>
-<tr>
- <td>TargetTypeValue<a name="TargetTypeValue" id="TargetTypeValue"></a></td>
+<tr id="TargetTypeValue">
+ <td>TargetTypeValue</td>
<td>4</td>
<td>[68][CA]</td>
<td>-</td>
@@ -87,8 +86,8 @@
<td>u-integer</td>
<td>A number to indicate the logical level of the target (see <a href="#targettypes">TargetType</a>).</td>
</tr>
-<tr>
- <td>TargetType<a name="TargetType" id="TargetType"></a></td>
+<tr id="TargetType">
+ <td>TargetType</td>
<td>4</td>
<td>[63][CA]</td>
<td>-</td>
@@ -98,9 +97,8 @@
<td>string</td>
<td>An <strong>informational</strong> string that can be used to display the logical level of the target like "ALBUM", "TRACK", "MOVIE", "CHAPTER", etc (see <a href="#targettypes">TargetType</a>).</td>
</tr>
-<tr>
- <td>TrackUID<a name="TTrackUID" id="TTrackUID"
- ></a></td>
+<tr id="TTrackUID">
+ <td>TrackUID</td>
<td>4</td>
<td>[63][C5]</td>
<td>-</td>
@@ -110,8 +108,8 @@
<td>u-integer</td>
<td>A unique ID to identify the Track(s) the tags belong to. If the value is 0 at this level, the tags apply to all tracks in the Segment.</td>
</tr>
-<tr>
- <td>EditionUID<a name="TEditionUID" id="TEditionUID"></a></td>
+<tr id="TEditionUID">
+ <td>EditionUID</a></td>
<td>4</td>
<td>[63][C9]</td>
<td>-</td>
@@ -121,8 +119,8 @@
<td>u-integer</td>
<td>A unique ID to identify the EditionEntry(s) the tags belong to. If the value is 0 at this level, the tags apply to all editions in the Segment.</td>
</tr>
-<tr>
- <td>ChapterUID<a name="TChapterUID" id="TChapterUID"></a></td>
+<tr id="TChapterUID">
+ <td>ChapterUID</td>
<td>4</td>
<td>[63][C4]</td>
<td>-</td>
@@ -132,8 +130,8 @@
<td>u-integer</td>
<td>A unique ID to identify the Chapter(s) the tags belong to. If the value is 0 at this level, the tags apply to all chapters in the Segment.</td>
</tr>
-<tr>
- <td>AttachmentUID<a name="AttachmentUID" id="AttachmentUID"></a></td>
+<tr id="AttachmentUID">
+ <td>AttachmentUID</td>
<td>4</td>
<td>[63][C6]</td>
<td>-</td>
@@ -143,8 +141,8 @@
<td>u-integer</td>
<td>A unique ID to identify the Attachment(s) the tags belong to. If the value is 0 at this level, the tags apply to all the attachments in the Segment.</td>
</tr>
-<tr>
- <td>SimpleTag<a name="SimpleTag" id="SimpleTag"/></td>
+<tr id="SimpleTag">
+ <td>SimpleTag</td>
<td>3+</td>
<td>[67][C8]</td>
<td>*</td>
@@ -154,9 +152,8 @@
<td>sub-elements</td>
<td>Contains general information about the target.</td>
</tr>
-<tr>
- <td>TagName<a name="TagName" id="TagName"
- ></a></td>
+<tr id="TagName">
+ <td>TagName</td>
<td>4+</td>
<td>[45][A3]</td>
<td>*</td>
@@ -167,8 +164,8 @@
<td>The name of the Tag that is going to be stored.</td>
</tr>
-<tr>
- <td>TagLanguage<a name="TagLanguage" id="TagLanguage"></a></td>
+<tr id="TagLanguage">
+ <td>TagLanguage</td>
<td>4+</td>
<td>[44][7A]</td>
<td>*</td>
@@ -178,8 +175,8 @@
<td>string</td>
<td>Specifies the language of the tag specified, in the <a href="../index.html#languages">Matroska languages form</a>.</td>
</tr>
-<tr>
- <td>TagDefault<a name="TagDefault" id="TagDefault"></a></td>
+<tr id="TagDefault">
+ <td>TagDefault</td>
<td>4+</td>
<td>[44][84]</td>
<td>*</td>
@@ -189,8 +186,8 @@
<td style="white-space: nowrap">u-integer (1 bit)</td>
<td>Indication to know if this is the default/original language to use for the given tag.</td>
</tr>
-<tr>
- <td>TagString<a name="TagString" id="TagString"></a></td>
+<tr id="TagString">
+ <td>TagString</td>
<td>4+</td>
<td>[44][87]</td>
<td>-</td>
@@ -200,8 +197,8 @@
<td>UTF-8</td>
<td>The value of the Tag.</td>
</tr>
-<tr>
- <td>TagBinary<a name="TagBinary" id="TagBinary"></a></td>
+<tr id="TagBinary">
+ <td>TagBinary</td>
<td>4+</td>
<td>[44][85]</td>
<td>-</td>
@@ -237,7 +234,7 @@
data should be stored using BASE64 encoding if it is being stored at authoring
time. <a href="tagexamples/example.xml">Example XML Tags</a></p>
-<h2>Why official tags matter<a name="why"/></h2>
+<h2 id="why">Why official tags matter</h2>
<p>There is a debate between people who think all tags should be free and those who think all tags should be strict. If you look at this page you will realise we are in between.</p>
@@ -251,13 +248,13 @@
<h2>Tag Formatting</h2>
<ul>
<li>The TagName should always be written in all capital letters and contain no space.</li>
- <li><a name="time"/>The fields with dates should have the following format: YYYY-MM-DD
+ <li id="time">The fields with dates should have the following format: YYYY-MM-DD
HH:MM:SS.MSS YYYY = Year, -MM = Month, -DD = Days, HH = Hours, :MM = Minutes,
:SS = Seconds, :MSS = Milliseconds. To store less accuracy, you remove items
starting from the right. To store only the year, you would use, "2004".
To store a specific day such as May 1st, 2003, you would use "2003-05-01".
</li>
-<li><a name="float"/>Fields that require a Float should use the "."
+<li id="float">Fields that require a Float should use the "."
mark instead of the "," mark. To display it differently for another
local, applications should support auto replacement on display. Also, a thousandths
separator should not be used.</li>
@@ -266,7 +263,7 @@
would store "15.59" instead of "$15.59USD".</li>
</ul>
-<h2><a name="targettypes"/>Target types</h2>
+<h2 id="targettypes">Target types</h2>
<p>The TargetType element allows tagging of different parts that are inside or outside a given file. For example in an audio file with one song you could have information about the album it comes from and even the CD set even if it's not found in the file.</p>
@@ -291,7 +288,7 @@
<p>Here is an example of how these <a href="#Organizational">organizational</a> tags work: If you set 10 TOTAL_PARTS to the ALBUM level (40) it means the album contains 10 lower parts. The lower part in question is the first lower level that is specified in the file. So if it's TRACK (30) then that means it contains 10 tracks. If it's MOVEMENT (20) that means it's 10 movements, etc.</p>
-<h2><a name="tags"/>Official tags</h2>
+<h2 id="tags">Official tags</h2>
<p>The following is a complete list of the supported Matroska
Tags. While it is possible to use Tag names that are not listed below, this
@@ -303,7 +300,7 @@
<div class="techdef">
<table>
<tr>
- <th colspan="5"><a name="original"/>Nesting Information (tags containing other tags)</th>
+ <th colspan="5" id="original">Nesting Information (tags containing other tags)</th>
</tr>
<tr>
<td>ORIGINAL</td>
@@ -315,8 +312,8 @@
<td>-</td>
<td>A tag that contains other tags to describe a sample used in the targeted item taken from another work of art. All tags in this list can be used "under" the SAMPLE tag like TITLE, ARTIST, DATE_RELEASED, etc.</td>
</tr>
- <tr>
- <td>COUNTRY<a name="country"></td>
+ <tr id="country">
+ <td>COUNTRY</td>
<td>UTF-8</td>
<td>The name of the country (<a href="http://lcweb.loc.gov/standards/iso639-2/englangn.html#two">biblio ISO-639-2</a>) that is meant to have other tags inside (using nested tags) to country specific information about the item. All tags in this list can be used "under" the COUNTRY_SPECIFIC tag like LABEL, PUBLISH_RATING, etc.</td>
</tr>
@@ -328,8 +325,8 @@
<th title="Defines if either TagString or TagBinary is used">Type</th>
<th>Description</th>
</tr>
- <tr>
- <th colspan="5"><a name="Organizational">Organizational Information</a></th>
+ <tr id="Organizational">
+ <th colspan="5">Organizational Information</th>
</tr>
<tr>
<td>TOTAL_PARTS</td>
@@ -341,8 +338,8 @@
<td>UTF-8</td>
<td>Number of the current part of the current level. (e.g. if TargetType is TRACK, the track number of an audio CD)</td>
</tr>
- <tr>
- <th colspan="5"><a name="titles">Titles</a></th>
+ <tr id="titles">
+ <th colspan="5">Titles</th>
</tr>
<tr>
<td>TITLE</td>
@@ -356,16 +353,16 @@
<td>UTF-8</td>
<td>Sub Title of the entity.</td>
</tr>
- <tr>
- <th colspan="5"><a name="original"/>Nested Information (tags contained in other tags)</th>
+ <tr id="original">
+ <th colspan="5">Nested Information (tags contained in other tags)</th>
</tr>
- <tr>
- <td>URL<a name="URL" id="URL"/></td>
+ <tr id="URL">
+ <td>URL</td>
<td>UTF-8</td>
<td>URL corresponding to the tag it's included in.</td>
</tr>
<tr>
- <td>SORT_WITH<a name="URL" id="URL"/></td>
+ <td>SORT_WITH</td>
<td>UTF-8</td>
<td>A child element to indicate what alternative value the parent tag can have to be sorted, for example "Pet Shop Boys" instead of "The Pet Shop Boys". Or "Marley Bob" and "Marley Ziggy" (no comma needed).</td>
</tr>
@@ -374,28 +371,28 @@
<td>UTF-8</td>
<td>The instruments that are being used/played, separated by a comma. It should be a child of the following tags: ARTIST, LEAD_PERFORMER or ACCOMPANIMENT.</td>
</tr>
- <tr>
- <td>EMAIL<a name="Email" id="Email"/></td>
+ <tr id="Email">
+ <td>EMAIL</td>
<td>UTF-8</td>
<td>Email corresponding to the tag it's included in.</td>
</tr>
- <tr>
- <td>ADDRESS<a name="Address" id="Address"/></td>
+ <tr id="Address">
+ <td>ADDRESS</td>
<td>UTF-8</td>
<td>The physical address of the entity. The address should include a country code. It can be useful for a recording label.</td>
</tr>
- <tr>
- <td>FAX<a name="Fax" id="Fax"/></td>
+ <tr id="Fax">
+ <td>FAX</td>
<td>UTF-8</td>
<td>The fax number corresponding to the tag it's included in. It can be useful for a recording label.</td>
</tr>
- <tr>
- <td>PHONE<a name="Phone" id="Phone"/></td>
+ <tr id="Phone">
+ <td>PHONE</td>
<td>UTF-8</td>
<td>The phone number corresponding to the tag it's included in. It can be useful for a recording label.</td>
</tr>
- <tr>
- <th colspan="5">Entities<a name="Entities"/></th>
+ <tr id="Entities">
+ <th colspan="5">Entities</th>
</tr>
<tr>
<td>ARTIST</td>
@@ -562,36 +559,36 @@
<td>UTF-8</td>
<td>The record label or imprint on the disc.</td>
</tr>
- <tr>
- <th colspan="5"><a name="Search">Search / Classification</a></th>
+ <tr id="Search">
+ <th colspan="5">Search / Classification</th>
</tr>
- <tr class="subjective">
- <td>GENRE<a name="Genre"></a></td>
+ <tr class="subjective" id="Genre">
+ <td>GENRE</td>
<td>UTF-8</td>
<td>The main genre (classical, ambient-house, synthpop, sci-fi, drama, etc). The format follows the infamous TCON tag in ID3.</td>
</tr>
- <tr class="subjective">
- <td>MOOD<a name="Genre"></a></td>
+ <tr class="subjective" id="Genre">
+ <td>MOOD</td>
<td>UTF-8</td>
<td>Intended to reflect the mood of the item with a few keywords, e.g. "Romantic", "Sad" or "Uplifting". The format follows that of the TMOO tag in ID3.</td>
</tr>
- <tr>
- <td>CONTENT_TYPE<a name="Type"></a></td>
+ <tr id="Type">
+ <td>CONTENT_TYPE</td>
<td>UTF-8</td>
<td>The type of the item. e.g. Documentary, Feature Film, Cartoon, Music Video, Music, Sound FX, ...</td>
</tr>
- <tr>
- <td>SUBJECT<a name="Subject"></a></td>
+ <tr id="Subject">
+ <td>SUBJECT</td>
<td>UTF-8</td>
<td>Describes the topic of the file, such as "Aerial view of Seattle."</td>
</tr>
- <tr>
- <td>DESCRIPTION<a name="Description"></a></td>
+ <tr id="Description">
+ <td>DESCRIPTION</td>
<td>UTF-8</td>
<td>A short description of the content, such as "Two birds flying."</td>
</tr>
- <tr>
- <td>KEYWORDS<a name="Keywords"></a></td>
+ <tr id="Keywords">
+ <td>KEYWORDS</td>
<td>UTF-8</td>
<td>Keywords to the item separated by a comma, used for searching.</td>
</tr>
@@ -605,8 +602,8 @@
<td>UTF-8</td>
<td>A description of the story line of the item. </td>
</tr>
- <tr>
- <td>INITIAL_KEY<a name="InitialKey"></a></td>
+ <tr id="InitialKey">
+ <td>INITIAL_KEY</td>
<td>UTF-8</td>
<td>The initial key that a musical track starts in. The format is identical
to ID3.</td>
@@ -616,18 +613,18 @@
<td>UTF-8</td>
<td>Describes the period that the piece is from or about. For example, "Renaissance". </td>
</tr>
- <tr>
- <td>LAW_RATING<a name="law_rating"></a></td>
+ <tr id="law_rating">
+ <td>LAW_RATING</td>
<td>UTF-8</td>
<td>Depending on the <a href="#country">country</a> it's the format of the rating of a movie (P, R, X in the USA, an age in other countries or a URI defining a logo).</td>
</tr>
- <tr>
- <td>ICRA<a name="icra"></a></td>
+ <tr id="icra">
+ <td>ICRA</td>
<td>binary</td>
<td>The <a href="http://www.icra.org/">ICRA</a> content rating for parental control. (Previously RSACi)</td>
</tr>
- <tr>
- <th colspan="5"><a name="Temporal">Temporal Information</a></th>
+ <tr id="Temporal">
+ <th colspan="5">Temporal Information</th>
</tr>
<tr>
<td>DATE_RELEASED</td>
@@ -666,8 +663,8 @@
<td>UTF-8</td>
<td>Information on when the file was purchased (see also <a href="#commercial">purchase tags</a>).</td>
</tr>
- <tr>
- <th colspan="5"><a name="Spacial">Spacial Information</a></th>
+ <tr id="Spacial">
+ <th colspan="5">Spacial Information</th>
</tr>
<tr>
<td>RECORDING_LOCATION</td>
@@ -687,88 +684,87 @@
<td>Nationality of the main composer of the item, mostly for classical music. The countries corresponding to the string, same 2 octets as in Internet
domains, or possibly ISO 3166.</td>
</tr>
- <tr>
- <th colspan="5">Personal<a name="Personal"/></th>
+ <tr id="Personal">
+ <th colspan="5">Personal</th>
</tr>
<tr class="subjective">
<td>COMMENT</td>
<td>UTF-8</td>
<td>Any comment related to the content.</td>
</tr>
- <tr class="subjective">
- <td>PLAY_COUNTER<a name="PlayCounter"></a></td>
+ <tr class="subjective" id="PlayCounter">
+ <td>PLAY_COUNTER</td>
<td>UTF-8</td>
<td>The number of time the item has been played.</td>
</tr>
- <tr class="subjective">
- <td>RATING<a name="rating"></a></td>
+ <tr class="subjective" id="rating">
+ <td>RATING</td>
<td>UTF-8</td>
<td>A numeric value defining how much a person likes the song/movie. The number is between 0 and 5 with decimal values possible (e.g. 2.7), 5(.0) being the highest possible rating. Other rating systems with different ranges will have to be scaled.</td>
</tr>
- <tr>
- <th colspan="5">Technical Information<a name="Technical"/></th>
+ <tr id="Technical">
+ <th colspan="5">Technical Information</th>
</tr>
- <tr>
- <td>ORIGINAL_MEDIA_TYPE<a name="OriginalMediaType"></a></td>
+ <tr id="OriginalMediaType">
+ <td>ORIGINAL_MEDIA_TYPE</td>
<td>UTF-8</td>
<td>Describes the original type of the media, such as, "DVD",
"CD", "computer image," "drawing," "lithograph," and so forth. This is akin to
the <a href="http://www.id3.org/id3v2.3.0.html#TMED">TMED tag in ID3.</a></td>
</tr>
- <tr>
- <td>ENCODER<a name="Encoder"></a></td>
+ <tr id="Encoder">
+ <td>ENCODER</td>
<td>UTF-8</td>
<td>The software or hardware used to encode this item. ("LAME" or "XviD")</td>
</tr>
- <tr>
- <td>ENCODER_SETTINGS<a name="EncodeSettings"></a></td>
+ <tr id="EncodeSettings">
+ <td>ENCODER_SETTINGS</td>
<td>UTF-8</td>
<td>A list of the settings used for encoding this item. No specific format.</td>
</tr>
- <tr>
- <td>BPS<a name="BitsPS"/></td>
+ <tr id="BitsPS">
+ <td>BPS</td>
<td>UTF-8</td>
<td>The average bits per second of the specified item. This is only the data
in the Blocks, and excludes headers and any container overhead.</td>
</tr>
- <tr>
- <td>FPS<a name="FramesPS"/></td>
+ <tr id="FramesPS">
+ <td>FPS</td>
<td>UTF-8</td>
<td>The average frames per second of the specified item. This is typically
the average number of Blocks per second. In the event that lacing is used,
each laced chunk is to be counted as a seperate frame. </td>
</tr>
- <tr>
- <td><a name="BPM"/>BPM</td>
+ <tr id="BPM">
+ <td>BPM</td>
<td>UTF-8</td>
<td>Average number of beats per minute in the complete target (e.g. a chapter). Usually a decimal number.</td>
</tr>
- <tr>
- <td><a name="MEASURE"/>MEASURE</td>
+ <tr id="MEASURE">
+ <td>MEASURE</td>
<td>UTF-8</td>
<td>In music, a measure is a unit of time in Western music like "4/4". It represents a regular grouping of beats, a meter, as indicated in musical notation by the time signature.. The majority of the contemporary rock and pop music you hear on the radio these days is written in the 4/4 time signature.</td>
</tr>
- <tr>
- <td><a name="TUNING"/>TUNING</td>
+ <tr id="TUNING">
+ <td>TUNING</td>
<td>UTF-8</td>
<td>It is saved as a frequency in hertz to allow near-perfect tuning of instruments to the same tone as the musical piece (e.g. "441.34" in Hertz). The default value is 440.0 Hz.</td>
</tr>
- <tr>
- <td>REPLAYGAIN_GAIN<a name="REPLAYGAIN_GAIN"/></td>
+ <tr id="REPLAYGAIN_GAIN">
+ <td>REPLAYGAIN_GAIN</td>
<td>binary</td>
<td>The gain to apply to reach 89dB SPL on playback. This is based on the <a href="http://www.replaygain.org/">Replay Gain standard</a>. Note that ReplayGain information can be found at all TargetType levels (track, album, etc).</td>
</tr>
- <tr>
- <td>REPLAYGAIN_PEAK<a name="REPLAYGAIN_PEAK" id="REPLAYGAIN_PEAK"
- ></a></td>
+ <tr id="REPLAYGAIN_PEAK">
+ <td>REPLAYGAIN_PEAK</td>
<td>binary</td>
<td>The maximum absolute peak value of the item. This is based on the <a href="http://www.replaygain.org/">Replay Gain standard</a>.</td>
</tr>
- <tr>
- <th colspan="5"><a name="identifiers">Identifiers</a></th>
+ <tr id="identifiers">
+ <th colspan="5">Identifiers</th>
</tr>
<tr>
<td>ISRC</td>
@@ -805,8 +801,8 @@
<td>UTF-8</td>
<td><a href="http://www.loc.gov/marc/lccn.html">Library of Congress Control Number</a></td>
</tr>
- <tr>
- <th colspan="5"><a name="commercial">Commercial</a></th>
+ <tr id="commercial">
+ <th colspan="5">Commercial</th>
</tr>
<tr>
<td>PURCHASE_ITEM</td>
@@ -826,22 +822,22 @@
<td>Information on the person who purchased the file. This is akin
to the <a href="http://www.id3.org/id3v2.3.0.html#TOWN">TOWN tag in ID3</a>.</td>
</tr>
- <tr>
- <td>PURCHASE_PRICE<a name="Price"></a></td>
+ <tr id="Price">
+ <td>PURCHASE_PRICE</td>
<td>UTF-8</td>
<td>The amount paid for entity. There should only be a numeric value in here.
Only numbers, no letters or symbols other than ".". For instance,
you would store "15.59" instead of "$15.59USD".</td>
</tr>
- <tr>
- <td>PURCHASE_CURRENCY<a name="Currency"></a></td>
+ <tr id="Currency">
+ <td>PURCHASE_CURRENCY</td>
<td>UTF-8</td>
<td>The currency type used to pay for the entity. Use <a
href="http://www.bsi-global.com/Technical%2BInformation/Publications/_Publications/tig90.xalter"
>ISO 4217</a> for the 3 letter currency code.</td>
</tr>
- <tr>
- <th colspan="5"><a name="legal">Legal</a></th>
+ <tr id="legal">
+ <th colspan="5">Legal</th>
</tr>
<tr>
<td>COPYRIGHT</td>
@@ -862,7 +858,7 @@
</tr>
</table>
</div>
-<h1>Notes<a name="notes"/></h1>
+<h1 id="notes">Notes</h1>
<ul>
<li>In the Target list, a logicial OR is applied on all tracks, a logicial OR is applied on all chapters. Then a logical AND is applied between the Tracks list and the Chapters list to know if an element belongs to this Target.</li>
</ul>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.