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

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?



2 answers

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?

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.)

Suggest an answer

Log in or Join to answer
Community showcase
Brian Ganninger
Published Jan 23, 2018 in Sourcetree

Tip from the team: workflow and keyboard shortcuts

Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...

238 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot