Introduction: By editing this section, you can localize the window which appears in the customer's computer when he/she calls an agent with the Call Button.

Example: In the localePager.cfg file, this section is as follows:

l2.1=You are contacting $_1...
l2.2=Call now
l2.3=Cancel
l2.4=Leave message
l2.5=Required field !

Localization steps: In order to localize the Call Button in your local language, you will need to translate the values 'You are contacting', 'Call now', 'Cancel', 'Leave message' and 'Required field' to your local language. The numbers of the parameters, namely, l2.1,...l2.5 should not be changed as they are connected to the applet configuration.

 

Introduction: By editing this section, you can localize the the window in which your customers will be able to leave a message for your agents in case your agents are offline or busy.

Example: In the localePager.cfg file, this section is as follows:

l3.1=$_1 is not available at this time. You can leave a text message.
l3.2=Message from $_1:
l3.3=Click here to leave a voice message
l3.4=Send
l3.5=Close
l3.6=Please type a text message in the text area.
l3.7=Message sent properly.

Localization steps: In order to localize the Call Button in your local language, you will need to translate the values 'is not available at this time. You can leave a text message', 'Message from', 'Click here to leave a voice message', 'Send', 'Close', 'Please type a text message in the text area' and 'Message sent properly' to your local language. The numbers of the parameters, namely, l3.1,...l3.7 should not be changed as they are connected to the applet configuration.

 

Introduction: By editing this section, you can localize the chat window with which your agent will communicate with your customer.

Example: In the localePager.cfg file, this section is as follows:

# Chat window
l4.1=To $_1
l4.2=Close
l4.3=Message :
l4.4=Send
l4.5=$_1 wants to launch the '$_2' with you.
l4.6=Accept
l4.7=Reject
l4.8=>> $_1 has closed the chat window.
l4.9=>> $_1 beeps you !
l4.10=>> You are now in super secure mode.
l4.11=>> You are not in super secure mode anymore.
l4.12=$_1 wants to send you the file $_2 (file size $_3 KB).
l4.13=>> Downloading the file $_1...

Localization steps: In order to localize the Call Button in your local language, you will need to translate the values 'To', 'Close', 'Message', 'Send', 'wants to launch the .. with you', 'Accept', 'Reject', 'has closed the chat window', 'beeps you', 'You are now in super secure mode', 'wants to send you the file', 'file size' and 'Downloading the file' to your local language. The numbers of the parameters, namely, l4.1,...l4.13 should not be changed as they are connected to the applet configuration.

 

Steps to localize the CallSite Application:

To translate your CallSite to any language:

• translate the localePager.cfg file to any language using the Native-to-ASCII Converter tool of Sun Microsystems to do the conversion. This tool is available as a utility with the JDK (in the directory '/jdk1.x/bin/'). Complete documentation about how to use this tool is available in the following web pages: http://java.sun.com/j2se/1.3/docs/tooldocs/win32/native2ascii.html (for windows OS), http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/native2ascii.html (for Unix/solaris OS)
• rename it to: localePager.YOURLANGUAGE.cfg
• upload it to your applet directory ('/callsite/applet/')
• modify the value of the locale parameter, as shown below in your HTML page containing your CallSite Call Button applet:
  
  <param name="locale" value="localePager.YOURLANGUAGE.cfg">