Skip to Content
It is currently March 5th, 2021, 1:59 am

All times are UTC - 6 hours [ DST ]




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: July 30th, 2020, 10:26 am 
Offline
New User
New User

Joined: August 4th, 2010, 1:16 pm
Posts: 4
I'm having trouble sending song info with special characters (Spanish characters like á é ó ñ) to the Icecast's status-json.xsl file (Icecast V2). As you can see in the file attached the characters are not rendered properly.

Attachment:
File comment: Special characters issue
Special-characters-issue.jpg
Special-characters-issue.jpg [ 197.56 KiB | Viewed 1457 times ]


I've tried with an older version of SAM (4.9.1) and the characters are sent properly and they render fine on any web application.

Is there any way to address this issue? I've tried adding the tag
Code:
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
but it seems that this is not something related to the page itself due that the information comes with errors from the json file.

Any help will be greatly appreciated.


Top
 Profile  
Reply with quote  
PostPosted: August 3rd, 2020, 5:22 am 
Offline
SVS Member
SVS Member

Joined: December 6th, 2004, 9:00 am
Posts: 8156
Location: Cologne (Germany)
Does Firebird know the concept of database collations? If so which one is used by SAM and which one is expected by Icecast?
I got too little (close to none) knowledge of Firebird to be able to help here. Maybe you can ask the people on the Firebird mailing list?
https://firebirdsql.org/en/mailing-lists/

For non-english language, there's a bunch of regional forums as well: https://firebirdsql.org/en/regional-sites/

_________________
Benedikt Bauer - SVS (Spacial Volunteer Support)

Shop for readymade PAL scripts by countrywesterndj - Or get a custom script made by me (or others)

My Project:
Send "Now Playing" from SAM to Twitter and/or Facebook | Sourcecode


Top
 Profile  
Reply with quote  
PostPosted: October 22nd, 2020, 10:35 am 
Offline
New User
New User

Joined: October 20th, 2020, 11:45 am
Posts: 7
By the way, is Russian Cyrillic supported by Broadcaster, and if yes, what type of encoding does it use? Because according to the encoding, when trying to display Russian text, it either works, or shows just interrogation marks, or a bunch of Latin letters with diacritic signs looking like this "àçóñĐ".


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC - 6 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot] and 44 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group