2012/3/1 Junio C Hamano <gitster@xxxxxxxxx>: >> >> Shall we remind the contributors for l10n to write commit log in English, >> but not language XX? It's a common mistake for translators. > > I would prefer to see the subject line (the first line summary) in English > to say something like "Update zh_CN translation for 1.7.12". That much of > English shouldn't be too much burden for language teams. I noticed that all i18n related commit logs all have prefix "i18n:". It would be nice to add a prefix "l10n:" to the l10n related commit log, such as: "l10n: Update zh_CN translation for 1.7.12". > > On the other hand, the body of the log that describes the change _may_ be > hurt if you forbid the use of language XX. The translators may want to > write something like: > Git does not handle multi-bytes character well. Multi-bytes characters not convert to UTF-8 when git write tree objects and commit objects. I think allow multi-bytes characters in commit log would hurt git.git until git gives full support UTF-8 (are there any plans for this?). I just tested several versions of msysgit: - Only Git-1.7.8-preview20111229-unicode.exe saves commit objects with utf-8 encode. - Other versions such as Git-1.7.9-preview20120201.exe and Git-1.7.8-preview20111206.exe will not convert multi-bytes characters in commit log into UTF-8. -- Jiang Xin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html