remove id3 support from the plugins
diff --git a/doc/html/changelog.html b/doc/html/changelog.html
index bc9100f..3b5cf76 100644
--- a/doc/html/changelog.html
+++ b/doc/html/changelog.html
@@ -160,6 +160,7 @@
<LI>Speed optimization in ReplayGain synthesis.</LI>
<LI>Speed optimization in XMMS playback.</LI>
<LI>Support for big-endian architectures in XMMS plugin.</LI>
+ <LI>Removed support for ID3 tags.</LI>
<LI>Bug fix: make hard limiter default to off in XMMS plugin.</LI>
<LI>Bug fix: stream length calculation bug in XMMS plugin, debian bug #200435; <A HREF="http://sourceforge.net/mailarchive/forum.php?thread_id=2733072&forum_id=6312">see also</A>.</LI>
<LI>Bug fix: small memory leak in XMMS plugin.</LI>
diff --git a/doc/html/documentation.html b/doc/html/documentation.html
index 100338d..bbdd204 100644
--- a/doc/html/documentation.html
+++ b/doc/html/documentation.html
@@ -189,7 +189,7 @@
<B>MISCELLANEOUS</B>
</P>
<P>
- In order to support come common types of metadata, the reference decoder knows how to skip <A HREF="http://www.id3.org/">ID3v1 and ID3v2 tags</A>. Note however that the FLAC specification does not require compliant implementations to support ID3 in any form. The XMMS and Winamp plugins support them out of convenience but other applications need not.
+ As a convenience, the reference decoder knows how to skip <A HREF="http://www.id3.org/">ID3v1 and ID3v2 tags</A>. Note however that the FLAC specification does not require compliant implementations to support ID3 in any form and their use is discouraged.
</P>
<P>
<B><TT>flac</TT></B> has a verify option <TT>-V</TT> that verifies the output while encoding. With this option, a decoder is run in parallel to the encoder and its output is compared against the original input. If a difference is found <B><TT>flac</TT></B> will stop with an error.
diff --git a/doc/html/faq.html b/doc/html/faq.html
index 9c8fb19..e522580 100644
--- a/doc/html/faq.html
+++ b/doc/html/faq.html
@@ -211,7 +211,7 @@
FLAC has it's own native tagging system which is identical to that of Vorbis. They are called alternately "FLAC tags" and "Vorbis comments". It is the only tagging system required and guaranteed to be supported by FLAC implementations.
</P>
<P>
- Out of convenience, some plugins and implementations allow and also read other kinds of tags. For example, the official FLAC Winamp and XMMS plugins can also read ID3 v1 and v2 tags in addition to FLAC tags. The reference decoder knows how to skip ID3 tags so that they don't interfere with decoding. But you should not expect any tags beside FLAC tags to be supported in all applications; some implementations may not even be able to decode a FLAC file with ID3 tags.
+ Out of convenience, the reference decoder knows how to skip ID3 tags so that they don't interfere with decoding. But you should not expect any tags beside FLAC tags to be supported in applications; some implementations may not even be able to decode a FLAC file with ID3 tags.
</P>
<P>
<A NAME="general__software"><B>What software support FLAC?</B></A>
diff --git a/doc/html/format.html b/doc/html/format.html
index 8a7d6aa..4265e35 100644
--- a/doc/html/format.html
+++ b/doc/html/format.html
@@ -312,9 +312,6 @@
All numbers used in a FLAC bitstream are integers; there are no floating-point representations. All numbers are big-endian coded. All numbers are unsigned unless otherwise specified.
</P>
<P>
- A FLAC bitstream may be appended with ID3V1 data or prepended with ID3V2 data. FLAC has no knowledge of such data, but the reference decoder knows how to skip an ID3 tag.</A>
- </P>
- <P>
Before the formal description of the stream, an overview might be helpful.
</P>
<UL>