On Wed, Mar 04, 2009 at 11:51:15AM +0100, Peter Krefting wrote: > The problem with changing wchar_t is that_ > it was defined to use 16-bit values at a time where Unicode was defined_ > to use 16-bit code points (but they soon figured out that was not_ > enough). I do realize that is a problem, and unfortunately there is no easy and quick fix to it. But you brought Windows as an example of good Unicode support... Well, to my mind, it is not, at least, not for C programs. You have two serious problems here: 1. wchar_t is too small to hold all Unicode characters as it is required by C standard. 2. UTF-8 support is broken in C runtime library. In fact, if UTF-8 were supported by C runtime, we would not have this thread in the first place... Now, it is possible to wrap all C functions used by Git to make them work with UTF-8, but it is a lot of work... Dmitry -- 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
