You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For git itself the charset of committed files does not matter, it more or less works with byte streams.
However, it is important for GUI tools like diff/merge.
While many source files of today are encoded in UTF-8 it is not always so, especially with legacy projects. Especially comments there, user UI texts, etc.
Feature requests: for repositories (and maybe also for folders and even particular files) provide user setting of source files charset, so DIFF would be seen in human-readable way.
The text was updated successfully, but these errors were encountered:
For git itself the charset of committed files does not matter, it more or less works with byte streams.
However, it is important for GUI tools like diff/merge.
While many source files of today are encoded in UTF-8 it is not always so, especially with legacy projects. Especially comments there, user UI texts, etc.
Feature requests: for repositories (and maybe also for folders and even particular files) provide user setting of source files charset, so DIFF would be seen in human-readable way.
The text was updated successfully, but these errors were encountered: