A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1741 
====================================================================== 
Reported By:                ajosey
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1741
Category:                   System Interfaces
Type:                       Error
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Andrew Josey 
Organization:                
User Reference:             ISO/US-003 
Section:                    3 
Page Number:                1137 
Line Number:                38955-38956 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2023-05-31 17:13 UTC
Last Modified:              2023-07-18 16:18 UTC
====================================================================== 
Summary:                    getlocalename_l (ISO/US-003)
====================================================================== 

---------------------------------------------------------------------- 
 (0006393) geoffclare (manager) - 2023-07-18 16:18
 https://austingroupbugs.net/view.php?id=1741#c6393 
---------------------------------------------------------------------- 
Since the specification for getlocalename_l() in the draft was based on the
__getlocalename_l() function in Solaris 11.4, I checked how that function
behaves when called with LC_ALL. It does actually do what is being asked
for here, i.e. it returns the same string that setlocale() would return for
the equivalent global locale setting:
<pre>$ LC_TIME=en_GB LC_MONETARY=en_US ./a.out
__getlocalename_l: /C/C/en_GB/C/en_US/C
setlocale        : /C/C/en_GB/C/en_US/C</pre>
So I am in favour of making a normative text change along the lines
suggested.

However, I am dubious about the suggested rationale addition of a use case
in recording the information, as there is no requirement that the string
contains printable characters, and storing it for use in a later
setlocale() call (by another process) would be fragile, as a future OS
upgrade could change the string format. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-05-31 17:13 ajosey         New Issue                                    
2023-05-31 17:13 ajosey         File Added: ISO_IEC CD 9945 Collated
Comments.doc                    
2023-05-31 17:13 ajosey         Name                      => Andrew Josey    
2023-05-31 17:13 ajosey         User Reference            => ISO/US-003      
2023-05-31 17:13 ajosey         Section                   => 3               
2023-05-31 17:13 ajosey         Page Number               => na              
2023-05-31 17:13 ajosey         Line Number               => na              
2023-07-17 23:17 Don Cragun     Page Number              na => 1137          
2023-07-17 23:17 Don Cragun     Line Number              na => 38955-38956   
2023-07-18 16:18 geoffclare     Note Added: 0006393                          
======================================================================


  • [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
    • [Issue ... 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
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to