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
{{ message }}
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
When having tried to commit with a commit message involving a four-byte UTF-8 character, namely non-BMP character, U+2123D, using Git GUI, the warning "commit message does not conform to UTF-8." came out.
With three-byte UTF-8 character, U+5721, no problem.
This is a Tcl/Tk issue. Tcl/Tk has two enhancement request outstanding to extend its Unicode handling beyond the BMP but as yet only one of these is completed for 8.6 and there is no support for non-BMP Unicode in 8.5. The two TIPs are http://tip.tcl.tk/388 and http://tip.tcl.tk/389 which indicates full Unicode 6.0 support is slated for 8.7 which is some way off.
So in summary - Tcl/Tk do not support 4 byte UTF-8.
When having tried to commit with a commit message involving a four-byte UTF-8 character, namely non-BMP character, U+2123D, using Git GUI, the warning "commit message does not conform to UTF-8." came out.
With three-byte UTF-8 character, U+5721, no problem.
And filenames involving four-byte UTF-8 character shall be corrupted on Git GUI and gitk.
For example, when the filename is including U+2123D, it shall be displayed as "�" on these tools.