[www] r516 - trunk/www.matroska.org/data/technical/specs/tagging

Author: robux4
Date: 2004-08-23 11:45:53 +0400 (Mon, 23 Aug 2004)
New Revision: 516

Modified:
   trunk/www.matroska.org/data/technical/specs/tagging/index.html
Log:
design: fix XHTML

Modified: trunk/www.matroska.org/data/technical/specs/tagging/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/index.html	2004-08-23 07:41:59 UTC (rev 515)
+++ trunk/www.matroska.org/data/technical/specs/tagging/index.html	2004-08-23 07:45:53 UTC (rev 516)
@@ -231,7 +231,7 @@
 
 <p>Advanced-users application might let you put any tag in your file. But for the rest of the applications, they usually give you a basic list of tags you can use. Both have their needs. But it's usually a bad idea to use custom/exotic tags because <em>you</em> will probably be the only person to use this information even though everyone else could benefit from it. So hopefully when someone want to put informations in one's file, they will find an official one that fit them and hopefully use it ! If it's not in the list, this person can contact us any time for addition of such a missing tag. But it doesn't mean it will be accepted... Matroska files are not meant the become a whole database of people who made costumes for a film. A website would be better for that... It's hard to define what should be in and what doesn't make sense in a file. So we'll treat each request carefully.</p>
 
-<p>We also need an official list simply for developpers to be able to display relevant informations in their own design (if they choose to support a list of meta-information they should know which tag has the wanted meaning so that other apps could understand the same meaning).
+<p>We also need an official list simply for developpers to be able to display relevant informations in their own design (if they choose to support a list of meta-information they should know which tag has the wanted meaning so that other apps could understand the same meaning).</p>
 
 <h2>Tag translations</h2>
 <p>To be able to save tags from other systems to Matroska we need to translate them to our system. There is a translation table <a href="othertagsystems/comparetable.html">on our site</a> and <a href="http://hobba.hobba.nl/audio/tag_frame_reference.html">one done by Prodoc</a> that will hopefully be featured here soon.</p>
@@ -429,7 +429,6 @@
     <td>UTF-8</td>
     <td>The name of the chief cameraman (often the same as DIRECTOR_OF_PHOTOGRAPHY).</td>
   </tr>
-  </tr>
     <tr>
     <td>SOUND_ENGINEER</td>
     <td>UTF-8</td>
@@ -716,10 +715,12 @@
     <td>The location where the item was recorded. The countries corresponding to the string, same 2 octets as in Internet
       domains, or possibly ISO 3166. This code is followed by a comma, then more detailed information such as state/province, another comma, and then city. For example, &quot;US, Texas, Austin&quot;. This will allow for easy sorting. It is okay to only store the country, or the country and the state/province. More detailed information can be added after the city through the use of additional commas. In cases where the province/state is unknown, but you want to store the city, simply leave a space between the two commas. For example, &quot;US, , Austin&quot;. </td>
   </tr>
+  <tr>
   <td>RECORDING_COORDINATES</td>
     <td>UTF-8</td>
     <td>Geographical cooridnates of the idem. e.g. "Latitude: 29° 34’ 40”N, Longitude: 98° 41’ 22”W" </td>
   </tr>
+  <tr>
   <td>RECORDING_ALTITUDE</td>
     <td>UTF-8</td>
     <td>Altitude of the idem. e.g. "357 meters" "-30 meters" </td>
@@ -1009,9 +1010,8 @@
     <td>The terms of use for this item. This is akin to the USER tag in ID3.</td>
   </tr>
 </table>
-</div>
-</p>
-</a>
+
+
 <h1>Notes<a name="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>