Hey all,

I've read many threads here before decided to make a post, because unfortunately I didn't find a solution. I've got a couple issues:

1. Centova cast does not display "&" symbol in the track name, neither in recent played tracks and nor in the current song widgets. The character encoding is set to ISO 8859-2: Latin-2 Europe. The ID3-tags of mp3 files are deleted completely, so it takes the information from the filename, which shouldn't be a problem on my opinion.

2. Was trying to use an undocumented parameter script for recent tracks widget, however it seems not to work for me (widget disappears then).

3. Very important problem: the recent widget plugin doesn't show the information in brackets, e.g. "(DJ XYZ Remix). However it doesn't seem to depend on ID3-Tags editing, because current song widget displays information correctly. Secondary problem, which is associated to the one before I think, is the song request widget. Let's assume I've got 2-3 tracks from same interpret and songname, but different remixes. If I request a certain remix, the widget takes the song, which is alphabetically located as the first, so the information in the brackets put in to the song request form was just ignored.

Someone's got a hint or solution for this problems? Maybe I'm just doing something wrong.

Regards

Dennis

Additional information to issue 3: I've tested an mp3 with editedid3 tag, nothing happened, recent tracks widget still refuses displaying the information in brackets, so that's not the reason

Your host opened a ticket and referred me to this thread -- below are essentially my responses to him.

1. Centova cast does not display "&" symbol in the track name, neither in recent played tracks and nor in the current song widgets. The character encoding is set to ISO 8859-2: Latin-2 Europe. The ID3-tags of mp3 files are deleted completely, so it takes the information from the filename, which shouldn't be a problem on my opinion.

The reliance upon the filename instead of using ID3 tags is the problem here.  Parsing the filenames is a "best effort" procedure and you're not likely to get very good results that way.  Using ID3 tags, ampersands show just fine.

2. Was trying to use an undocumented parameter script for recent tracks widget, however it seems not to work for me (widget disappears then).

Pardon my bluntness here, but in a nutshell that means you did something incorrectly, thereby breaking the JavaScript code for the widget.  You must know (and follow) the rules of JavaScript when making these modifications.

3. Very important problem: the recent widget plugin doesn't show the information in brackets, e.g. "(DJ XYZ Remix).

This is intentional.  Most of the time, any "stuff" appended to the song title is cruft that shouldn't be displayed to visitors (eg: "single", "LP version", "ripped by l33th4x0r", etc.) and we implemented the current song title sanitization system by very popular demand many years ago.  Tonight's build adds a feature to make this optional though.

However it doesn't seem to depend on ID3-Tags editing, because current song widget displays information correctly.

That's because the current song title is pulled straight from the SHOUTcast server without modification.  Also fixed by tonight's build, for consistency.

Secondary problem, which is associated to the one before I think, is the song request widget. Let's assume I've got 2-3 tracks from same interpret and songname, but different remixes. If I request a certain remix, the widget takes the song, which is alphabetically located as the first, so the information in the brackets put in to the song request form was just ignored.

It won't be alphabetical, it will be whatever order MySQL returns the results in -- consider it random.

Unfortunately there's no way around that for the time being.  We may implement an optional JavaScript autocomplete feature for the request widget at some point in the future (the feature requests forum would be a good place to request this) allowing the user to pick which song he means, but for now it works essentially the way you described.