Re: [PATCH v3] git-p4: add "--path-encoding" option
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 1, 2015, 17:35 UTC
- Message-ID
- <xmqqmvx6rqk7.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <523D2C52-893E-4A54-9DD1-2DDBCEA29960@gmail.com>
Lars Schneider <larsxschneider@gmail.com> writes:
Show 16 quoted lines
> On 01 Sep 2015, at 01:13, Junio C Hamano <gitster@pobox.com> wrote: > >> larsxschneider@gmail.com writes: >> >>> From: Lars Schneider <larsxschneider@gmail.com> >>> >> >> 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?