Author: robux4
Date: 2004-08-20 12:57:19 +0400 (Fri, 20 Aug 2004)
New Revision: 467
Modified:
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:
fix typos and better navigation
Modified: trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html 2004-08-20 08:48:49 UTC (rev 466)
+++ trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html 2004-08-20 08:57:19 UTC (rev 467)
@@ -31,8 +31,15 @@
<div id="content">
-<h2>Introduction</h2>
+<ul>
+<li><a href="#intro">Introduction</a></li>
+<li><a href="#whole">One file with all tracks</a></li>
+<li><a href="#cd">One file per CD track</a></li>
+<li><a href="#meaningful">One file per "meaningful" track</a></li>
+</ul>
+<h2><a name="intro"/>Introduction</h2>
+
<p>Audio content is usually found with tags, ie meta informations 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>
<p>Let's consider the mini-album of <a href="http://www.the-micronauts.com/">The Micronauts</a> "<a href="http://www.discogs.com/release/8788">Bleep To Bleep</a>", as found in the <a href="../chapters/index.html">chapter examples</a>. The tracks are layed out on the CD as follows :</p>
@@ -56,7 +63,7 @@
-<h3>One file with all tracks</h3>
+<h3><a name="whole"/>One file with all tracks</h3>
<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>
@@ -403,7 +410,7 @@
</li>
</ul>
-<h3>One file per CD track</h3>
+<h3><a name="cd"/>One file per CD track</h3>
<p>Now let's split this one file in pieces :</p>
@@ -539,7 +546,7 @@
<p>etc...</p>
-<h3>One file per "meaningful" track</h3>
+<h3><a name="meaningful"/>One file per "meaningful" track</h3>
<p>In this case the 4 first tracks appear in one file.</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-08-20 08:48:49 UTC (rev 466)
+++ trunk/www.matroska.org/data/technical/specs/tagging/example-video.html 2004-08-20 08:57:19 UTC (rev 467)
@@ -31,8 +31,15 @@
<div id="content">
-<h2>Introduction</h2>
+<ul>
+<li><a href="#intro">Introduction</a></li>
+<li><a href="#whole">One file with all DVDs</a></li>
+<li><a href="#dvd">One file per DVD</a></li>
+<li><a href="#episode">One file per episode</a></li>
+</ul>
+<h2><a name="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 a smaller.</p>
<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>
@@ -110,7 +117,7 @@
-<h3>One file with all DVDs</h3>
+<h3><a name="whole"/>One file with all DVDs</h3>
<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>
@@ -372,7 +379,7 @@
</li>
</ul>
-<h3>One file per DVD</h3>
+<h3><a name="dvd"/>One file per DVD</h3>
<p>Now let's split this one file in pieces. The big difference is that the SEASON info are repeated in each files :</p>
@@ -720,7 +727,7 @@
<p>etc...</p>
-<h3>One file per episode</h3>
+<h3><a name="episode"/>One file per episode</h3>
<p>In this case we have 8 files, one for each episode.</p>
@@ -1039,9 +1046,11 @@
</li>
</ul>
-<p><strong>NOTE: If you want to keep the original episode numbers, you must remove MEDIUM TargetType.</strong></p>
+<p>etc...</p>
+<p><strong>NOTE: If you want to keep the original episode numbers, you must remove the MEDIUM TargetType.</strong></p>
+
</div>
<!--#include virtual="/include/page-tail.html" -->
Modified: trunk/www.matroska.org/data/technical/specs/tagging/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-08-20 08:48:49 UTC (rev 466)
+++ trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-08-20 08:57:19 UTC (rev 467)
@@ -1,14 +1,10 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--#set var="docroot" value="../../../" -->
-<html><!-- InstanceBegin template="/Templates/main.dwt" codeOutsideHTMLIsLocked="false" -->
+<html>
<head>
-<!-- InstanceBeginEditable name="doctitle" -->
<title>Matroska Tags</title>
-<!-- InstanceEndEditable -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<!--#include virtual="/include/stylesheet-main.html" -->
-<!-- InstanceBeginEditable name="head" -->
-<!-- InstanceEndEditable -->
</head>
<body>
@@ -29,10 +25,8 @@
</div>
-<div id="content"><!-- InstanceBeginEditable name="Content" -->
+<div id="content">
-<h2>WARNING: the current tag system is being reworked, so changes are bound to happen.</h2>
-
<div class="techdef">
<table>
<tr>
@@ -209,7 +203,7 @@
</table></div>
<p>When a Tag is nested within another Tag, the nested Tag becomes an attribute
- of the base tag. For instace, if you wanted to store the dates that a singer
+ of the base tag. For instance, if you wanted to store the dates that a singer
used certain addresses for, that singer being the lead singer for a track that
included multiple bands simultaneously, then your tag tree would look something
like this:</p>
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.