Author: atamido
Date: 2004-09-10 11:53:54 +0400 (Fri, 10 Sep 2004)
New Revision: 685
Modified:
trunk/www.matroska.org/data/overhead.html
trunk/www.matroska.org/data/technical/overhead/index.html
trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html
trunk/www.matroska.org/data/technical/specs/tagging/index.html
trunk/www.matroska.org/data/technical/specs/tagging/oldtags.html
trunk/www.matroska.org/data/technical/transor/index.html
trunk/www.matroska.org/data/technical/transor/transor-conf.html
trunk/www.matroska.org/data/technical/transor/transor-conf.xml
Log:
Content: Removed the "S" from the end of "information".
Modified: trunk/www.matroska.org/data/overhead.html
===================================================================
--- trunk/www.matroska.org/data/overhead.html 2004-09-09 17:16:26 UTC (rev 684)
+++ trunk/www.matroska.org/data/overhead.html 2004-09-10 07:53:54 UTC (rev 685)
@@ -27,7 +27,7 @@
<tr><td>64kbps</td><td>800</td><td>1+2+4+0+800 (0.88%)</td><td>1+2+4+5+1600 (0.75%)</td><td>1+2+4+9+2400 (0.67%)</td><td>1+2+4+13+3200 (0.63%)</td><td>1+2+4+17+4000 (0.60%)</td><td>1+2+4+21+4800 (0.58%)</td><td>1+2+4+26+5600 (0.59%)</td></tr>
</tbody>
</table>
-<p><strong>explanations :</strong> This is the overhead introduced by the Block level. There is more overhead in a matroska file, ie the Cluster head (that contains many Blocks) and the file header (containing various meta informations).</p>
+<p><strong>explanations :</strong> This is the overhead introduced by the Block level. There is more overhead in a matroska file, ie the Cluster head (that contains many Blocks) and the file header (containing various meta information).</p>
<p>the first number is the number is the size of the total Block+Data, ie element ID (1), size (1 to 8), Block head (4), lacing (0 to infinite), data</p>
<p>the second number is the pourcentage of overhead for each packet</p>
Modified: trunk/www.matroska.org/data/technical/overhead/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/overhead/index.html 2004-09-09 17:16:26 UTC (rev 684)
+++ trunk/www.matroska.org/data/technical/overhead/index.html 2004-09-10 07:53:54 UTC (rev 685)
@@ -33,7 +33,7 @@
<tr><td>64kbps</td><td>800</td><td>1+2+4+0+800 (0.88%)</td><td>1+2+4+5+1600 (0.75%)</td><td>1+2+4+9+2400 (0.67%)</td><td>1+2+4+13+3200 (0.63%)</td><td>1+2+4+17+4000 (0.60%)</td><td>1+2+4+21+4800 (0.58%)</td><td>1+2+4+26+5600 (0.59%)</td></tr>
</tbody>
</table>
-<p><strong>explanations :</strong> This is the overhead introduced by the Block level. There is more overhead in a matroska file, ie the Cluster head (that contains many Blocks) and the file header (containing various meta informations).</p>
+<p><strong>explanations :</strong> This is the overhead introduced by the Block level. There is more overhead in a matroska file, ie the Cluster head (that contains many Blocks) and the file header (containing various meta information).</p>
<p>the first number is the number is the size of the total Block+Data, ie element ID (1), size (1 to 8), Block head (4), lacing (0 to infinite), data</p>
<p>the second number is the pourcentage of overhead for each packet</p>
Modified: trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html 2004-09-09 17:16:26 UTC (rev 684)
+++ trunk/www.matroska.org/data/technical/specs/tagging/example-audio.html 2004-09-10 07:53:54 UTC (rev 685)
@@ -46,7 +46,7 @@
<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>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>
<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>
@@ -793,7 +793,7 @@
<h2><a name="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 informations 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>
+<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>
<h4>File #1 : CD #1 - Track #1</h4>
@@ -1366,7 +1366,7 @@
<ul>
<li>Tag
<ul>
- <li>Targets (<em>tagging the volume informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the volume information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 70</em></li>
<li><em>TargetType = "COLLECTION"</em></li>
@@ -1395,7 +1395,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 60</em></li>
<li><em>TargetType = "VOLUME"</em></li>
@@ -1430,7 +1430,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 50</em></li>
<li><em>TargetType = "ALBUM"</em></li>
@@ -1534,7 +1534,7 @@
<ul>
<li>Tag
<ul>
- <li>Targets (<em>tagging the volume informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the volume information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 70</em></li>
<li><em>TargetType = "COLLECTION"</em></li>
@@ -1563,7 +1563,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 60</em></li>
<li><em>TargetType = "VOLUME"</em></li>
@@ -1598,7 +1598,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 50</em></li>
<li><em>TargetType = "ALBUM"</em></li>
@@ -1690,7 +1690,7 @@
<ul>
<li>Tag
<ul>
- <li>Targets (<em>tagging the volume informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the volume information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 70</em></li>
<li><em>TargetType = "COLLECTION"</em></li>
@@ -1719,7 +1719,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 60</em></li>
<li><em>TargetType = "VOLUME"</em></li>
@@ -1754,7 +1754,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 50</em></li>
<li><em>TargetType = "ALBUM"</em></li>
@@ -1900,7 +1900,7 @@
<ul>
<li>Tag
<ul>
- <li>Targets (<em>tagging the volume informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the volume information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 70</em></li>
<li><em>TargetType = "COLLECTION"</em></li>
@@ -1929,7 +1929,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 60</em></li>
<li><em>TargetType = "VOLUME"</em></li>
@@ -2068,7 +2068,7 @@
<ul>
<li>Tag
<ul>
- <li>Targets (<em>tagging the volume informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the volume information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 70</em></li>
<li><em>TargetType = "COLLECTION"</em></li>
@@ -2097,7 +2097,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 60</em></li>
<li><em>TargetType = "VOLUME"</em></li>
@@ -2240,7 +2240,7 @@
<ul>
<li>Tag
<ul>
- <li>Targets (<em>tagging the volume informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the volume information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 70</em></li>
<li><em>TargetType = "COLLECTION"</em></li>
@@ -2269,7 +2269,7 @@
<li>Tag
<ul>
- <li>Targets (<em>tagging the CD informations, no target since it covers the whole file</em>)
+ <li>Targets (<em>tagging the CD information, no target since it covers the whole file</em>)
<ul>
<li><em>TargetTypeValue = 60</em></li>
<li><em>TargetType = "VOLUME"</em></li>
Modified: trunk/www.matroska.org/data/technical/specs/tagging/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-09-09 17:16:26 UTC (rev 684)
+++ trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-09-10 07:53:54 UTC (rev 685)
@@ -241,9 +241,9 @@
<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>
-<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>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 information 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>
+<p>We also need an official list simply for developpers to be able to display relevant information 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>
@@ -268,7 +268,7 @@
<h2><a name="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 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 information about the album it comes from and even the CD set even if it's not found in the file.</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>
@@ -303,7 +303,7 @@
<div class="techdef">
<table>
<tr>
- <th colspan="5"><a name="original"/>Nesting Informations (tags containing other tags)</th>
+ <th colspan="5"><a name="original"/>Nesting Information (tags containing other tags)</th>
</tr>
<tr>
<td>ORIGINAL</td>
@@ -318,7 +318,7 @@
<tr>
<td>COUNTRY<a name="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 informations about the item. All tags in this list can be used "under" the COUNTRY_SPECIFIC tag like LABEL, PUBLISH_RATING, etc.</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>
<tr><th colspan="3" style="color: #f00;">Colour coding</th></tr>
<tr class="subjective" style="text-align: center"><td colspan="3">subjective information</td></tr>
@@ -357,7 +357,7 @@
<td>Sub Title of the entity.</td>
</tr>
<tr>
- <th colspan="5"><a name="original"/>Nested Informations (tags contained in other tags)</th>
+ <th colspan="5"><a name="original"/>Nested Information (tags contained in other tags)</th>
</tr>
<tr>
<td>URL<a name="URL" id="URL"/></td>
Modified: trunk/www.matroska.org/data/technical/specs/tagging/oldtags.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/oldtags.html 2004-09-09 17:16:26 UTC (rev 684)
+++ trunk/www.matroska.org/data/technical/specs/tagging/oldtags.html 2004-09-10 07:53:54 UTC (rev 685)
@@ -83,7 +83,7 @@
<td>-</td>
<td>-</td>
<td>sub-elements</td>
- <td>Contains general informations about the target.</td>
+ <td>Contains general information about the target.</td>
</tr>
<tr>
<td>ArchivalLocation<a name="ArchivalLocation"
Modified: trunk/www.matroska.org/data/technical/transor/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/transor/index.html 2004-09-09 17:16:26 UTC (rev 684)
+++ trunk/www.matroska.org/data/technical/transor/index.html 2004-09-10 07:53:54 UTC (rev 685)
@@ -67,7 +67,7 @@
<h2>Format of the XML transors list file</h2>
-<p>The informations we need about a transor:</p>
+<p>The information we need about a transor:</p>
<ul>
<li>The file path</li>
<li>The name</li>
Modified: trunk/www.matroska.org/data/technical/transor/transor-conf.html
===================================================================
--- trunk/www.matroska.org/data/technical/transor/transor-conf.html 2004-09-09 17:16:26 UTC (rev 684)
+++ trunk/www.matroska.org/data/technical/transor/transor-conf.html 2004-09-10 07:53:54 UTC (rev 685)
@@ -46,7 +46,7 @@
<body>
<span> <span class="S9"><!-- all elements+values sent to the transor might be taken in account --></span><span class="S0"><br /></span>
<span class="S0"><br /></span>
-<span onclick="toggle('ln3')">-</span> <span class="S9"><!-- one should retrieve the informations after setting, in order to verify that<br /></span>
+<span onclick="toggle('ln3')">-</span> <span class="S9"><!-- one should retrieve the information after setting, in order to verify that<br /></span>
<span id="ln3"> <span class="S9">setting the value worked --></span><span class="S0"><br /></span></span>
<span class="S0"><br /></span>
<span onclick="toggle('ln6')">-</span> <span class="S1"><transor></span><span class="S0"><br /></span>
Modified: trunk/www.matroska.org/data/technical/transor/transor-conf.xml
===================================================================
--- trunk/www.matroska.org/data/technical/transor/transor-conf.xml 2004-09-09 17:16:26 UTC (rev 684)
+++ trunk/www.matroska.org/data/technical/transor/transor-conf.xml 2004-09-10 07:53:54 UTC (rev 685)
@@ -1,6 +1,6 @@
<!-- all elements+values sent to the transor might be taken in account -->
-<!-- one should retrieve the informations after setting, in order to verify that
+<!-- one should retrieve the information after setting, in order to verify that
setting the value worked -->
<transor>
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.