tech-userlevel archive

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

Re: [PATCH] replace 0xA0 to whitespace in plain text files (part 2)

On Thu, Sep 11, 2008 at 1:36 PM, Quentin Garnier <> 
> On Thu, Sep 11, 2008 at 06:33:51PM +0200, Alan Barrett wrote:
>> On Thu, 11 Sep 2008, der Mouse wrote:
> [...]
>> > >> Not that I care so much, but are NetBSD supposed to have its files
>> > >> in Latin1?  Is that supposed to be the source character set, or
>> > >> what?
>> > > I think that simply is the practical reality.
>> > I agree.
>> I think the default should be either ASCII or UTF-8.  Other encodings
> I have a dim recollection of someone insisting on having (c) in the source
> files instead of (c).  There was a semi-absurd (well, to be frank,
> totally absurd in my eyes) reasoning behind it.  Please, dear Someone,
> don't resurrect that discussion.  I believe any other participant or
> reader have just ended up rolling their eyes mumbling "whatever".
> Personally, I think everything in the source tree should ASCII unless it
> is impossible, such as for locale-related files.  In which case, an
> encoding which is as friendly as possible to iso-8859-1 terminals would
> be preferred.  Not a rule to set in stone though, just a strong advice;
> it's no big deal for anyone if a few files have Latin1 characters in
> them.

Check out the thread "Unicode text editor."

I also had an issue recently with some sort of non-ascii dash in an
attempt to use an arrow (->) operator.

Home | Main Index | Thread Index | Old Index