It's all about the answers!

Ask a question

Issue with UTF-8 content-type file comparision in RTC web client

Arun K Sriramaiah (3.2k13277) | asked May 29 '19, 7:40 a.m.
retagged Jun 28 '19, 10:27 a.m. by Ken Tessier (84117)
While doing defect-fix-reviews using the web client, trying to compare C file, which is of content type UTF-8, but I see a message like below :

"Cannot display text comparison because the initial and final content types are UTF-8 and UTF-8." UTF-8 is indeed a standard character set, and C-files are just text.

One answer

permanent link
Arun K Sriramaiah (3.2k13277) | answered May 29 '19, 7:41 a.m.
edited May 29 '19, 7:42 a.m.

The problematic files have "UTF-8" set as the content type, while the "working" files have e.g. "text/plain".

The web UI relies on the content type and does not recognize the files as text files, hence there is no option to view it in the Web UI.

 Note: UTF-8 supported with encoding not as file content type, you have to change to supported content type.

 The most obvious way to automate code migrations would be to use the SCM Command Line Interface. There are three ways to set this content type using the tool:

 A. Using line "mime: <content-type>" in C:\Users\<user name>\AppData\Local\jazz-scm\

This sets the MIME type for all files processed by the SCM CLI.

 B. By setting the property for individual files, e.g.

lscm set property jazz.mime <content-type> src/

 C. Using the File Properties wizard as documented in the Knowledge Center:

 The list of supported content types is available online, e.g. at:

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.