The following issue has been CLOSED. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1791 
====================================================================== 
Reported By:                calestyo
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1791
Category:                   Shell and Utilities
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     Closed
Name:                       Christoph Anton Mitterer 
Organization:                
User Reference:              
Section:                    Shells and Utilities 
Page Number:                3427, ff. 
Line Number:                116995, ff. 
Final Accepted Text:         
Resolution:                 Rejected
Fixed in Version:           
====================================================================== 
Date Submitted:             2023-12-07 04:34 UTC
Last Modified:              2024-01-22 17:06 UTC
====================================================================== 
Summary:                    tr: clarify encdings of non-characters bytes and
proper encodings of the NUL byte and
====================================================================== 

---------------------------------------------------------------------- 
 (0006634) Don Cragun (manager) - 2024-01-22 17:06
 https://www.austingroupbugs.net/view.php?id=1791#c6634 
---------------------------------------------------------------------- 
<blockquote>NUL is not a special case; NUL is a character in every locale. 
The standard says that the strings specified by <i>string1</i> and
<i>string2</i> contain characters.  A single character in those strings may
be represented by one or more adjacent octal sequences that represent
individual bytes of a multi-byte character. The notes in the APPLICATION
USAGE and in the RATIONALE specify that <tt>tr -d '\000'</tt> must remove
NUL characters from the input stream.  This would also work with <tt>tr -d
'\0</tt>' and <tt>tr -d '\00'</tt>.  But if one wanted to remove NUL
characters and the character '1', one would have to use <tt>tr -d
'\0001'</tt> (or put the '1' before the octal escape sequence for the NUL
character, e.g. <tt>tr -d '1\0'</tt>); not <tt>tr -d '\01'</tt> or <tt>tr
-d '\001'</tt>.
Therefore, this bug is rejected.</blockquote> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-12-07 04:34 calestyo       New Issue                                    
2023-12-07 04:34 calestyo       Name                      => Christoph Anton
Mitterer
2023-12-07 04:34 calestyo       Section                   => Shells and
Utilities
2023-12-07 04:34 calestyo       Page Number               => 3427, ff.       
2023-12-07 04:34 calestyo       Line Number               => 116995, ff.     
2024-01-22 17:06 Don Cragun     Note Added: 0006634                          
2024-01-22 17:06 Don Cragun     Status                   New => Closed       
2024-01-22 17:06 Don Cragun     Resolution               Open => Rejected    
======================================================================


  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to