Re: LC_CTYPE=UTF-8

2020-12-12 Thread k...@keldix.com via austin-group-l at The Open Group
iso 30112 has a 10646 i18n locale which is implemented in glibc, and which 
should be used.

keld

On Sun, Dec 13, 2020 at 04:35:08AM +, Thorsten Glaser via austin-group-l at 
The Open Group wrote:
> Martijn Dekker dixit:
> 
> > Datapoint: AT ksh93 has a C.UTF-8 locale built in which it handles
> > internally. I suppose that could be considered a precedent of sorts.
> 
> Datapoint:
> 
> I proposed to add a C.UTF-8 locale to eglibc via Debian, almost a
> decade ago.
> 
> Debian???s GNU libc packages have been shipping C.UTF-8 since about
> 2013 or so, and there have been numerous problems with its precise
> implementation (as it turns out that it???s *extremely* tricky to
> implement correctly, FSVO correct).
> 
> Please contact Aurélien Jarno, who has been maintaining this, for
> any detail information on this, how this has evolved and why and
> consider to standardise this existing variant (possibly bugfixing
> it where, if at all, necessary).
> 
> bye,
> //mirabilos
> -- 
> 22:20??? The crazy that persists in his craziness becomes a master
> 22:21??? And the distance between the craziness and geniality is
> only measured by the success 18:35??? "Psychotics are consistently
> inconsistent. The essence of sanity is to be inconsistently inconsistent



Re: LC_CTYPE=UTF-8

2020-12-12 Thread Thorsten Glaser via austin-group-l at The Open Group
Martijn Dekker dixit:

> Datapoint: AT ksh93 has a C.UTF-8 locale built in which it handles
> internally. I suppose that could be considered a precedent of sorts.

Datapoint:

I proposed to add a C.UTF-8 locale to eglibc via Debian, almost a
decade ago.

Debian’s GNU libc packages have been shipping C.UTF-8 since about
2013 or so, and there have been numerous problems with its precise
implementation (as it turns out that it’s *extremely* tricky to
implement correctly, FSVO correct).

Please contact Aurélien Jarno, who has been maintaining this, for
any detail information on this, how this has evolved and why and
consider to standardise this existing variant (possibly bugfixing
it where, if at all, necessary).

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent



Minutes of the 10th December 2020 Teleconference

2020-12-12 Thread Andrew Josey via austin-group-l at The Open Group
All
Enclosed are the minutes of the Thursday meeting this week
regards
Andrew


Minutes of the 10th December 2020 Teleconference Austin-1087 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 12th December 2020

Attendees:
Don Cragun, IEEE PASC OR
Joerg Schilling, FOKUS Fraunhofer
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Andrew Josey, The Open Group
Geoff Clare, The Open Group
Richard Hansen
Mark Ziegast, SHware Systems Dev.


Apologies:
Tom Thompson, IEEE
Eric Blake, Red Hat, The Open Group OR
Eric Ackermann

* General news 

We agreed that the 17th December meeting will be the last meeting before the 
New Year.

* Outstanding actions

(Please note that this section has been flushed to shorten the minutes -
to locate the previous set of outstanding actions, look to the minutes
from 13th June 2019 and earlier)

Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR 
list" OPEN
https://austingroupbugs.net/view.php?id=1254
Action: Joerg to investigate how his shell behaves.

Bug 700 - Nick to raise this issue with the C committee
Bug 713 - Nick to raise with the C committee.
Bug 739 - Nick to raise with the C committee.


* Current Business


Bug 1347: stderr access mode - "is expected to be" is not definedAccepted 
as Marked
https://austingroupbugs.net/view.php?id=1347

This item is tagged for TC3-2008.

On page 65 before line 1912 (XBD "interactive shell") insert a new definition 
and renumber the remaining:

Interactive Device

A terminal device.

Note: This definition is intended to align with the ISO C standard's use of 
"interactive device".

On page 496 lines 17224-17228 (XSH 2.5 Standard I/O Streams) and
page 2017 lines 64723-64727 (XSH stderr, stdin, stdout DESCRIPTION)
change:
At program start-up, three streams shall be predefined and need
not be opened explicitly: standard input (for reading conventional
input), standard output (for writing conventional output), and
standard error (for writing diagnostic output). When opened,
the standard error stream is not fully buffered; the standard
input and standard output streams are fully buffered if and
only if the stream can be determined not to refer to an interactive
device.
to:
At program start-up, three streams shall be predefined and
already open: stdin (standard input, for conventional input)
for reading, stdout (standard output, for conventional output)
for writing, and stderr (standard error, for diagnostic output)
for writing. When opened, stderr shall not be fully buffered;
stdin and stdout shall be fully buffered if and only if [CX]the
file descriptor associated with the stream is determined not
to be associated with an interactive device.[/CX]


On page 2017 line 64733 (XSH stdin DESCRIPTION), change:
The stderr stream is expected to be open for reading and writing.
to:

These file descriptors are often all associated with a single
open file description which has access mode O_RDWR (e.g., in
the case of a terminal device for a login shell). However, the
stderr, stdin, and stdout streams need not be opened for both
reading and writing at program start-up in this case.


On page 2017 line 64747 (stdin SEE ALSO) add isatty().


Bug 1348: "the exec() family of functions" should not include "()"Accept
https://austingroupbugs.net/view.php?id=1348

This item is tagged TC3-2008.

Bug 1367: mailx: add -E option to discard (not send) empty messages
https://austingroupbugs.net/view.php?id=1367

This item is tagged Issue 8.

On page 2943 line 97431 (mailx SYNOPSIS) change:
mailx [−s subject] address...

to:
mailx [-E] [−s subject] address...


On page 2944, insert after line 97471:
-E Discard messages with an empty message body.


On page 2964 line 98259 (mailx EXIT STATUS) change:
Successful completion; note that this status implies that all
messages were sent, ...

to:
Successful completion; note that in Send Mode this status implies
that all messages were either sent or successfully discarded
(see -E), ...


Bug 1368: Unworldly use of redirection and mailx(1) in at(1) and batch(1) 
examples. OPEN
https://austingroupbugs.net/view.php?id=1368


We started this item and will continue next time


Gettext draft.

We will return to this on a future call.

The gettext draft in the etherpad is at

https://posix.rhansen.org/p/gettext_draft
https://posix.rhansen.org/p/gettext_split

Next Steps 
--

The next calls are on:



December 14th 2020 (Monday) 
This call will be for 60 minutes.

December 17th 2020 (Thursday)
This call will be for 90 minutes.

This will be the last call before the New Year.

January 4th 2021 (Monday) 
This call will be for 60 minutes.

Apologies in advance:
Tom Thompson (rest of December).

Calls are anchored on US time. (8am Pacific) 

Please check the calendar invites for dial in details.

Bugs are