Planned Enhancements and Known Bugs
===================================

General
--------
 o Better tag parse exception hierarchy and universal usage.
 o Multiple frames per set: COMM, APIC, etc.  And are TEXT frames mutually
   exclusive????
 o Compression testing on id3lib sample tags.  Currently zlib complains
   about an unsupported compression message.
 o The ability to write tags.  Currently eyeD3 is a reader of tags only.
 o More user friendly Tag.setTextFrame and add Tag.setURLFrame() and
   Tag.setMCDIFrame().
 o Read-only bit must be used to disable set methods.
 o File/tag preservation rules must be followed when saving is added.

ID3 v2.3 Compliance
-------------------
 o Extened headers.
 o UTF-16 encoding (0x01 byte prefix)

ID3 v2.4 Compliance
-------------------
 o Handle appened ID3v2 tags, SEEK frames, and footers.
 o UTF-16BE encoding (0x02 byte prefix).
 o UTF-8 encoding (0x03 byte prefix).

Ogg/Vorbis Compliance
---------------------
 o Parse field/value and incorporate OggTag into eyeD3.
 o Access methods.
 o UTF-8 support.  Currently the strings are interpreted as ISO-8859-1
   which works for every ogg tag I've encountered.
 o Ogg tag writing.

Current Status of id3lib Sample Tags
------------------------------------
230-compressed.tag - Python exception: unknown compression method
230-picture.tag - Not all the APIC image data is being read because it
                  looks as if the frame header is reporting the data
                  size before unsynchronization.  See id3lib mailing
                  list.
230-syncedlyrics.tag - Not tested, synced lyrics has not been implemented
                       yet.
230-unicode - Not tested, encodings other then ISO-8859-1 have not been
              implemented yet.
ozzy.tag - Python exception: unknown compression method.
thatspot.tag - Parses fine, but native support for multiple COMM frames,
               USLT, PCNT, POPM, and IPLS is needed. On a positive note,
               the APIC frame is parsed and generated perfectly!
