Supported Escape Characters for File Endpoint Delimiters

When defining an endpoint for a File type inbound or outbound message service, use the following guidelines:

• Use the \<ASCII character> format.
• Observe case-sensitivity.
• Use any of the following nonprintable and special characters.

  Table 1. Valid escape characters

  Character	Description
  \b	\u0008: backspace
  \t	\u00098: horizontal tab
  \n	\u000a: line feed
  \f	\u000c: form feed
  \r	\u000d: carriage return
  \"	\u0022: double quote
  \'	\u0027: single quote
  \\	\u005c: backslash
  \uXXXX	Unicode escaped character where X is a hexadecimal value. The value range for hex is 0 to Character.MAX_VALUE (\u000 to \uFFFF). The number of bits for a Unicode escaped character is 6, includinig \u. Note: All Unicode escape characters are supported regardless of whether they are supported by your Java compiler. For example, the \u000a Unicode escape character is supported as a substitute for \n (carriage return).
  \X \XX \YXX	Octal escaped character where X is an Octal digit. The value range of X is from 0 to 7 and Y is from 0 to 3. Note: Sybase does not recommend the use of Octal escapes with XML. Its primary use is with C. All Octal escapes can be expressed using Unicode values \u0000 through \u00FF. For the \YXX format, if Y is greater than 3, \YXX is treated as \XX. For example, \455 is treated as an Octal Escape "\45" and "5" separately.