Welcome to the Jazz Community Forum
Manipulating the mime type of the Jazz Source Control property

This question has two parts. Our project uses a number of python files with a *.py extension that are not recognized as text files by default. This means that they are associated with a mime type of application/unknown instead of the expected text/plain. This means that the diff editor won't work on these files because it thinks that they have binary content.
1) Is there a way to search for files by their associated mime type so that I can find all files that might have this issue and change them?
2) Is there a way to configure RTC to recognize additional file extensions as text by default in order to prevent this problem from happening again? I am aware that individual developers can configure their RTC client to recognize additional file extensions, but I am hoping that there might be a way to configure this at the server level once and for all.
Brian
1) Is there a way to search for files by their associated mime type so that I can find all files that might have this issue and change them?
2) Is there a way to configure RTC to recognize additional file extensions as text by default in order to prevent this problem from happening again? I am aware that individual developers can configure their RTC client to recognize additional file extensions, but I am hoping that there might be a way to configure this at the server level once and for all.
Brian
Accepted answer

Hi Brian, I'm not sure of a way to accomplish item 1. I do know that the following RFE exists for item 2.
One other answer

Hi Brian, I am not aware of a way how defining the mime types can be achieved at server side, but there are ways to export the settings of a workspace and let other users use the same while creating any new workspace. So someone has to do the hard work once for all.
I think you may consider this as a part of user education other than a limitation till the server side configuration possibility is known.
Just my 2 cents...
I think you may consider this as a part of user education other than a limitation till the server side configuration possibility is known.
Just my 2 cents...