Using non-ASCII Characters in the Live Meeting service API

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The Live Meeting service API is localized for eight languages including English. There are many strings that only accept ASCII characters (like password and userID). However, there are other strings that accept non-ASCII characters.

The Live Meeting Manager Web interface allows you to enter non-ASCII characters where they are supported. The Live Meeting service API requires a different encoding for non-ASCII characters. The encoding expected by the APIs has the form &#xHHHH; where 'H' is a hexadecimal digit. This encoding can be used for single-byte or multi-byte characters. The hexadecimal value for the character can vary depending on the character set used to display that character.

The following options are allowed to contain non-ASCII characters:

• billing

• company

• firstName

• infoA

• infoP

• lastName

• lobbyMessage

• opaque1

• opaque2

• seatLabelBlue

• seatLabelGreen

• seatLabelPurple

• seatLabelRed

• seatLabelYellow

• seatPrompt

• title

• userName

The following table shows some example names with example encodings.

Example

<PlaceWareConfCenter authUser="apiuser" authPassword="Pa$$w0rd">
<ModifyUserRequest userID="jkranitz">
<OptionList>
<StringOption name="firstName" value="J&#xF3;zsef" /> 
<StringOption name="lastName" value="Kr&#xE1;nitz" /> 
</OptionList>
</ModifyUserRequest>
</PlaceWareConfCenter>

For more information about XML character encoding, see the following documentation:

• Extensible Markup Language (XML) 1.0 (Third Edition)

• Section 2.2 Characters at http://www.w3.org/TR/2004/REC-xml-20040204/\#charsets.

See Also

Concepts

String Restriction and Transformation

Best Practices