From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Wed Feb 1 22:15:13 2023 Return-Path: X-Original-To: sc22wg5-dom9 Delivered-To: sc22wg5-dom9@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id DDBAA358FDC; Wed, 1 Feb 2023 22:15:13 +0100 (CET) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 585 seconds by postgrey-1.34 at www5.open-std.org; Wed, 01 Feb 2023 22:15:13 CET Received: from sasl.smtp.pobox.com (pb-sasl1.pobox.com [64.147.108.66]) by www.open-std.org (Postfix) with ESMTP id 7D30D358FC4 for ; Wed, 1 Feb 2023 22:15:13 +0100 (CET) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id 91E119621E; Wed, 1 Feb 2023 16:05:25 -0500 (EST) (envelope-from gak@dancingbear.dev) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=sasl; bh= 0ddnJIXuaRUqAn4+VEsFm1tHiMUvgQi0fbeG2RbkAzE=; b=gzE52+aSsU2JXrgE IrWBM7PDbB9RmvkcFvF8GoXU51OUEDQlAyuMYPUX0NIyCibgsa2KRq/ZGW5K0Uh4 sCcAUGwEQo4FRqCa/Nw8kHWq56OHS660yT+gKDcJmU9U6nfxF3pLGmtdkyHbl5ww RDdQqQnXndbE1hfIbRins8y0iK0= Received: from pb-sasl1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id 743AC9621C; Wed, 1 Feb 2023 16:05:25 -0500 (EST) (envelope-from gak@dancingbear.dev) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=dancingbear.dev; h=content-type:mime-version:subject:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=2019-12.pbsmtp; bh=0ddnJIXuaRUqAn4+VEsFm1tHiMUvgQi0fbeG2RbkAzE=; b=r6mMwFZEv+Jv3Nt/x44ab11jPfLOQ6G0T/nm68aENUYCweKgZd8KjhN4buuPFSLgkzTeqwEvNgMeM51SpCotPg9cJSICo0aMfhT13twxkFz7g42Ml8XYy7vOhHqxfJ1xWvEDQMorHAMqAIjyBwPSlMLtR73rc6W8EXkA42JOy7I= Received: from smtpclient.apple (unknown [209.180.167.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-sasl1.pobox.com (Postfix) with ESMTPSA id 76E549621B; Wed, 1 Feb 2023 16:05:24 -0500 (EST) (envelope-from gak@dancingbear.dev) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Subject: Re: [J3] [SC22WG5.6424] F2023 DIS ballot results and comments From: Gary Klimowicz In-Reply-To: <20230201174516.10EC3358FD8@www.open-std.org> Date: Wed, 1 Feb 2023 13:04:53 -0800 Cc: David Muxworthy Content-Transfer-Encoding: quoted-printable Message-Id: <5C9BBA62-9CD1-4F8D-975D-5CF00A66971B@dancingbear.dev> References: <20230201152213.D1BFB358FD7@www.open-std.org> <20230201174516.10EC3358FD8@www.open-std.org> To: David Muxworthy , sc22wg5@open-std.org, General J3 interest list X-Mailer: Apple Mail (2.3731.400.51.1.1) X-Pobox-Relay-ID: 2588C086-A274-11ED-94A8-38C66D9B1A4B-83697616!pb-sasl1.pobox.com Sender: owner-sc22wg5@open-std.org Precedence: bulk > On Feb 1, 2023, at 09:37, d.muxworthy--- via J3 = wrote: >=20 >> The argument against line numbers is that, especially when the = document is translated, they can change. Does anyone have strong = opinions about whether we should put line numbers back in the official = standard? I'd like to keep the paragraph numbers and don't care about = line numbers. >=20 > Unlike line numbers paragraph numbers remain invariant with different = font sizes (mentioned by ITTF in the DIS comments), page sizes and page = margins as well as in any translation. I vote to keep paragraph numbers = and not to have line numbers in the versions going outside the Fortran = committees. > David I agree with David.=