Server Side

Actions:
serveMP3
downloadfile
dir
phpinfo
feedPlaylist
getCoverart
podcast

Directives:
wimpyConfigFile
media_types
wimpy_auth
getMyid3info
ecommerce
ecomWindow
useMysql
defaultVisualBaseName
defaultVisualExt
hide_folders
hide_files
startDir
getid3libPath
httpOption
blockPHPinfo

Client Side

wimpyApp
wimpySkin
startPlayingOnload
randomOnLoad
shuffleOnLoad
displayDownloadButton
autoAdvance
popUpHelp
forceDownload
startOnTrack
trackPlays
voteScript
getMyid3info
forceXMLplaylist
useSysCodePage
ecommerce
ecomWindow
useMysql
scrollInfoDisplay
infoDisplayTime
bufferAudio
theVolume
defaultImage
loopPlaylist
limitPlaytime
startupLogo

HTML display

wimpySkin
wimpySwf
bkgdColor
tptBkgd
wimpyHTMLpageTitle
useSysCodePage

useSysCodePage

useSysCodePage -- Causes the player to display double-byte characters (e.g. Chinese character sets).

Usage

wimpy.swf?useSysCodePage=yes

Parameters

yes - enables localized doublebyte characters
no - disables localized doublebyte characters

This option defaults to "no"
You can either explicitly set this option to "yes" or "no" or simply do not include this option when loading the player and Wimpy will use the "default" value.

Description

This option should allow special glyphs, characters and symbols to display correctly within the player.

Arabic, Asian, Cyrillic and some European Languages use unique characters that are not included in the standard Western Latin (English) character set (e.g. latin-1, ISO-8859-1).

If this option is set to "yes" Wimpy interprets text data using the traditional code page of the operating system running the player.

If this option is set to "no" Wimpy interprets text data using UTF-8 character encoding.

Since this option is based on the end-users system, setting this option to "yes" could still cause certain characters to display improperly. This option should only be set when the majority of the end-users that view the player use a common character set.

Also, by default PHP interprets text data as UTF-8 encoding, ASP and ColdFusion default to ISO-8859-1, so if your web site is hosted on a server that was set up using the default UTF-8 character encoding, this option may have no affect.

If you are using an XML playlist, you may want to consider adding a character description to the beginning of the playlist.xml file to define the proper text encoding.

Example:

<?xml version="1.0" encoding="windows-1251"?>
<playlist>
    <item>
      yada yada
    </item>
</playlist>

NOTE: Use this option with care. It is best to use UTF-8 encoding whenever possible

Example:

<?xml version="1.0" encoding="UTF-8"?>
<playlist>
    <item>
      yada yada
    </item>
</playlist>

See Also:

Using non-western characters

Multibyte String Functions

XML playlists

URL encoding text

.