title: WinMerge: How to compare files with the same content but different encodings?
body: <p><strong>Motivation:</strong>  I am rewriting a doc -- text files to be processed later. The new sources now use UTF-8. Large portions of the sources are the same. I need to find differences.</p>
  
  <p><strong>Details:</strong> The old doc sources use the cp1250 encoding, the new sources use the UTF-8. Both new and old sources use the same line endings (CR+LF). I am using the Unicode version of the WinMerge application (WinMergeU.exe), version 2.12.4.0.</p>
  
  <p>It almost works, but... When the lines differ, they are initially marked as block by the dark yellow, and the different portions are marked using the lighter colour. When moving the red block cursor there, the panes below show the different part.</p>
  
  <p>However, the block of text is marked by the dark yellow also in cases when (the Unicode representation of) the text is the same. The red block moves also to those portions of the files. In such case, the two panes below (that show the differences) containt the same text and nothing is marked as different. See the picture below:</p>
  
  <p><img src="https://i.stack.imgur.com/NbTtH.png" alt="Example of the line that should not differ."></p>
  
  <p>The very first line differs -- this is OK. But the second line has visually the same content. The only character outside of the ASCII range is <code>Ú</code> there. It has a different representation in the encoded sources. This causes the line marked as different, but the panes below does not mark anyting at the line as different.</p>
  
  <p>See also the following paragraphs that are exactly the same (only the encoding in the sources differ, the same line ending is used).</p>
  
  <p>It looks as if the initial comparison were based on binary representation of the lines. Is there any setting to tell WinMerge that the comparison (I mean the block marking) should be based on Unicode content?</p>
  
  <p>I tried hard, but no luck, yet.</p>
  
  <p><strong>Update:</strong> The above question was for the latest stable 2.12.4. The beta version 2.13.22 works just perfectly for me. See <a href="https://stackoverflow.com/a/14606297/1346705">my answer below</a>.</p>