|
From: | Jim Hyslop |
Subject: | Re: CVS and unicode |
Date: | Sun, 11 Sep 2005 23:57:30 -0400 |
User-agent: | Mozilla Thunderbird 1.0.6 (Windows/20050716) |
Christian Hujer wrote:
In that case, the specification is broken: line endings are defined by the operating system, not by a file specification. Suppose I defined a file specification as: "This is a text file. Line endings always have to be ASCII 0x7f, regardless of the operating system."This is not the point of the program but of the file specification.If a file specification says "This is a text file. Line endings always have to be LF, regardless of the operating system."
I have to be the ruler over line endings and encodings, because this is the only way I can make sure that every single byte in the file is the way I want. For me this is also true in the context of version controlled text files.This seems to be a case of the tail wagging the dog. You have cited one particular example where automatic line ending conversion is a problem. Should we invalidate thousands of other use-cases where automated line ending conversion is not only desirable, but the correct course of action?
-- Jim
[Prev in Thread] | Current Thread | [Next in Thread] |