On 2006-05-06 22:56:26 -0500, Peter Samuelson wrote: > [Vincent Lefevre] > > This is a very bad idea, as the encoding of the files from the > > repository is common for every user, thus does not necessarily > > correspond to the locales. > > subversion has to guess, one way or another. Guessing that you want > your files to look like UTF-8 but your filenames to look like KOI8-R > seems pretty dumb.
It is not possible to guess in general. > If you want to edit UTF-8 content, you should probably be using a UTF-8 > locale This is completely wrong. > - I doubt most text editors will do the right thing otherwise. Emacs can edit files in any encoding without any problem, whatever the locale the user has chosen. Locales are mainly for user interaction, such as input/output, they don't enforce the encoding of documents or various file formats. And there are not text editors only. There are also XML tools, that work on files with encodings (UTF-8 in particular) that may be different from the user's locale. There are also other file formats, such as ogg files, whose meta-data are encoded in UTF-8. > And for XML tools that expect a file to be UTF-8-encoded, what will > they think of filename references in some foreign encoding? I don't understand your question. If you mean that the XML document encoded in UTF-8 contains a filename, then yes, the filename must be encoded in UTF-8, as any other data in the document. Otherwise, the keyword expansion doesn't concern the encoding of filenames, which is a different and unrelated matter. > > Note that upstream disagrees concerning this patch, e.g. > > > > http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=115189 > > No - they're of mixed opinions. Brane disagrees, Julian doesn't: > > http://svn.haxx.se/dev/archive-2006-04/0785.shtml Well, in his second sentence, Julian said: "... is better than mixed locales." > Ivan thinks keywords should not be localised at all, which also > solves the problem, but that's a lot harder to implement. No, it doesn't solve the problem. Anyway AFAIK, upstream hasn't applied the patch, so that this creates a huge inconsistency between Debian and upstream. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / SPACES project at LORIA
