View previous topic :: View next topic |
Author |
Message |
dimajak
Joined: 11 Sep 2008 Posts: 7
|
Posted: Thu Sep 11, 2008 2:09 pm Post subject: <charset> |
|
|
Tag <charset></charset> work in <mount>, but not work in <relay>.
It is necessary to create in addition <mount>. |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Sep 11, 2008 10:27 pm Post subject: |
|
|
it's not a relay setting, but a mount setting. For non-ogg streams latin1 is assumed because most use that but a simple <mount-name> and <charset> can be the only options specified in mount for something other than latin1.
karl. |
|
Back to top |
|
|
dimajak
Joined: 11 Sep 2008 Posts: 7
|
Posted: Fri Sep 12, 2008 2:40 pm Post subject: |
|
|
I know, that <charset> for section <mount>.
But if to create <mount> and relayed station it is switched off, it will be present at my list.
And at this station the name current songs goes not in the coding latin1 (CP1251). Therefore it was necessary to create <mount> for this station.
P.S. sorry for my english. |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Fri Sep 12, 2008 9:23 pm Post subject: |
|
|
Which list are you referring to. A mount block just provides some settings for a mountpoint.
karl. |
|
Back to top |
|
|
dimajak
Joined: 11 Sep 2008 Posts: 7
|
Posted: Sat Nov 01, 2008 2:35 pm Post subject: |
|
|
I call on a main page IceCast Server.
Station, prescribed in <mount> will be always shown on a main page. Correctly?
And if is not the station now accessible?
Then it is not needed that she was represented.
I create the tag of <mount> only from the tag of <charset>. |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sat Nov 01, 2008 7:57 pm Post subject: |
|
|
Are you talking about an on-demand relay? Where a relay will connect then there is at least 1 listener.
Yes, to change the assumed character set you need to use the <charset> tag in mount (along with a <mount-name> to identify the stream name to match). Nothing else is required in <mount> for this.
karl. |
|
Back to top |
|
|
dimajak
Joined: 11 Sep 2008 Posts: 7
|
Posted: Fri Dec 12, 2008 3:46 pm Post subject: |
|
|
Wished to do without <mount>, only <relay> and inside <relay> to use a tag <charset>. |
|
Back to top |
|
|
yarajii
Joined: 21 Jul 2009 Posts: 3
|
Posted: Tue Jul 21, 2009 7:38 am Post subject: |
|
|
I have been using this wonderfull streaming server for several years in
Japanese language. With related above encoding problem, I cannot
update to Icecast 2.3.2.
I feel really eager to use that "supported multipul ports of Shoutcast source" connections.
-WinXP SP3 Japanese with Icecast,
-Connecting from Shoutcast source and/or m3w streamer.
*2.3.1 is working fine to show Japanese letters unless any configuration.
*With 2.3.2, source client connected with http,
-To set <charset>"UTF-8" or "ISO-2022-JP" inside <mount>, then some article of status.xsl
are not displayed.
-To set <charset>"Shift_JIS" inside <mount>, then status.xsl is fine same as 2.3.1.
-Then this is goal for me, with 2.3.2, source client(s) connected with Icy,
multipul ports by Icy could be succeeded, but Japanese letters are broken
with the Stream Title/Genre and Current songs in status.xsl.
*I have tried to change the encoding in status.xsl, but not worked.
As this was based on explained before, I recognize current specification of that. I also hope
something charcter encoding control would be expanded, such as control for "Shoutcast mounts"
or all mount points.
Best regards, |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Jul 21, 2009 11:21 am Post subject: |
|
|
You seem to be referring to 2 different parts of icecast. It sounds like you have resolved the charset problem by using the Shift_JIS charset to convert the incoming metadata to utf8.
The second point you talked about was the shoutcast connections. All you need for that is a <shoutcast-mount> inside the <listen-socket>.
karl. |
|
Back to top |
|
|
yarajii
Joined: 21 Jul 2009 Posts: 3
|
Posted: Tue Jul 21, 2009 12:03 pm Post subject: |
|
|
Dear KarlH,
Thank you for your comments, and sorry for my poor expression on the
problem.
These are OK, and now working fine with 2.3.2.
-To show Japanese letters in status.xsl, in case of http connections(to put <charset>
inside <mount>
-To connect multipul session with Shoutcast compatible(Icy) mode.
*In any case, at listner client like Winamp can show Japanse letters correctly.
As I have not enough skill to make original page, such as used with php to get Icecast info.
So that I am using modified Status.xsl for my client listners to check someone's radio start or not.
The problem is when it connect with Icy protocol, I have no way to make Status.xsl can display
Japanese letters correctly, because <charset> inside <listen-socket> doesn't make sense.
-2.3.1 can handle Japanese letters without any settings.
I'd appreciated if you give me any beautiful idea.
Thank you,
yarajii |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Jul 21, 2009 1:31 pm Post subject: |
|
|
When you request an xsl page then you use the http protocol not icy. The whole idea of charset is to convert whatever characters are coming in into utf8 so that the stats work without having conflicting character sets. If you write an xsl page then fine, but those stats should be in utf8 not say Shift_JIS.
karl. |
|
Back to top |
|
|
|