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 16:16 UTC
====================================================================== 
Summary:                    Add an API to query the name of a locale category of
a locale object
====================================================================== 

---------------------------------------------------------------------- 
 (0005067) geoffclare (manager) - 2020-10-26 16:16
 https://austingroupbugs.net/view.php?id=1220#c5067 
---------------------------------------------------------------------- 
Re note 5065, environment variables are not always used (and if they are
used, then they can simply be queried with getenv()). If an application
calls:<pre>setlocale(LC_NUMERIC, locale1);
setlocale(LC_TIME, locale2);</pre>then getlocalename_l(LC_ALL,
LC_GLOBAL_LOCALE) would have to return, somehow, the information that the
locale name for LC_NUMERIC is locale1, for LC_TIME is locale2, and for all
other categories is "C" or "POSIX".

With locale objects, in order to modify a locale and restore later there is
no need to query locale names. It can be done using the existing locale_t
handling functions (i.e. duplocale(), newlocale(), uselocale(), and
freelocale()). 

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                          
2020-10-26 16:16 geoffclare     Note Added: 0005067                          
======================================================================


  • [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