Looks good.
One question about your XRAT suggestion:
"For the utilities in IEEE Std 1003.1-2001..."
Do you mean to refer to only those utilites defined by the std.
or do you mean any utilities written to conform to the std. ?
mark
> -----Original Message-----
> From: Andrew Josey [mailto:yyyyyy@xxxxxxxxxxxxxxxxx]
> Sent: Sunday, June 08, 2003 3:43 AM
> To: yyyyyyyyyyyyyy@xxxxxxxxxxxxx
> Subject: Re: XSH ERN 92 (was: Minutes of the June 5th Teleconference)
>
>
> I've reviewed the .1-1996 text , the setlocale() man page and
> XBD Chapt 8.1
>
> I think this would lead to an additional CX shaded piece of text added
> as the 2nd last sentence to the DESCRIPTION in setlocale()
>
> [CX] Setting all of the categories of the locale of the
> process is similar
> to successively setting each individual category of the locale of the
> process, except that all error checking is done before any actions
> are performed. To set all the categories of the locale of the process,
> setlocale() is invoked as:
>
> setlocale(LC_ALL, "");
>
> In this case, setlocale() first verifies that the values of all
> the environment variables it needs according to the precedence rules,
> described in the Base Definitions Volume of IEEE Std
> 1003.1-8, Chapter 8,
> Environment Variables, indicate supported locales. If the
> value of any of
> these environment-variable searches yields a locale that is
> not supported
> (and nonnull), the setlocale() function returns a null pointer and the
> locale of the process is not changed. If all environment
> variables name
> supported locales, setlocale() then proceeds as if it had been called
> for each category, using the appropriate value from the associated
> environment variable or from the implementation-defined
> default if there
> is no such value. [/CX]
>
> Earlier in the DESCRIPTION we ought to consider
> changing
>
> "" Specifies an implementation-defined native environment. [CX]
> This corresponds to the value of the associated environment
> variables, LC_* and LANG ; see the Base Definitions volume
> of IEEE Std
> 1003.1-2001, Chapter 7, Locale and the Base Definitions
> volume of IEEE
> Std 1003.1-2001, Chapter 8, Environment Variables. [/CX]
>
> To:
>
> "" Specifies an implementation-defined native environment. [CX]
> The determination of the name of the new locale for the specified
> category depends on the value of the associated environment
> variables, LC_* and LANG ; see the Base Definitions volume
> of IEEE Std
> 1003.1-2001, Chapter 7, Locale and the Base Definitions
> volume of IEEE
> Std 1003.1-2001, Chapter 8, Environment Variables. [/CX]
>
> to make it a bit clearer (basically there is text is 8.2 )
>
> And add a SEE ALSO to Section 8.2 in XBD
>
> In XRAT
>
> We need to prefix the text....
>
> "If any of the environment variables are invalid, it makes sense to
> default to an implementation-defined, consistent locale
> environment....."
>
> With , "For the utilities in IEEE Std 1003.1-2001..."
>
> and Add text before that paragraph with .
>
> "The DESCRIPTION of setlocale() requires that when setting all
> categories of a locale,that if the value of any of
> the environment-variable searches yields a locale that is not
> supported
> (and nonnull), the setlocale() function returns a null pointer and the
> locale of the process is unchanged."
>
> Suggestions for better wording welcome
> regards
> Andrew
>
>
> On Jun 6, 11:29am in "XSH ERN 92 (was: Min", Geoff Clare wrote:
> > Andrew Josey <yyyyyy@xxxxxxxxxxxxxxxxx> wrote, on 06 Jun 2003:
> > >
> > > Subject: Minutes of the June 5th Teleconference
> > [snip]
> > >
> > > ERN 92 OPEN
> > > The test assertion has been round for a long time.
> > > Some concern about the wording in XRAT which appears to be
> > > about atuned to the utilities rather than setlocale().
> > > We need to identify wording changes for a clarification
> > > and if there is conflict between XSH/XBD we need to sort it.
> >
> > I thought the real problem here, as pointed out by Mark
> Funkenhauser,
> > was that some text from .1-1996 clause 8.1.2.2 has gone missing:
> >
> > 172 Setting all of the categories of the locale of the
> process is similar to successively
> > 173 setting each individual category of the locale of
> the process, except that all error
> > 174 checking is done before any actions are performed.
> To set all the categories of the
> > 175 locale of the process, setlocale() is invoked as:
> >
> > 176 setlocale(LC_ALL, "");
> >
> > 177 In this case, setlocale() first verifies that the
> values of all the environment vari-
> > 178 ables it needs according to the precedence above
> indicate supported locales. If the
> > 179 value of any of these environment-variable searches
> yields a locale that is not sup-
> > 180 ported (and nonnull), the setlocale() function
> returns a NULL pointer and the
> > 181 locale of the process is not changed. If all
> environment variables name supported
> > 182 locales, setlocale() then proceeds as if it had been
> called for each category, using
> > 183 the appropriate value from the associated
> environment variable or from the
> > 184 implementation-defined default if there is no such value.
> >
> > This text (and any other missing text from that clause)
> needs to be reinstated.
> >
> > --
> > Geoff Clare <yyyyyyy@xxxxxxxxxxxxx>
> > The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
> >-- End of excerpt from Geoff Clare
>
>
> -----
> Andrew Josey The Open Group
> Austin Group Chair Apex Plaza,Forbury Road,
> Email: yyyyyyy@xxxxxxxxxxxxx Reading,Berks.RG1
> 1AX,England
> Tel: +44 118 9508311 ext 2250 Fax: +44 118 9500110
>
|