Author: robux4
Date: 2004-08-27 15:14:31 +0400 (Fri, 27 Aug 2004)
New Revision: 584
Modified:
trunk/www.matroska.org/data/technical/specs/tagging/index.html
Log:
spec: add more precision on the use of TOTAL_PARTS and PART_NUMBER
Modified: trunk/www.matroska.org/data/technical/specs/tagging/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-08-27 10:56:13 UTC (rev 583)
+++ trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-08-27 11:14:31 UTC (rev 584)
@@ -268,10 +268,8 @@
<h2><a name="targettypes"/>Target types</h2>
-<p>The TargetType/TargetPhysical 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 informations about the album it comes from and even the CD set even if it's not found in the file.</p>
+<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 informations about the album it comes from and even the CD set even if it's not found in the file.</p>
-<p><strong>When a level doesn't exist it must not be specified in the files, so that the TOTAL_PARTS and PART_NUMBER elements match the same levels.</strong></p>
-
<p>For application to know what kind of information (like TITLE) relates to a certain level (CD title or track title), we also need a set of official TargetType names. For now audio and video will have different values & names. That also means the same tag name can have different meanings depending on where it is (otherwise we would end up with 15 TITLE_ tags).</p>
<div class="techdef">
@@ -288,6 +286,10 @@
<p>An upper level value tag applies to the lower level. That means if a CD has the same artist for all tracks, you just need to set the ARTIST tag at level 40 (ALBUM) and not to each TRACK (but you can). That also means that <strong>if some parts of the CD have no known ARTIST the value must be set to nothing (a void string "")</strong>.</p>
+<p><strong>When a level doesn't exist it must not be specified in the files, so that the TOTAL_PARTS and PART_NUMBER elements match the same levels.</strong></p>
+
+<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>
<p>The following is a complete list of the supported Matroska
@@ -315,7 +317,7 @@
<tr>
<td>PART_NUMBER</td>
<td>UTF-8</td>
- <td>Number of the current part of the current level. (e.g. the track number of an audio CD)</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>
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.