Re: CVS and unicode

[Spiro Trikaliotis]

Hello,

* On Mon, Sep 12, 2005 at 09:13:28PM +0200 Christian Hujer wrote:

> > Then they're not text files.  ISO 8859-1 files won't look anything
> > like text on an IBM mainframe that uses EBCDIC instead of ASCII.
>
> Okay, but I think talking of EBCDIC or other non-ASCII-based charsets
> / encodings is really pointless.

Why is this pointless?

> Well, I don't know that many compilers, I know javac, jikes, gcc and
> those from Microsoft. All of these accept LF just as well as CR/LF,
> regardless of the platform.

Did you ever try to have a project with MSVC .DSP and .DSW files opened
if these files only have LF as line endings? MSVC refuses even to load
these files.

Russ also told you about another placs where LF file endings seems to be
supported, but in fact, they are not.

> I've never seen a project where text files with LF only would be a
> problem when still being LF only on Windows. But I've of course only
> seen a small number of possible projects...

See above, I have seen these problems. In fact, I started using cygwin
in LF only mode. I changed back to CR/LF after recognizing I got many
problems with this setting.

 
> Now who is responsible for adding the CR if I access the file with
> Notepad?  (Imo I, the user is, because the OS is too stupid, and I
> really know more about how my file contents should look like than the
> OS)

Why should notepad - which is a very simple editor - try to implement
each and every OS line ending specification known on earth? The "one
task - one tool" approach seems much more appropriate here.

While we're at Windows: Wordpad, for example, can open LF only files.
Writing them back to disk, it always uses CR/LF again. So, does Wordpad
satisfy your requirement of a "smart editor"?

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://cbm4win.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/