From owner-sc22wg5@dkuug.dk Fri Jul 25 23:18:24 2003 Received: (from majordom@localhost) by dkuug.dk (8.12.8p1/8.9.2) id h6PLIO7R030368 for sc22wg5-domo; Fri, 25 Jul 2003 23:18:24 +0200 (CEST) (envelope-from owner-sc22wg5@dkuug.dk) X-Authentication-Warning: ptah.dkuug.dk: majordom set sender to owner-sc22wg5@dkuug.dk using -f Received: from mailhub.dfrc.nasa.gov (mailhub.dfrc.nasa.gov [130.134.81.12]) by dkuug.dk (8.12.8p1/8.9.2) with ESMTP id h6PLGmEc030349 for ; Fri, 25 Jul 2003 23:18:19 +0200 (CEST) (envelope-from maine@altair.dfrc.nasa.gov) Received: from mail.dfrc.nasa.gov by mailhub.dfrc.nasa.gov with ESMTP for sc22wg5@dkuug.dk; Fri, 25 Jul 2003 14:13:51 -0700 Received: from altair.dfrc.nasa.gov ([130.134.20.211]) by mail.dfrc.nasa.gov (Post.Office MTA v3.5.3 release 223 ID# 0-71686U2500L200S0V35) with ESMTP id gov for ; Fri, 25 Jul 2003 14:16:40 -0700 Received: by altair.dfrc.nasa.gov (Postfix, from userid 201) id 70D4135780; Fri, 25 Jul 2003 14:16:35 -0700 (PDT) From: Richard Maine MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <16161.40499.314474.129284@altair.dfrc.nasa.gov> Date: Fri, 25 Jul 2003 14:16:35 -0700 To: sc22wg5@dkuug.dk Subject: (SC22WG5.2895) Paper N1547 In-Reply-To: <200307250745.h6P7jIn7025962@dkuug.dk> References: <200307250745.h6P7jIn7025962@dkuug.dk> X-Mailer: VM 7.07 under 21.4 (patch 12) "Portable Code" XEmacs Lucid Sender: owner-sc22wg5@dkuug.dk Precedence: bulk Sorry I didn't look at this earlier. I can't offer guaranteed next day response (that would be the higher cost "gold" support level :-)). Fortunately my comments are pretty trivial. I have no serious heartburn about any of the edits in the version of N1547 on the server (i.e. after Malcolm's suggestions were incorporated). David Muxworthy writes: > 467:35 "may or may not" -> "might or might not" I presume this to be a typo for [467:42] > 2. Normative references I could go any way on most of these questions, though I agree we should be consistent. We really need a shorthand for the C and IEEE standards because we reference them so much. I don't care a lot whether we use the short form for the ASCII or Unicode (or whatever it 10646 is called) standards, but I agree that we should not refer to a standard in multiple ways. The 3 references to ASCII appear to use 3 different forms. (One abbreviations and two long forms - one of the long forms includes the bit about IRV in parens). -- Richard Maine | Good judgment comes from experience; Richard.Maine@nasa.gov | experience comes from bad judgment. | -- Mark Twain