Dolf Dijkstra
2004-05-13, 02:14
>
> That's true, but SlimServer does support the Latin-1 subset. For
> iTunes and MP3 files, SlimServer takes the unicode text and extracts
> the Latin-1 versions from that. We should update SlimServer
> to, first,
> do the same with Ogg & FLAC tags, then later, add support for full
> UTF8.
>
As pointed out early by Larry, UTF-8 is only part of the puzzle. The
next step is the locale for sorting. Meaning that a slashed-O should
sort in the O range in some locales (for instance utf8.swedish_sweden)
but maybe not in others (or in others users preferences).
Dean: do you have any timeline when to expect UTF-8 handling for
flac/ogg comments and Utf-8 http responses? I am well aware that
'yesterday' is not possible :) I just want to make sure it is on the
radar.
Is there an open bug for this already? If not I will open one.
Please be aware that ISO-8859 is not a subset of UTF-8. For instance:
the copyright character in ISO-8859 does not exists in UTF-8 at the same
code-point.
I am more interested in correct browser display and sorting routines
then squeezebox display, though an extended, but simplified (display a
slashed-O as an O), font for squeeze might quickly solve this issue
once slim is doing UTF-8.
Thx
Dolf
> That's true, but SlimServer does support the Latin-1 subset. For
> iTunes and MP3 files, SlimServer takes the unicode text and extracts
> the Latin-1 versions from that. We should update SlimServer
> to, first,
> do the same with Ogg & FLAC tags, then later, add support for full
> UTF8.
>
As pointed out early by Larry, UTF-8 is only part of the puzzle. The
next step is the locale for sorting. Meaning that a slashed-O should
sort in the O range in some locales (for instance utf8.swedish_sweden)
but maybe not in others (or in others users preferences).
Dean: do you have any timeline when to expect UTF-8 handling for
flac/ogg comments and Utf-8 http responses? I am well aware that
'yesterday' is not possible :) I just want to make sure it is on the
radar.
Is there an open bug for this already? If not I will open one.
Please be aware that ISO-8859 is not a subset of UTF-8. For instance:
the copyright character in ISO-8859 does not exists in UTF-8 at the same
code-point.
I am more interested in correct browser display and sorting routines
then squeezebox display, though an extended, but simplified (display a
slashed-O as an O), font for squeeze might quickly solve this issue
once slim is doing UTF-8.
Thx
Dolf