Bad storage path translation (native characters in file names are not translated correctly)

GoogleCodeExporter commented 8 years ago

If there's a file with name using native/non ASCII characters, Hg4J deduces 
storage path (.i/.d) for the file incorrectly.

Mercurial uses (see http://mercurial.selenic.com/wiki/EncodingStrategy) bytes 
of native filesystem encoding (e.g. cp1251) when mangling storage file name. 
Hence, copy of a repository is of no use if copied to a filesystem with 
different encoding.

Hg4J shall translate Unicode file names into appropriate byte representation 
when translating file names to storage paths.

Original issue reported on code.google.com by tikhomir...@gmail.com on 20 Mar 2012 at 4:56

GoogleCodeExporter commented 8 years ago

Fixed in revision 464b4404e75d, branch smartgit3.
Tests: TestStorePath#testNationalChars

Original comment by tikhomir...@gmail.com on 20 Mar 2012 at 5:01

GoogleCodeExporter commented 8 years ago

Revision bb278ccf9866: pull into default

Original comment by tikhomir...@gmail.com on 21 Mar 2012 at 7:52

Changed state: Fixed

3r1co / hg4j

Bad storage path translation (native characters in file names are not translated correctly) #29