File encodings

Text written by Rational® Synergy to the standard output and standard error streams is in the system default encoding. Text read by Rational Synergy from the standard input stream is assumed to be in the same system default encoding.

Therefore, scripts using the CLI might not support attribute values from multiple locales because many encodings cannot simultaneously represent both Chinese and Japanese characters, for example.

On Windows, programs might read command-line parameters in the default system encoding or in Unicode. Programs that read the parameter values in Unicode support strings from multiple locales. Programs that use the default system encoding probably support only one locale.

On UNIX, the command-line parameters are available in the encoding for the current locale only. If the encoding is Unicode (for example, UTF-8), characters from multiple locales are supported correctly. If the locale encoding is not Unicode (for example, EUC), programs support command-line characters from that one locale only.

Source files are sent to and read from editors, viewers, merge tools, and so on, as an uninterpreted stream of bytes. The user must select tools and tool options that match the source file encodings.

Rational Synergy expects its own files to be in specific encodings, either UTF-8 or the system encoding. Files that contain only7-bit ASCII characters are compatible with both UTF-8 and system encodings, such as Shift-JIS.


Feedback