https://bugs.kde.org/show_bug.cgi?id=432583
--- Comment #2 from seb.lebre...@gmail.com --- Hi, sorry for my late reply. Yes I eventually figured out that I can see the language by clicking "Edit..." so I made it work like this. I also figured out where my 'XXX' COMMENT frame come from, it's because of AUDACITY which messes up several tags when exporting a modified track : - new COMMENT with 'XXX' language - duplicated DATE - new "unknown text information" tag with the value from COMPILATION - new "BAND" tag with the value from ALBUM ARTIST I'm often editing files to remove glitches, or split/cut them, so that's why I ended up having so many of these weird double COMM files. I'll file some bugs on their tracker, but maybe this info can be helpful for others and can help give more weight to my suggestion of adding a second (smaller) line, in the table, below the frame name, which could display its language, or encoding, or whatever additional detail is available. It's definitely not critical since "Edit..." gets me the info, but it would be a nice addition. Thanks ! (In reply to Urs Fleisch from comment #1) > You can view the details when you are in the comment and click the "Edit..." > button. A dialog will appear where you can see all fields of the frame > including the "Language" field. > > When the "COMM" frame has a non empty "Description" field, it is used as the > name in the table, so you can differentiate between comments with a > description. Having multiple "COMM" frames without "Description" but with > different "Language" seems rather unusual. I would expect to be able to > differentiate from the language used in their content. The space in the > table is limited, therefore the "Language" is not visible there, but you can > always go into the edit dialog if you need to see the details. -- You are receiving this mail because: You are watching all bug changes.
