On 13 January 2011 14:20, tamanaco <[email protected]> wrote: > > awy;602158 Wrote: >> I guess that the Moose author needs to diagnose what is going wrong. >> >> Looking at the Moose home pages it says that it just uses the CLI. It >> could be that file URLs have changed format but metdata (Artist, Album, >> ...) should still be in the same format: URL-encoded UTF-8. > > I just posted on one of the Moose threads asking the author to comment > on this issue.
Hey guys, sorry for the delay/absence.. Right.. I've yet to pin down exactly what's going on, but there do seem to be numerous inconsistencies with the CLI and escaping.. Even in a simple status reply to playing the radio I get two versions of the same string: current_title%3AAndr%C3%A9%20Schneider%2C%20ehemaliger%20WEF-Direktor%20by%20Schweizer%20Radio%20DRS%20from%20Focus title%3AAndr%C3%83%C2%A9%20Schneider%2C%20ehemaliger%20WEF-Direktor%20by%20Schweizer%20Radio%20DRS%20from%20Focus The second one here's double-escaped but the first one isnt.. Which of these is actually what it should be doing ? I've got functions to handle both of these formats, it's just knowing which to call.. Back at version 0.69 of moose i swapped my decoding methods as the escaping all changed. Swapping back seems to fix things somewhat, but breaks other things.. My current theory is to run the string through a DecodeUtf8String function, then if there are any 0xc2 or 0xc3 binary characters followed by a TBS character, run it through a DecodeUtf8BinaryString to fix any doubly encoded chars. This seems to work with both the above quite nicely, and possibly with everything else.. Just a bit worried if it's going to break something.. -- - Dr Lovegrove http://www.rusticrhino.com/drlovegrove http://groups.google.com/group/moosenews _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
