From owner-freebsd-hackers Tue Oct 17 15:04:26 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA10287 for hackers-outgoing; Tue, 17 Oct 1995 15:04:26 -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 PAA10258 ; Tue, 17 Oct 1995 15:04:13 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA28514; Tue, 17 Oct 1995 14:58:27 -0700 From: Terry Lambert Message-Id: <199510172158.OAA28514@phaeton.artisoft.com> Subject: Re: Locale stuff: call for conclusion. To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Tue, 17 Oct 1995 14:58:27 -0700 (MST) Cc: terry@lambert.org, wollman@lcs.mit.edu, ache@astral.msk.su, core@FreeBSD.ORG, hackers@FreeBSD.ORG, phk@critter.tfs.com In-Reply-To: <9510172112.AA04040@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Oct 17, 95 05:12:00 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: 914 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > > Why do you dislike the #ifdef XPG4? > > > It seems the sane soloution for code transitioning... the code can't > > all be transitioned to runic support at once, and runic support is > > less than useful at present in any case because of ISO 2022 and > > shift-JIS not quite fitting XPG/4 in any case. > > I think the most sensible thing to do is to simply say ``multibyte > locales are not supported'' and leave the code in for someone who > actually uses such locales to find any problems. This is workable, but it is less friendly for the transition from 8bit clean to rune-capable code. If I'm running a runic environment, this will cause transitioned 8bit clean code to fail. Wouldn't it be better to allow it to be tackled in two stages instead of all at once? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.