Fossil SCM
Chinese commit message File in code UTF-8 when using commit -M under WINDOWS Garbled
5a0a33f31a7a791…
· opened 11 years, 5 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Important
- Resolution
- Fixed
- Subsystem
- —
- Created
- Nov. 11, 2014 6:12 a.m.
WHEN I use commit -M file .If the File was code in UTF-8 and with Chinese. Then in Timeline page the Chinese was Garbled. I think it's need to check commit message File ,if it was UTF-8 then do not convert.
Comments (2)
WHEN I use commit -M file .If the File was code in UTF-8 and with Chinese. Then in Timeline page the Chinese was Garbled. I think it's need to check commit message File ,if it was UTF-8 then do not convert.
Fossil checks whether the file contains a BOM (for either UTF-8 or UTF-16) and does the appropriate conversion then. If the file does not contain a BOM, it assumes CP1252. On Windows, it is customary to start a file with the UTF-8 BOM, otherwise editors like Notepad will interpret the data wrong as well.
Regards, Jan Nijtmans