On 01 Sep 2015, at 19:35, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Lars Schneider <larsxschneider@xxxxxxxxx> writes: > >> On 01 Sep 2015, at 01:13, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> >>> larsxschneider@xxxxxxxxx writes: >>> >>>> From: Lars Schneider <larsxschneider@xxxxxxxxx> >>>> >>> >>> Here is a space for you to describe what it does and why it is a >>> good idea to have it. >> How about this: >> >> Perforce keeps the encoding of a path as given by the originating >> OS. Git expects paths encoded as UTF-8. Add an option to tell git-p4 >> what encoding Perforce had used for the paths. This encoding is used >> to transcode the paths to UTF-8. As an example, Perforce on Windows >> uses “cp1252” to encode path names. > > Very readable. Does "Perforce on Windows" always use cp1252, or > is it more correct to say "often uses" here? Thank you! I don’t know if “always” or “often” is better. On my Windows test system it is “always”… but that’s not a valid sample size :-) I searched the Internet for clues around cp1252 and found that a similar patch was submitted to Mercurial just a month ago. The author seconds my cp1252 observation: http://mercurial.808500.n3.nabble.com/PATCH-stable-convert-use-original-local-encoding-when-converting-from-Perfoce-tp4025088p4025094.html - Lars-- 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