Handling differences in file encoding between code streams for the same file
This question is related: https://jazz.net/forum/questions/81523/text-file-encoding-problems-between-linux-and-windows-eclipse-clients
Is there any best practices document describing how to avoid encoding problems between windows and Linux developers working on the same files. What we're experiencing is that files in the say the Release 1 code stream is not UTF-8, and then say in the Release 2 code steam, the file is UTF-8. When trying to apply changesets with no differences besides the encoding, RTC gives very odd errors such as the one shown below. Needless to say, this is absolutely MADDENING to deal with this issue when merging.
Is there a way to go through our entire code repository and normalize the file encoding of text files (maybe those within a set of file suffixes)? Any way to set a preference in RTC (using Server v4 and client v3)? Any other tips for merging? We also have issues with differing line terminators, but that issue is not as onerous as the encoding issue.
Thanks,
Justin
|
One answer
Ralph Schoon (63.1k●3●36●46)
| answered Nov 02 '12, 5:34 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The only suggestion I could give is to settle to a common encoding and line delimiters. I would use UTF-8 and Unix. Eclipse can handle both on windows.
You can set UTF8 as default in Eclipse and you can change the encoding for each file in the file properties. |
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.