lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] Should we restrict cvs files to ASCII?


From: Vadim Zeitlin
Subject: Re: [lmi] Should we restrict cvs files to ASCII?
Date: Tue, 17 Apr 2007 14:58:49 +0200

On Tue, 17 Apr 2007 12:50:12 +0000 Greg Chicares <address@hidden> wrote:

GC> I see this inadvertent change:
GC> 
GC>   ChangeLog,v 1.618 2007/04/17 12:33:09
GC> -  "§21.2206(1)(I)-(M), (O), (Q)-(S) and (U)-(V) Supplemental - Other"
GC> +  "�21.2206(1)(I)-(M), (O), (Q)-(S) and (U)-(V) Supplemental - Other"

 This is probably due to an editor which does conversion to UTF-8
automatically... Which also means that it's probably impossible to even
notice that it has happened. And while Codestriker should have shown it
it's still easy to miss it.

GC> How do other projects typically prevent this?

 Not using ASCII at all is a solution, of course. Otherwise the best is
probably to standardize on encoding to use for 8 bit characters. Either
ISO8859-1, ISO8859-15 or UTF-8 could be reasonable choices for us.

GC> Should we just restrict all files in cvs to ASCII?

 This really depends on whether you think we really need to use such
characters (including § above, but also ones like © or ® or ½ or ¤) or
not...

GC> For now, I'll revert that one line.

 Sorry about this,
VZ





reply via email to

[Prev in Thread] Current Thread [Next in Thread]