GNU logs - #35343, boring messages

Message sent to bug-coreutils@HIDDEN:

Subject: bug#35343: sort: printing characters: define
Resent-From: =?UTF-8?Q?=E7=A9=8D=E4=B8=B9=E5=B0=BC?= Dan Jacobson <jidanni@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-coreutils@HIDDEN
Resent-Date: Sat, 20 Apr 2019 13:55:01 +0000
Resent-Message-ID: <handler.35343.B.15557684939809 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 35343 <at> debbugs.gnu.org
From: =?UTF-8?Q?=E7=A9=8D=E4=B8=B9=E5=B0=BC?= Dan Jacobson <jidanni@HIDDEN>
Date: Sat, 20 Apr 2019 21:54:34 +0800
Message-ID: <87zhokye79.5.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

(info "(coreutils) sort invocation") says

=E2=80=98-i=E2=80=99
=E2=80=98--ignore-nonprinting=E2=80=99
     Ignore nonprinting characters.  The =E2=80=98LC_CTYPE=E2=80=99 local=
e determines
     character types...

Well this leaves the user high and dry trying to figure out what you
mean by printing characters.

Is SPC a printing character he wonders. It makes the printer head
advance one unit, whereas ESC doesn't.

So at least mention the ASCII range [A-Z...] of what your are talking
about. It would only take up a word or two of the INFO page.

Anyway, each program might have their own idea of "printing characters"
as well as grandpa down the hall's definition. So the user is left unsure=
.

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: =?UTF-8?Q?=E7=A9=8D=E4=B8=B9=E5=B0=BC?= Dan Jacobson <jidanni@HIDDEN>
Subject: bug#35343: Acknowledgement (sort: printing characters: define)
Message-ID: <handler.35343.B.15557684939809.ack <at> debbugs.gnu.org>
References: <87zhokye79.5.fsf@HIDDEN>
X-Gnu-PR-Message: ack 35343
X-Gnu-PR-Package: coreutils
Reply-To: 35343 <at> debbugs.gnu.org
Date: Sat, 20 Apr 2019 13:55:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-coreutils@HIDDEN

If you wish to submit further information on this problem, please
send it to 35343 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
35343: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D35343
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-coreutils@HIDDEN:

Subject: bug#35343: sort: printing characters: define
Resent-From: L A Walsh <coreutils@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-coreutils@HIDDEN
Resent-Date: Fri, 26 Apr 2019 06:18:02 +0000
Resent-Message-ID: <handler.35343.B.155625946524327 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: =?UTF-8?Q?=E7=A9=8D=E4=B8=B9=E5=B0=BC?= Dan Jacobson <jidanni@HIDDEN>
Cc: 35343 <at> debbugs.gnu.org
Message-ID: <5CC2A259.4060606@HIDDEN>
Date: Thu, 25 Apr 2019 23:16:57 -0700
From: L A Walsh <coreutils@HIDDEN>
User-Agent: Thunderbird
MIME-Version: 1.0
References: <87zhokye79.5.fsf@HIDDEN>
In-Reply-To: <87zhokye79.5.fsf@HIDDEN>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

On 4/20/2019 6:54 AM, =E7=A9=8D=E4=B8=B9=E5=B0=BC Dan Jacobson wrote:
> (info "(coreutils) sort invocation") says
>
> =E2=80=98-i=E2=80=99
> =E2=80=98--ignore-nonprinting=E2=80=99
>      Ignore nonprinting characters.  The =E2=80=98LC_CTYPE=E2=80=99 loc=
ale determines
>      character types...
>  =20
----
    @ location:
 https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/basedefs/V1=
_chap07.html#tag_07_03_01

LC CTYPE is defined by POSIX for the 'POSIX' or 'C' locale.  It is
relative (defined) as specified by the current locale.
> Well this leaves the user high and dry trying to figure out what you
> mean by printing characters.
>  =20
If the user is wet and water is introduced into the printing medium,
ink smearing or other malfunctions may occur that might hinder
performance, recognition and validation w/r/t any specification.
(str8 face)
> Is SPC a printing character he wonders. It makes the printer head
> advance one unit, whereas ESC doesn't.
>  =20
SPACE is a printing character, ESC is a control-character.  All
control characters are *excluded* from the the class 'PRINT'.

> So at least mention the ASCII range [A-Z...] of what your are talking
> about. It would only take up a word or two of the INFO page.
>
> Anyway, each program might have their own idea of "printing characters"
> as well as grandpa down the hall's definition. So the user is left unsu=
re.
>  =20
In that regard, if each program has its own definition, then different
programs would find it hard to talk with each other.  In order for
programs to inter-operate with each other, it would be best if all
programs being used would use the same specification for details like
"printing character".  Having each program document shared and basic
definitions would tend to be redundant.  Instead the reader should be
aware of standards (such as character definitions and classifications)
for their platform.=20

Accordingly, it would be redundant to include extra information about
needed standards with each program.  No?  :-)

Message sent to bug-coreutils@HIDDEN:

Subject: bug#35343: sort: printing characters: define
In-Reply-To: <87zhokye79.5.fsf@HIDDEN>
Resent-From: =?UTF-8?Q?=E7=A9=8D=E4=B8=B9=E5=B0=BC?= Dan Jacobson <jidanni@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-coreutils@HIDDEN
Resent-Date: Sat, 27 Apr 2019 16:12:02 +0000
Resent-Message-ID: <handler.35343.B.155638148327141 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: L A Walsh <coreutils@HIDDEN>
Cc: 35343 <at> debbugs.gnu.org
From: =?UTF-8?Q?=E7=A9=8D=E4=B8=B9=E5=B0=BC?= Dan Jacobson <jidanni@HIDDEN>
References: <87zhokye79.5.fsf@HIDDEN> <5CC2A259.4060606@HIDDEN>
Date: Sat, 27 Apr 2019 23:57:20 +0800
Message-ID: <875zqz1lwf.8.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Well all I know is e.g., perl's man perlrecharclass is
more detailed than
(info "(coreutils) Character sets") section,
(which (info "(coreutils) sort invocation") perhaps should also link to.)
Anyways, coreutils should at least link to a definite statement...

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.