SourceGear Support

I made a sample here. If you take the 1st set of files (files encoded with the byte order marks), those use the correct encoding on Windows, Mac, and Linux. However, if a file is missing the BOM, it will depend on what character set ends up displaying the text. The default character set on the Mac ...

Can you try a quick test on the Mac? a) Make a copy of both files you are working with, but rename the files so the copies extensions end with '.utf8'. For example, 'somefile.json' would be 'somefile.utf8'. b) Run these two *.utf8 files in DiffMerge. What does the diff look like for these two files...

I tried disabling custom rule set, then enabling but unticking 'Search for Unicode BOM' - and making sure that the Named Character Encoding was set to UTF-8. No difference. In the Json I make on my Mac, DiffMerge sees "Curaçao" -- even if it's just an empty plain text document and I copy/...

All of this will be dependent on what is stored in the Byte Order Mark (BOM) in the beginning of your file. Do you know if one is present? Next, take a look at the individual Rulesets for the extensions of your configuration files. Is the BOM option checked in the Ruleset? Perhaps you need define o...

Hi, I'm using DiffMerge to compare Json files that we use to update the text content on our web portal and having problems with UTF-8 and special characters. For example, in the last Json file I made on Windows, Notepad++ (Windows), TextEdit (Mac) and DiffMerge all see the text "Curaçao". ...