IIUC, Windows's Long File Names are encoded in UTF-16 - or maybe in UCS-2 which is a subset of it, covering only code points U+0000 to U+FFFF. In addition, some particular characters are forbidden in Linux but not in Windows, or vice-versa.
I don't have a Windows system anymore, however, so I don't know how to try various possible solutions to your problem. Best regards, Tony. On Mon, Aug 5, 2019 at 2:22 AM Manuel Jacob <[email protected]> wrote: > > Hi, > > So far, all systems from which we accessed our Mercurial repositories > have been Linux machines, configured with a UTF-8 locale. > > We want to give some Windows machines access to some of our > repositories. But now the problem is that if a file with a non-ASCII > filename is committed on Windows, the filename is not properly shown on > Linux and vice versa. > > I understand that the problem is that Mercurial doesn't interpret the > encoding of the file name. But it's unclear how to solve the problem. > The Wiki was not very helpful regarding this. The information ranges > from "too bad, Mercurial won't help you here" to "we have a plan on how > to fix the problem", but because the idea is originally from 2011, it's > unclear whether or not it was implemented in the meantime. > > What would you recommend to solve this problem? The Windows clients > access the repositories with TortoiseHG. Ideally, in the repository, we > would like to have everything encoded in UTF-8. > > -Manuel > _______________________________________________ > Mercurial mailing list > [email protected] > https://www.mercurial-scm.org/mailman/listinfo/mercurial _______________________________________________ Mercurial mailing list [email protected] https://www.mercurial-scm.org/mailman/listinfo/mercurial
