Space in tags

[GoogleCodeExporter]

From names of tags containing spaces, ie the Txxx tag "album artist", only
the first word shows up. Especially in the case of this example this tag
shows up as "album" which as you see is sort of confusing. Also when adding
a custom tag as an entry for a column in preferences-->songlist-->others
there is no way of entering tag that contain whitespaces. Adding the tag
"album artist" with and (without quotes) makes it show up as a column
called artist and a column called album.

Btw i'm using quodlibet 2.0 from the ubuntu jaunty repositories.

Original issue reported on code.google.com by jeroen.l...@gmail.com on 27 May 2009 at 4:16

[GoogleCodeExporter]

While ID3v2.4 supports whitespace in TXXX frames, Vorbis comments do not permit
whitespace in keys (tag names), so Quod Libet wasn't designed to support 
whitespace
in keys when it comes to things like the column list and queries. To encourage
consistency, I don't think these should be supported, either, although there 
may be
ways to handle existing files with these tags better.

In the meantime, I suggest that you use "albumartist", which is supported 
natively by
Quod Libet.

Original comment by steven.strobe.cc@gmail.com on 28 May 2009 at 12:39

• Added labels: Component-Library, Priority-Low, Type-Enhancement
• Removed labels: Priority-Normal, Type-Defect

[GoogleCodeExporter]

After considering this, I can't find any good ways in which to extend support 
for
this without overcomplicating things. Most commonly-used tags are supported via 
QL
directly and will map properly without using whitespace.

Original comment by steven.strobe.cc@gmail.com on 15 Aug 2009 at 5:35

• Changed state: WontFix

[GoogleCodeExporter]

<blockquote>While ID3v2.4 supports whitespace in TXXX frames, Vorbis comments 
do not 
permit
whitespace in keys (tag names)</blockquote>
Just reading up on this, and the Vorbis Comment spec 
(http://www.xiph.org/vorbis/doc/
v-comment.html) seems to say that of your standard ASCII charcters, only = and 
~ are 
excluded; spaces (0x20) are OK. Spaces don't seem to be used in the spec for 
anything else, so it shouldn't complicate things too badly, should it?

Original comment by jarrad.w...@gmail.com on 22 Oct 2009 at 3:33