Force files to be in UTF-8 Format for checking in the code
Salman Shaikh (234●1●23●72)
| asked Mar 24 '17, 10:55 a.m.
retagged Mar 31 '17, 11:23 a.m. by Ken Tessier (841●1●7) Can we Force files to be in UTF-8 Format for checking in the code, Can we set this thing at global/project level.
|
Accepted answer
It looks like there is a precondition (Restrict Check-in Based on Specified MIME Types and Encodings) that you can set to restrict check-in of files to only those files that have a specific encoding. You can set the scope of the precondition to all components in the project area or to specific components. See Team process preconditions for Rational Team Concert source control for details.
Ken
Salman Shaikh selected this answer as the correct answer
Comments I am unable to find it in Version 5.0.2 and 6.0.2
Ralph Schoon
commented Apr 02 '17, 12:44 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
This is planned to become available in 6.0.4. There was no check in extension point prior to 6.0.4.
|
2 other answers
RTC does not have the control of the file encoding. The encoding should be set in Eclipse IDE or on Eclipse project level.
You can follow http://stackoverflow.com/questions/36494326/setting-text-file-encoding-per-eclipse-project to set the encoding on Eclipse project level which will create a file ".settings/org.eclipse.core.resources.prefs". You can check-in and deliver the file so other users will have the same setting.
|
|
Ralph Schoon (62.7k●3●36●43)
| answered Apr 02 '17, 2:33 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Unless you wait for 6.0.4 and the availability of the check in operation you would have to prevent delivery similar to https://rsjazz.wordpress.com/2012/11/01/restrict-delivery-of-changesets-to-workitem-types-advisordelivery-of-changesets-associated-to-wrong-work-item-types-advisor/
|