2011/11/15 Martin Konečný <martin.kone...@sourcefabric.org>: > Hi Romain,
Hi, > Ok back to this issue, I didn't really understand your last email, so I went > to other things for a bit. Now I spent some time understanding what you did, > and have a few questions: > You say you have the following configuration in your icecast.xml: > <mount> > <mount-name>/test</mount-name> > <charset>UTF-8</charset> > </mount> > Why do we need to edit the icecast.xml file? When using output.icecast is > creating the mountpoint can it tell icecast what charset to interpret the > text as? > On the icecast documentation page I see the following: >> >> The source clients can also specify a charset= parameter to the metadata >> update URL if they so wish. > > Is it possible to add a "charset" parameter to output.icecast to specify > this? I had originally assumed "encoding" was telling icecast what to > interpret the string of character bits as, but today I found that "encoding" > is actually using chamomile to encode the data. You have to tell icecast to use UTF8 for this mountpoint because it is using latin1 by default for mp3 mountpoints. When you pass a charset=UTF8 parameter to icecast, it tries to convert the given string to its target encoding. Thus for mp3 mountpoints you get a conversion UTF8 -> latin1, which cannot be done with Cyrillic characters, hence the resulting HTML special codes for lack of better alternatives.. If you set UTF8 for this mountpoint in icecast's config, it becomes the new internal targeted encoding. In this case, a UTF8 string is not converted and works perfectly.. Romain ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
