On 09.07.2013 17:01, Andreas Krey wrote: > On Tue, 09 Jul 2013 16:26:40 +0000, Branko ??ibej wrote: > ... >> Since we're on the topic, would you care to explain why translating >> files to the native encoding is "a rather stupid idea"? > Because LANG isn't "the native encoding", but, for the file system > the "naive encoding". > > What encoding is used in the file system is a property of the > file system or even individual directories and files, but certainly > not of the terminal session I'm using to do the checkout. > > (And if you think that LANG should apply to file names on disk, > why would you think it should not do so for the file names that > come from the svn server in the checkout?)
Unlike on Windows and Mac OS (the latter at least with HFS+), the is no notion of native filesystem encoding on other Unix-like platforms. The best we can do is look at the locale settings, specifically, LC_CTYPE. I posit that if the "native encoding" is supposed to be UTF-8, then it is an error to use LANG=C at all. Instead, one should use LANG=C.UTF-8. In a context where, for example, most files were encoded in Big5 (http://en.wikipedia.org/wiki/Big5) — not a too far-fetched proposition — it would be slightly insane, to put it mildly, for Subversion to assume it can just write UTF-8 to disk. So indeed, this state of affairs puts the burden of setting up their locale correctly on users, but that's simply the way Unix works. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
