On Thursday, March 29, 2018 at 5:09:03 PM UTC+2, David Balažic wrote: > > It turns out a nonascii charater a few lines above the other change was > changed in its encoding. > > Question: Why does TMerge not mark such a change as... a change? Is it > depending on some settings of TMerge? > > TortoiseMerge tries to detect the encoding of the whole file and uses that when saving. It does not do that line-by-line since that breaks more than using the whole file. So, when saving the file with TMerge, it is saved with the detected encoding. You can see the detected encoding at the bottom right of TMerge. And there you can also change the encoding if necessary.
It doesn't show those lines as changed since after loading with the detected encoding, those lines are not different anymore. > > Additional info: > > After that I edited the said file and changed that character back to UTF-8 > encoding. > Now TMerge says: > > --------------------------- > TortoiseMerge > --------------------------- > The text is identical, but the files do not match! > > The following differences were found: > > Encoding (ASCII, UTF-8) > > Since you're using utf-8 encoding as the default, go to the TMerge settings dialog and check the box "Default to UTF-8 encoding". Or you could add an .editorconfig file. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/1dc5ffbe-ec6e-40dd-837c-51413faf5970%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
