Klocwork support for non-ASCII encoding

Klocwork or later is fully internationalized, meaning that it accepts multibyte characters, such as Japanese, in:

• source-file contents (note that for C/C++, multibyte characters are allowed only in comments and strings)
• source-file names and paths (see Limitations related to internationalization)
• tables directory paths
• comments on detected issues
• custom checker help files (Note that multibyte characters are not permitted in issue codes)
• configuration files
• user authentication management (for example, LDAP access control)
• Checker Studio

Characters that are used in file system paths must be representable in your current encoding. For example, if Japanese characters are used in paths to source files or to the tables directory, then the current encoding should be appropriately set to support Japanese characters. On Windows, this means that the language for non-unicode programs must be set to Japanese. To change this property, go to Control Panel > Regional and Language options > Advanced, select Japanese, and restart your computer.

You cannot set up or submit a code review if your Perforce Depot or Visual Studio workspace contains Japanese characters. Therefore, use ASCII characters to specify both your P4 depot name and your Visual Studio workspace, or use a unicode enabled Perforce server.

Do not use non-ASCII, double-byte characters (e.g. Japanese) to specify the name of your projects_root

Using Japanese or other non-ASCII, double-byte characters to specify your projects_root will cause failures. Therefore, use ASCII characters to specify your projects_root.