Why does SourceTree treat Localizable.strings files as binaries; they're not!

Question

This makes updating a localization that much more annoying.

Can ST be configured to treat certain file types as text?

Why is this the default?

Thanks,

S

Josh Snelling_bhzq16 · Answer

Adapting the Git configuration to treat UTF-16 encoded strings file as text does the trick for command-line diffs as well as when viewing pre-commit diffs in SourceTree (when viewing "Uncommitted changes"). However, it's not working when viewing committed changes. Based on this behavior, this doesn't appear to be Git problem.

Does anyone know why SourceTree can show pre-commit diffs but bails on committed changes?

Balázs Szakmáry · Answer

I think you might be looking for this: http://stackoverflow.com/questions/14990993/override-gits-choice-of-binary-file-to-text (As far as I know, you need to make Git understand this, not SourceTree.)