A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1635 
====================================================================== 
Reported By:                steffen
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1635
Category:                   Base Definitions and Headers
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       steffen 
Organization:                
User Reference:              
Section:                    iconv 
Page Number:                1123 
Line Number:                38014 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2023-02-21 00:14 UTC
Last Modified:              2024-06-13 16:37 UTC
====================================================================== 
Summary:                    iconv: please be more explicit in
input-not-convertible case
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001007 iconv function not allowed to fail to c...
====================================================================== 

---------------------------------------------------------------------- 
 (0006817) eblake (manager) - 2024-06-13 16:37
 https://austingroupbugs.net/view.php?id=1635#c6817 
---------------------------------------------------------------------- 
Based on the discussions of the 2024-06-13 call, the Austin Group
understands the desire to have a means for an iconv() implementation that
stops early when a transliteration is not possible, despite recognizing
valid characters in the input.  Would it work to utilize a different errno
in this sequence, perhaps ENOTSUP or EPROTO, to make it easier for
applications to distinguish between a stop because of unrecognized input
(EILSEQ) vs unrepresentable output (the new errno)?

https://austingroupbugs.net/view.php?id=1635#c6812 mentioned ICONV_SET_* flags
on MacOS; that appears to be used
with a non-standard interface iconvctl(), and while it may be possible to
standardize that interface and a new ICONV_SET_* flag as a means for for
opting into the new errno value behavior, it seems like a much bigger
request at this time

Regarding the different defaults, we could add //NOTRANSLIT and make it
unspecified whether //TRANSLIT or //NOTRANSLIT is the default. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-02-21 00:14 steffen        New Issue                                    
2023-02-21 00:14 steffen        Name                      => steffen         
2023-02-21 00:14 steffen        Section                   => iconv           
2023-02-21 00:14 steffen        Page Number               => 1123            
2023-02-21 00:14 steffen        Line Number               => 38014           
2023-02-21 18:20 steffen        Note Added: 0006164                          
2023-03-06 16:35 nick           Relationship added       related to 0001007  
2024-06-11 23:42 bhaible        Note Added: 0006812                          
2024-06-11 23:47 bhaible        Note Added: 0006813                          
2024-06-12 00:16 bhaible        Note Added: 0006814                          
2024-06-12 00:24 bhaible        Note Added: 0006815                          
2024-06-13 16:37 eblake         Note Added: 0006817                          
======================================================================


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

Reply via email to