A NOTE has been added to this issue. ====================================================================== http://austingroupbugs.net/view.php?id=1222 ====================================================================== Reported By: stephane Assigned To: ====================================================================== Project: 1003.1(2016)/Issue7+TC2 Issue ID: 1222 Category: Shell and Utilities Type: Enhancement Request Severity: Objection Priority: normal Status: Resolved Name: Stephane Chazelas Organization: User Reference: Section: echo utility Page Number: echo Line Number: echo Interp Status: --- Final Accepted Text: http://austingroupbugs.net/view.php?id=1222#c4375 Resolution: Accepted As Marked Fixed in Version: ====================================================================== Date Submitted: 2018-12-27 23:49 UTC Last Modified: 2019-04-29 20:19 UTC ====================================================================== Summary: "echo" specification doesn't reflect current implementations (missing -e, -E and - handling) ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001206 The echo that supports -n is Bell Labs ... ======================================================================
---------------------------------------------------------------------- (0004378) stephane (reporter) - 2019-04-29 20:19 http://austingroupbugs.net/view.php?id=1222#c4378 ---------------------------------------------------------------------- Re: http://austingroupbugs.net/view.php?id=1222#c4375 That resolution doesn't seem to address the encoding issue. BIG5 α (Greek alpha U+03B1) is encoded as 0xA8 0x5C and BIG5 \ (backslash U+005C) is 0x5C. In echo αc in a locale that uses the BIG5 as charset, do the "operands contain a <backslash> character" (encoding 0x5C) as virtually all echo implementations think it does, or does it not? Do you want me to raise a separate bug for that? Could you please state the Austin Group position on that in this bug, even if it doesn't end up in the text of the specification? Issue History Date Modified Username Field Change ====================================================================== 2018-12-27 23:49 stephane New Issue 2018-12-27 23:49 stephane Name => Stephane Chazelas 2018-12-27 23:49 stephane Section => echo utility 2018-12-27 23:49 stephane Page Number => echo 2018-12-27 23:49 stephane Line Number => echo 2019-03-01 10:04 stephane Note Added: 0004272 2019-04-01 16:33 nick Relationship added related to 0001206 2019-04-25 16:17 eblake Note Added: 0004370 2019-04-25 21:46 stephane Note Added: 0004372 2019-04-26 08:49 geoffclare Note Added: 0004373 2019-04-29 15:39 geoffclare Note Added: 0004375 2019-04-29 15:40 geoffclare Note Edited: 0004375 2019-04-29 15:41 geoffclare Interp Status => --- 2019-04-29 15:41 geoffclare Final Accepted Text => http://austingroupbugs.net/view.php?id=1222#c4375 2019-04-29 15:41 geoffclare Status New => Resolved 2019-04-29 15:41 geoffclare Resolution Open => Accepted As Marked 2019-04-29 15:42 geoffclare Tag Attached: issue8 2019-04-29 20:11 stephane Note Added: 0004377 2019-04-29 20:19 stephane Note Added: 0004378 ======================================================================
