Thanks for great app. I want to use Japanese in the commit log, but the combining character string is difficult to read or not display at all.
I extract the commit objects from .git/objects and check the raw commit message bytes.
Original Message:
がぎぐげご
Commit from Git commandline:
e3818c e3818e e38190 e38192 e38194
Commit from Github client:
e3818c e3818e e38190 e38192 e38194
Commit from SourceTree:
e3818b e38299 e3818d e38299 e3818f e38299 e38191 e38299 e38193 e38299
- http://www.fileformat.info/info/unicode/char/304c/index.htm
- http://www.fileformat.info/info/unicode/char/304b/index.htm
- http://www.fileformat.info/info/unicode/char/3099/index.htm
> The combining characters are rarely used in full-width Japanese characters, as Unicode and all common multibyte Japanese encodings provide precomposed glyphs for all possible dakuten and handakuten character combinations in the standard hiragana and katakana ranges.
- is duplicated by
-
SRCTREE-1116 Please support convert UTF8-MAC (NFD) to UTF8 (NFC) in commit message
-
- Closed
-
[SRCTREE-978] Unicode combining character is used to express Japanese 'Dakuten'.
Workflow | Original: JAC Bug Workflow v3 [ 3369871 ] | New: SRCTREE JAC Bug Workflow [ 3737039 ] |
Workflow | Original: SourceTree Bug Workflow [ 381715 ] | New: JAC Bug Workflow v3 [ 3369871 ] |
Assignee | Original: Steve Streeting [ sstreeting ] |
Link |
New:
This issue is duplicated by |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Reopened [ 4 ] | New: Closed [ 6 ] |
Fix Version/s | New: 1.5 [ 24991 ] |
Resolution | Original: Won't Fix [ 2 ] | |
Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
In 1.5 all commit message data is redirected via a file which avoids NSTask's automatic conversion to decomposed unicode (done to assume compatibility with HPFS+).
I've tested this with the examples and the original non-decomposed unicode gets through to the commit message correctly.