Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 3 of 3
  1. #1
    Jon Watte
    Guest

    Changing charset for web interface

    Changing charset for web interface
    Wouldn't the best way of doing this be to select a charset which can display
    all possible characters? Ideally, this means UTF-8. Of course, you have to
    make sure that the charset of the data you get in (your song titles) is
    know, and convertable to UTF-8.

    Note that just changing the charset in the header, while it might work if
    ALL your track titles are in that particular charset, isn't generally a good
    solution, because you may commonly have tracks with names in multiple
    charsets. The problem here is of course that the ID3 tag doesn't contain a
    common information about what charset is used.

    I've come to wish that everybody would just use UTF-8 everywhere, and it'd
    all Just Work (tm) in the end. All other representations seem to have some
    kind of problem somewhere (Unicode means 2 bytes on Window,s but 4 bytes on
    UNIX, and has byte order problems, for example).

    Cheers,

    / h+

    -----Original Message-----
    From: discuss-bounces (AT) lists (DOT) slimdevices.com
    [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com]On Behalf Of Meshoulam, Arnon
    Sent: Monday, July 05, 2004 11:38 AM
    To: discuss (AT) lists (DOT) slimdevices.com
    Subject: [slim] Changing charset for web interface


    All,

    I want to change the web interface to support international characters.
    All it entails is changing the page charset in 3 of the web pages.

    This will allow support of international characters in the
    songs/artists/albumns - in my case - Hebrew.

    However, I don't want to implement it as a new language as the interface
    is still in English, and I want it to apply to all the skins.

    Any ideas on how to implement it?

    Arnon

  2. #2
    Michael Brouwer
    Guest

    Changing charset for web interface

    Both the FLAC and MP3 tag reading code can produce tags in utf8 form.
    I've suggested before that it would probably be a good idea for
    slimserver to store all tags in utf8 internally and convert to latin1
    (for the squeezebox) as late as possible. Thus enabling support for
    other languages in the web interface.

    If I can find some spare time I might whip up a patch. However this is
    most likely going to make slimserver depend on perl 5.8. Is this
    acceptable or are we still required to have everything work on perl
    5.6?

    Michael

    On Jul 5, 2004, at 2:20 PM, Jon Watte wrote:

    >
    > Wouldn't the best way of doing this be to select a charset which can
    > display all possible characters? Ideally, this means UTF-8. Of course,
    > you have to make sure that the charset of the data you get in (your
    > song titles) is know, and convertable to UTF-8.
    >
    > Note that just changing the charset in the header, while it might work
    > if ALL your track titles are in that particular charset, isn't
    > generally a good solution, because you may commonly have tracks with
    > names in multiple charsets. The problem here is of course that the ID3
    > tag doesn't contain a common information about what charset is used.
    >
    > I've come to wish that everybody would just use UTF-8 everywhere, and
    > it'd all Just Work (tm) in the end. All other representations seem to
    > have some kind of problem somewhere (Unicode means 2 bytes on Window,s
    > but 4 bytes on UNIX, and has byte order problems, for example).
    >
    > Cheers,
    >
    > / h+
    >
    > -----Original Message-----
    > From: discuss-bounces (AT) lists (DOT) slimdevices.com
    > [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com]On Behalf Of Meshoulam,
    > Arnon
    > Sent: Monday, July 05, 2004 11:38 AM
    > To: discuss (AT) lists (DOT) slimdevices.com
    > Subject: [slim] Changing charset for web interface
    >
    >
    > All,
    >
    > I want to change the web interface to support international
    > characters. All it entails is changing the page charset in 3 of the
    > web pages.
    >
    > This will allow support of international characters in the
    > songs/artists/albumns - in my case - Hebrew.
    >
    > However, I don't want to implement it as a new language as the
    > interface is still in English, and I want it to apply to all the
    > skins.
    >
    > Any ideas on how to implement it?
    >
    > Arnon
    >

  3. #3
    Gadfly, Former Founder Slim Devices dean's Avatar
    Join Date
    Apr 2005
    Location
    San Francisco, CA
    Posts
    4,427

    Changing charset for web interface

    Hi Michael,

    Yes, we'll need (for the time being) to keep compatibility back to
    5.6.0 in order to support Mac OS X below version 10.3.

    Let's take this discussion to the developer list and talk about how we
    might progress, I'd love to see utf8 support added soon.

    -dean

    On Jul 6, 2004, at 4:32 PM, Michael Brouwer wrote:

    > Both the FLAC and MP3 tag reading code can produce tags in utf8 form.
    > I've suggested before that it would probably be a good idea for
    > slimserver to store all tags in utf8 internally and convert to latin1
    > (for the squeezebox) as late as possible. Thus enabling support for
    > other languages in the web interface.
    >
    > If I can find some spare time I might whip up a patch. However this
    > is most likely going to make slimserver depend on perl 5.8. Is this
    > acceptable or are we still required to have everything work on perl
    > 5.6?
    >
    > Michael
    >
    > On Jul 5, 2004, at 2:20 PM, Jon Watte wrote:
    >
    >>
    >> Wouldn't the best way of doing this be to select a charset which can
    >> display all possible characters? Ideally, this means UTF-8. Of
    >> course, you have to make sure that the charset of the data you get in
    >> (your song titles) is know, and convertable to UTF-8.
    >>
    >> Note that just changing the charset in the header, while it might
    >> work if ALL your track titles are in that particular charset, isn't
    >> generally a good solution, because you may commonly have tracks with
    >> names in multiple charsets. The problem here is of course that the
    >> ID3 tag doesn't contain a common information about what charset is
    >> used.
    >>
    >> I've come to wish that everybody would just use UTF-8 everywhere, and
    >> it'd all Just Work (tm) in the end. All other representations seem to
    >> have some kind of problem somewhere (Unicode means 2 bytes on
    >> Window,s but 4 bytes on UNIX, and has byte order problems, for
    >> example).
    >>
    >> Cheers,
    >>
    >> / h+
    >>
    >> -----Original Message-----
    >> From: discuss-bounces (AT) lists (DOT) slimdevices.com
    >> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com]On Behalf Of Meshoulam,
    >> Arnon
    >> Sent: Monday, July 05, 2004 11:38 AM
    >> To: discuss (AT) lists (DOT) slimdevices.com
    >> Subject: [slim] Changing charset for web interface
    >>
    >>
    >> All,
    >>
    >> I want to change the web interface to support international
    >> characters. All it entails is changing the page charset in 3 of the
    >> web pages.
    >>
    >> This will allow support of international characters in the
    >> songs/artists/albumns - in my case - Hebrew.
    >>
    >> However, I don't want to implement it as a new language as the
    >> interface is still in English, and I want it to apply to all the
    >> skins.
    >>
    >> Any ideas on how to implement it?
    >>
    >> Arnon
    >>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •