Comment 36 for bug 1817395

Revision history for this message
Terry Belton (tezzy) wrote :

Daniel wrote:
[quote]
Cool, we are getting close. I can look into it tonight. If you have time before, I suggest to place addition qDebug() or printf() calls to the code or use gdb to set bteakpoints. Do you have gdb experiences? I use eclipse and gdb for debugging
[/quote]

I don't know how to place additional qDebug() or printf() calls to the code or use gdb to set breakpoints.
I have no eclipse or gdb experience.

Daniel wrote:
[quote]
An other issue:
It looks like we utf8 encoding is broken as well. If I send a cyrilic track,
Only ?,?,... is displayed in Totem.
I cannot imagine how this should work.
[/quote]

Can you post an example MP3 file so I can look into it?

Daniel wrote:
[quote]
The URL containing the metadata is already percent encoded, so what is the point of setting the charset.

Can you point me to a document that explains that?
[/quote]

I saw this page which looks interesting: http://ask.xmodulo.com/convert-mp3-id3-tag-encodings-linux.html

I read this paragraph: Fix Broken Characters in MP3 Song Titles and Artist Names

I looked at https://en.wikipedia.org/wiki/ID3

The point of setting the charset is because ID3v2.4
[quote https://en.wikipedia.org/wiki/ID3]
ID3v2 tags consist of a number of frames, each of which contains a piece of metadata. For example, the TIT2 frame contains the title, and the WOAR frame contains the URL of the artist's website. Frames can be up to 16MB in length, while total tag size is limited to 256MB. The internationalization problem was solved by allowing the encoding of strings not only in ISO-8859-1, but also in Unicode.[/quote]

The wikipedia article continues:

[quote]
ID3v2.4
    v2.4 was published on November 1, 2000, and remains the latest version. It allows textual data to be encoded in UTF-8, which was a common practice in earlier tags (despite the standard, since it was not supported yet) because it has several noticeable advantages over UTF-16. Another new feature allows the addition of a tag to the end of the file before other tags (like ID3v1).[18]
    No version of Windows Explorer or Windows Media Player—up to and including Windows 10 (initial release) and WMP 12, respectively—interprets ID3v2.4 tags correctly. These programs can interpret ID3v2.3 and earlier, however.[19][20] Windows Explorer finally supports reading ID3v2.4 tags with the Windows 10 Creators Update (version 1703).
[/quote]