From owner-freebsd-hackers  Mon Oct 16 15:16:25 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA24504
          for hackers-outgoing; Mon, 16 Oct 1995 15:16:25 -0700
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA24491
          for <hackers@freefall.freebsd.org>; Mon, 16 Oct 1995 15:16:20 -0700
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA25592; Mon, 16 Oct 1995 15:11:18 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199510162211.PAA25592@phaeton.artisoft.com>
Subject: Re: A couple problems in FreeBSD 2.1.0-950922-SNAP
To: kaleb@x.org (Kaleb S. KEITHLEY)
Date: Mon, 16 Oct 1995 15:11:17 -0700 (MST)
Cc: hackers@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de
In-Reply-To: <199510160028.UAA06809@exalt.x.org> from "Kaleb S. KEITHLEY" at Oct 15, 95 08:28:36 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 841       
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

> Expo follows RFC 821/822 to the letter. It's not convenient, but it does 
> blindly adhere to the rules. Everyone else in the world seems to be 
> overlooking the rules, mostly it seems because it's inconvenient to
> to follow the rules set out in the RFCs.

Strongly agreed.

> Along the same line, it'd be really convenient if the default chartype
> table had its right side populated for ISO8859-1 so that broken tools
> could still manage to do the right thing most of the time.

My major premise in this whole discussion is that the bogus code in
crt0.o is a result of trying to correct the C locale deficiencies
without actually correcting the C locale.

It is a kludge on a bug, not a bugfix.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.