• Bug#266052: jack: doesn't support UTF8 freedb entries

    From [email protected]@1:229/2 to All on Mon Aug 16 16:40:11 2004
    Package: jack
    Version: 2.99.7-7

    jack doesn't cope properly with CDs whose track titles have non ISO-8859-1 characters in them. (For example, this one: http://www.freedb.org/freedb_search_fmt.php?cat=misc&id=6f071b0a
    NB that you might have to explicitly tell your web browser that the
    page is in UTF8.)

    The effect is that all non-ISO-8859-1 characters are displayed as
    '?' characters in the display and also in filenames on disk, even
    when the user's locale is set to a UTF8 locale.

    The cause of this is that jack is querying cddb using protocol level 3,
    whereas you need level 6 to get UTF8 responses. Protocol docs are here: http://www.freedb.org/modules.php?name=Sections&sop=viewarticle&artid=28
    with a bit near the bottom about what changed in 4,5,6. There are some
    other changes which need to be handled by jack as well as the UTF8,
    like the way that you can now get 210 responses to the query command.

    I made a quick hack change to my copy of jack so it used protocol
    level 6, and it seems to work OK in that tracks are written to disk
    with the correct UTF8 filenames and displayed on screen correctly
    too. NB that I haven't tested what happens if the user's locale is
    not UTF8. However, the display is now a bit mangled because the
    layout code doesn't cope with the concept that some characters are
    double width, so that needs fixing.

    Although I'm using 2.99.7-7, I had a quick look at the source for
    3.0.0-5 and it still seems to use protocol level 3.

    Peter Maydell


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)