External diff fine encoding issue
We have many UCS2-LE (aka UTF-16) files for holding localized strings in our products.
If I double click such a file in my Pending Changes to view the diffs; the RTC source copy is showing as Codepage 1252 and hence does not display correctly and shows as a huge number of differences. Comparing the same file manually (by making changes to another copy and diffing directly from WinMerge) works fine, The files fetched normally from RTC are fine and in the correct format; it's just a problem when using the external diff. Is this an issue with RTC 2.0.0.1 and should I file a work item? It also seems to have issues with InstallShield scripts (saved in XML format), which are stored as ANSI, but incorrectly marked as Thanks. |
3 answers
|
Sorry - inability to type! The subject should read "External diff file encoding issue" :oops:
|
It's not 100% clear to me what your scenario is. Are you saying that the
problem is occurring using an external compare tool? If you turn the external compare off, does the internal compare viewer look right? Based on the information you have provided, it sounds like the local file is encoded properly so perhaps the remote files are not. When you open an external compare, the remote files are saved to temp files. From within the compare, you should be able to find the temp files and open them to see if they are encoded properly. If they are not, it is a problem in RTC and you should log a work item. As for the improperly marked XML files, I think it is reasonable to expect problems when things are misconfigured. If you are seeing problems in an external compare tool, you would need to consult the documentation of that tool to see how to handle that situation. Michael DuncanL wrote: We have many UCS2-LE (aka UTF-16) files for holding localized strings |
|
Thank you for the reply. Apologies for the delayed response - the forum notification option didn't tell me.
Are you saying that the problem is occurring using an external compare tool? Yes - and the actual tool doesn't make any difference - WinMerge and DiffMerge show the same issue. If you turn the external compare off, does the internal compare viewer look right? Yes; the internal diff tool is correct. Based on the information you have provided, it sounds like the local file is encoded properly so perhaps the remote files are not. When you open an external compare, the remote files are saved to temp files. From within the compare, you should be able to find the temp files and open them to see if they are encoded properly. If they are not, it is a problem in RTC and you should log a work item. I did as you suggested and saved the "remote" copy fetched to the temporary location - it is corrupted; so it does look like an RTC issue. I will try to write this up as a work item. As for the improperly marked XML files, I think it is reasonable to expect problems when things are misconfigured. Indeed. In this case I don't think that it's actually relevant to the problem - given that it happens for other file types. |
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.