A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1220 
====================================================================== 
Reported By:                bhaible
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1220
Category:                   System Interfaces
Type:                       Omission
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Bruno Haible 
Organization:               GNU 
User Reference:              
Section:                    --- 
Page Number:                --- 
Line Number:                --- 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2018-12-20 13:46 UTC
Last Modified:              2020-10-26 14:50 UTC
====================================================================== 
Summary:                    Add an API to query the name of a locale category of
a locale object
====================================================================== 

---------------------------------------------------------------------- 
 (0005065) shware_systems (reporter) - 2020-10-26 14:50
 https://austingroupbugs.net/view.php?id=1220#c5065 
---------------------------------------------------------------------- 
Nothing in Note: 5037 implies multiple locale names are to be returned,
mimicing setlocale(). The LC_ALL and LANG environment values are just a
single name. That was someone's invention during that call this was the
intent and I agree it would be nonsensical to do it. We've even argued at
other times it's non-sensical for setlocale() to require it to begin with.

The primary reason this makes sense is it simplifies library routines that
modify aspects of a locale but then are expected to reset them to the
original LC_ALL value. Without a means to query the object for this name a
separate parameter to the function is required to specify that value, since
the function has no way of knowing a previous name returned after a change
is the same as that LC_ALL name, nor that LC_ALL in the environment hasn't
been modified. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2018-12-20 13:46 bhaible        New Issue                                    
2018-12-20 13:46 bhaible        Name                      => Bruno Haible    
2018-12-20 13:46 bhaible        Organization              => GNU             
2018-12-20 13:46 bhaible        Section                   => ---             
2018-12-20 13:46 bhaible        Page Number               => ---             
2018-12-20 13:46 bhaible        Line Number               => ---             
2020-10-05 11:11 geoffclare     Note Added: 0005026                          
2020-10-05 11:13 geoffclare     Note Edited: 0005026                         
2020-10-05 11:13 geoffclare     Note Edited: 0005026                         
2020-10-05 15:45 bhaible        Note Added: 0005027                          
2020-10-05 17:57 shware_systems Note Added: 0005030                          
2020-10-05 17:58 shware_systems Note Edited: 0005030                         
2020-10-07 13:29 geoffclare     Note Added: 0005035                          
2020-10-07 15:08 shware_systems Note Added: 0005037                          
2020-10-23 14:21 geoffclare     Note Added: 0005059                          
2020-10-23 15:57 shware_systems Note Added: 0005062                          
2020-10-26 10:03 geoffclare     Note Added: 0005063                          
2020-10-26 14:50 shware_systems Note Added: 0005065                          
======================================================================


  • [1003.1(2016... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to