Closed sspiff closed 6 months ago
Not sure if "extended ascii" is the correct classification, but character codes such as 0xe9 (e with acute) and 0xf3 (o with acute) are not displayed properly in LMS in, for example, station names.
When rendering the decoded JSON that comes back from the API, Data::Dumper outputs these character codes as \x{e9} and \x{f3}. In LMS they are displayed as "é" and "ó".
Data::Dumper
\x{e9}
\x{f3}
U+00E9 (unicode e acute) is two bytes in UTF-8: 0xc3 0xa9
U+00E9
U+00F3 (unicode o acute) is two bytes in UTF-8: 0xc3 0xb3
U+00F3
WebService::Pandora::Method is not decoding the JSON returned by the API as UTF-8. Fix pending.
Not sure if "extended ascii" is the correct classification, but character codes such as 0xe9 (e with acute) and 0xf3 (o with acute) are not displayed properly in LMS in, for example, station names.
When rendering the decoded JSON that comes back from the API,
Data::Dumper
outputs these character codes as\x{e9}
and\x{f3}
. In LMS they are displayed as "é" and "ó".U+00E9
(unicode e acute) is two bytes in UTF-8: 0xc3 0xa9U+00F3
(unicode o acute) is two bytes in UTF-8: 0xc3 0xb3