Re: POSIX gettext: a typo

[Geoff Clare via austin-group-l at The Open Group]

Bruno Haible  wrote, on 12 May 2022:
>
> https://posix.rhansen.org/p/gettext_draft
> Line 668
> 
> Typo: msgid_pural -> msgid_plural

Thanks for spotting this.  It was corrected in today's teleconference.

-- 
Geoff Clare 
The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England

Re: POSIX gettext() and NLSPATH

[Geoff Clare via austin-group-l at The Open Group]

Bruno Haible wrote, on 12 May 2022:
>
> https://posix.rhansen.org/p/gettext_draft
> Line 130
> "indicates that catopen( ) should look ..."
> What does the gettext family of functions do when NLSPATH is set to this
> value?
> 
> Line 136
> "indicates that the gettext family of functions ..."
> What does the catopen() function when NLSPATH is set to this value?
> 
> There is some explanation in example 5. But IMO it's not immediately clear
> how this applies to example 1 and example 2.

This was discussed in today's teleconference. The intention is that
examples 1 and 3 show what an application writer/user might set NLSPATH
to for an application that uses catopen() but doesn't use gettext.
And vice versa for 2 and 4.

Example 5 is the only one aimed at applications that use both catopen()
and gettext, which is why it is the only one that has mention of how
each deals with the part of NLSPATH meant for the other.

We added text after each "Example ..." heading to make it clear which
type of application the example is aimed at.

-- 
Geoff Clare 
The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England

[1003.1(2016/18)/Issue7+TC2 0001254]: "asynchronous list" description uses "command" instead of "AND-OR list"

[Austin Group Bug Tracker via austin-group-l at The Open Group]

A NOTE has been added to this issue. 
== 
https://austingroupbugs.net/view.php?id=1254 
== 
Reported By:stephane
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1254
Category:   Shell and Utilities
Type:   Error
Severity:   Objection
Priority:   normal
Status: New
Name:   Stephane Chazelas 
Organization:
User Reference:  
Section:2.9.3.1 Asynchronous Lists 
Page Number:2370 (in 2018 edition, not 2016) 
Line Number:the whole 2.9.3.1 section and also 76177 (execution
environment), 115763 (wait), 128448 (rationale), 74883 ($!) 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2019-06-08 09:14 UTC
Last Modified:  2022-06-06 09:48 UTC
== 
Summary:"asynchronous list" description uses "command"
instead of "AND-OR list"
==
Relationships   ID  Summary
--
related to  760 asynchronous list assignment of stdin s...
== 

-- 
 (0005845) geoffclare (manager) - 2022-06-06 09:48
 https://austingroupbugs.net/view.php?id=1254#c5845 
-- 
Proposed changes...

On page 38 line 1270 section 3.33 Background Job, change:See
Background Process Group in [xref to
3.35].to:In the context of the System Interfaces
volume of POSIX.1-202x, a background process group (see [xref to 3.35]).

In the context of the shell, a job that the shell is not waiting for before
it executes further commands or, if interactive, prompts for further
commands. A background job can be a job-control background job or a
non-job-control background job. A job-control background job is a job that
started execution (either in the background or the foreground) while job
control was enabled and is currently in the background. A non-job-control
background job is an asynchronous AND-OR list that started execution while
job control was disabled and was assigned a job number. An implementation
need not support non-job-control background jobs; that is, the shell may,
but need not, assign job numbers to asynchronous AND-OR lists that start
execution while job control is disabled.

Note: Asynchronous AND-OR lists are defined in detail in
[xref to XCU 2.9.3.1].

Note: See also [xref to 3.182 Foreground Job], [xref to 3.202
Job], [xref to 3.203 Job Control], and [xref to 3.379 Suspended
Job].
On page 38 line 1273 section 3.35, change:Background Process
Group (or Background Job)to:Background Process
Group
On page 38 line 1275 section 3.35, add a new
paragraph:Note: See also [xref to 3.33 Background
Job].
On page 62 line 1849 section 3.182 Foreground Job, change:See
Foreground Process Group in [xref to
3.184].to:In the context of the System Interfaces
volume of POSIX.1-202x, a foreground process group (see [xref to 3.184]).

In the context of the shell, a job that the shell is waiting for before it
executes further commands or, if interactive, prompts for further
commands.

Note: See also [xref to 3.33 Background Job], [xref to 3.202
Job], and [xref to 3.379 Suspended Job].
On page 62 line 1852 section 3.184, change:Foreground Process
Group (or Foreground Job)to:Foreground Process
Group
On page 62 line 1857 section 3.184, add a new
paragraph:Note: See also [xref to 3.182
Foreground Job].
On page 65 line 1924 section 3.202 Job, change:A set of
processes, comprising a shell pipeline, and any processes descended from
it, that are all in the same process group.

Note: See also [xref to XCU 2.9.2
Pipelines].to:A background job, a
foreground job, or a suspended job.

In the context of the shell, jobs are created when a list (see [xref to XCU
2.9.3 Lists]) is executed while job control is enabled, and may be created
when an asynchronous AND-OR list is executed while job control is
disabled.

Note: Job control in the shell is defined in detail in [xref
to XCU 2.11 Job Control].

Note: See also [xref to 3.33 Background Job], [xref to 3.182
Foreground Job], and [xref to 3.379 Suspended Job].
After page 65 line 1931 section 3.203 Job Control, add:The term
is also used in connection with system interfaces that can be used by a
command interpreter to implement