GNU bug report logs - #48248
tr docs: mention what to expect now vs. future

Previous Next

Package: coreutils;

Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>

Date: Thu, 6 May 2021 00:54:02 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 48248 in the body.
You can then email your comments to 48248 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-coreutils <at> gnu.org:
bug#48248; Package coreutils. (Thu, 06 May 2021 00:54:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Thu, 06 May 2021 00:54:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-coreutils <at> gnu.org
Subject: tr docs: mention what to expect now vs. future
Date: Thu, 06 May 2021 07:00:04 +0800
(info "(coreutils) tr invocation") says
   Currently ‘tr’ fully supports only single-byte characters.
   Eventually it will support multibyte characters; when it does, the ‘-C’

And the man page has no warning at all. #BUG. Please add one.

BTW,

$ echo 哇|tr 哇 123
123

It works fine! (People will think.)

Therefore be sure to mention just when it will start failing, with real examples,

$ echo 哇|tr 哇 1
111
$ echo 哇|tr 哇 1234
123
$ echo 哇哇|tr 哇 1234
123123
$ echo 哇哇姑五湖|tr 哇 1234
1231231__五湖

$ echo "22°56'52.2\"N 121°14'09.3\"E" | tr ° d
22dd56'52.2"N 121dd14'09.3"E

Also on the INFO page, give examples of, for the same input,
what to expect now, and what to expect in the future.




Reply sent to Paul Eggert <eggert <at> cs.ucla.edu>:
You have taken responsibility. (Mon, 14 Feb 2022 20:20:02 GMT) Full text and rfc822 format available.

Notification sent to 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>:
bug acknowledged by developer. (Mon, 14 Feb 2022 20:20:02 GMT) Full text and rfc822 format available.

Message #10 received at 48248-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 48248-done <at> debbugs.gnu.org
Subject: Re: bug#48248: tr docs: mention what to expect now vs. future
Date: Mon, 14 Feb 2022 12:18:46 -0800
[Message part 1 (text/plain, inline)]
Thanks for the bug report. This stuff about "the future" has been there 
for years so it's time to remove any predictions. I installed the 
attached revamp of the tr documentation to try to address the problems 
you mentioned, plus some others I noticed while in the neighborhood.
[0001-tr-improve-multibyte-etc.-doc.patch (text/x-patch, attachment)]
[0002-tr-mention-multibyte-problem-in-man-page.patch (text/x-patch, attachment)]

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 15 Mar 2022 11:24:07 GMT) Full text and rfc822 format available.

This bug report was last modified 2 years and 14 days ago.

Previous Next


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