[Issue 8 drafts 0001524]: open() flags used by fopen()

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1524 == Reported By:Don Cragun Assigned To: =

[Issue 8 drafts 0001524]: open() flags used by fopen()

The following issue has been set as RELATED TO issue 0001302. == https://austingroupbugs.net/view.php?id=1524 == Reported By:Don Cragun Assig

[1003.1(2016/18)/Issue7+TC2 0001302]: Alignment with C17

The following issue has been set as RELATED TO issue 0001524. == https://austingroupbugs.net/view.php?id=1302 == Reported By:geoffclare Assig

Minutes of the 6th January 2022 Teleconference

All Enclosed are the minutes of yesterday’s teleconference regards Andrew -- Minutes of the 6th January 2022 Teleconference Austin-1188 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 7th January 2022 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC

Re: Future of locale, will there be POSIX.utf-8, what will it bring?

The first Issue 8 draft is focusing, afaik, on adding the C1x changes and Mantis Issue 8 tagged items. The changes to XBD 6, 7, etc., that will formally add a POSIX UTF8 locale are to be part of the second, maybe third, draft. This is why you don't see them yet. For maximum compatibility with ex

Re: Future of locale, will there be POSIX.utf-8, what will it bring?

Hello. shwaresyst wrote in <1494661216.220561.1641574109...@mail.yahoo.com>: [i resort a bit] | On Thu, Jan 6, 2022 at 3:40 PM, Steffen Nurpmeso via austin-group-l \ | at The Open Group wrote: Hello! | |I wonder about POSIX.utf-?8, i tried to remember any statement |i had read, and Manti

Re: Future of locale, will there be POSIX.utf-8, what will it bring?

C11 tried to add the minimal support for UTF-8, with the u8 string constant prefix, but in a broken manner. C2x provides what can be considered a fix for this, but does it in a mostly unusable way from the aspect of supporting multiple locale languages. That is why you don't see anything about a

[1003.1(2016/18)/Issue7+TC2 0001544]: uudecode: standardise or at least reserve - as another special symbol for decoding to stdout

The following issue has been SUBMITTED. == https://www.austingroupbugs.net/view.php?id=1544 == Reported By:calestyo Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001545]: sed: standardise or at least reserve -E with sed for use of EREs

The following issue has been SUBMITTED. == https://www.austingroupbugs.net/view.php?id=1545 == Reported By:calestyo Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|

The following issue has been SUBMITTED. == https://www.austingroupbugs.net/view.php?id=1546 == Reported By:calestyo Assigned To: