On 14. mai 2010, at 12.16, Dmitry Potapov wrote: > Probably, ability of automatic add utf8 BOM on Windows to text files > (which are marked as "unicode") can be helpful, but it is just a part > of the problem of how to deal with text files in "legacy" encoding, > which are still widely used on Windows. Sounds like something a clean/smudge filter should be able to do. The clean filter converts legacy encoded text to utf8 and strips any utf8 BOM before checking the file in, and the smudge filter writes the file out as utf8 with a BOM (which hopefully works no matter what your code page is? I don't know much about Windows i18n). Adding this to convert.c would be more difficult, at least politically, since I assume it would be Windows-specific code. -- Eyvind -- 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