Re: [PATCH v4] git-p4: add config git-p4.pathEncoding

2015-09-02 Thread Eric Sunshine
On Wednesday, September 2, 2015, wrote: > Perforce keeps the encoding of a path as given by the originating OS. > Git expects paths encoded as UTF-8. Add a config 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,

Re: [PATCH v4] git-p4: add config git-p4.pathEncoding

2015-09-02 Thread Junio C Hamano
larsxschnei...@gmail.com writes: > From: Lars Schneider > > Perforce keeps the encoding of a path as given by the originating OS. > Git expects paths encoded as UTF-8. Add a config to tell git-p4 what > encoding Perforce had used for the paths. This encoding is used to > transcode the paths to UT

[PATCH v4] git-p4: add config git-p4.pathEncoding

2015-09-02 Thread larsxschneider
From: Lars Schneider Perforce keeps the encoding of a path as given by the originating OS. Git expects paths encoded as UTF-8. Add a config 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 my Windows bo

[PATCH v4] git-p4: add config git-p4.pathEncoding

2015-09-02 Thread larsxschneider
From: Lars Schneider Diff to v3: * add proper commit message * remove command line option "--path-encoding" and add config "git-p4.pathEncoding" * change TC number to 9822 * escape UTF-8 characters in TC * change test encoding used in TC from cp1251 to ISO-8859-1 * use static ISO-8859-1 encoded