View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
00000221003.1(2008)/Issue 7Base Definitions and Headerspublic2009-05-14 14:082013-04-16 13:06
ReporterDon Cragun Assigned To 
PrioritynormalSeverityCommentTypeError
Status ClosedResolutionAccepted As Marked 
NameDon Cragun
OrganizationSelf
User Reference
Section7.3.6
Page Number164
Line Number5141-5146
Interp Status
Final Accepted Text0000022:0000168
Summary0000022: yesexpr and noexpr clarification
DescriptionWayne Pollack (in austin-group-l email sequence #12110) reported that a
Weirdnix case of a user typing in the multi-line response:
    no
    Y
and getting a false positive when using the example in the locale
command description on XCU7 P2848, L93156-93163.

I say this is a Weirdnix case because most shell scripts will read a
single line response. But, the same issue could arise with responses
like "no or yes", "yes or no", etc. on single line responses.

However, there is a real issue in that the current descriptions of
yesexpr and noexpr imply that there is one and only correct affirmative
responsse, and one and only one negative response. The current settings
for these keywords in the POSIX locale accepts anything starting with
uppercase or lowercase "y" or "n", respectively (and this is the desired
behavior).
Desired ActionChange:
    "the acceptable"
on XBD7 P164, L5142 to:
    "an acceptable"
in the description of the yesexpr keyword.

Change:
    "the acceptable"
on P164, L5144-5145 to:
    "an acceptable"
in the description of the noexpr keyword.

Cross volume change:
Add a new paragraph to section A.7.3.6 LC_MESSAGES after XRAT7, P3463,
L116354:
    Affirmative responses like:
        y
        Yes
        Yes!
    and negative responses like:
        N
        No
        Never
        No way!
    should all be recognized as affirmative and negative responses,
    respectively, by the EREs identified by the yesexpr and noexpr
    keywords for English language based locales. There is no
    requirement that multi-line responses nor amgibuous responses
    like:
        no or yes
        yes or no
        maybe
    be correctly classified by either of these EREs. Application
    writers are encouraged to include locale specific suggestions
    for affirmative and negative responses in prompts.
Tagstc1-2008

Activities

Don Cragun

2009-07-30 15:49

manager   bugnote:0000168

Replace the first two changes in the Desired Action with the following
two changes. The change to the RATIONALE from the Desired Action should
also be applied.
Change:
    "an acceptable affirmative response"
on XBD7 P164, L5142 to:
    "acceptable affirmative responses"
in the description of the yesexpr keyword.

Change:
    "an acceptable negative response"
on P164, L5144-5145 to:
    "acceptable negative responses"
in the description of the noexpr keyword.

Issue History

Date Modified Username Field Change
2009-05-14 14:08 Don Cragun New Issue
2009-05-14 14:08 Don Cragun Name => Don Cragun
2009-05-14 14:08 Don Cragun Section => 7.3.6
2009-05-14 14:08 Don Cragun Page Number => 164
2009-05-14 14:08 Don Cragun Line Number => 5141-5146
2009-06-04 09:14 Don Cragun Tag Attached: real bug not in aardvark
2009-07-01 15:21 Don Cragun Organization => Self
2009-07-30 15:43 Don Cragun Tag Detached: real bug not in aardvark
2009-07-30 15:49 Don Cragun Note Added: 0000168
2009-07-30 15:49 Don Cragun Status New => Closed
2009-07-30 15:49 Don Cragun Resolution Open => Accepted As Marked
2009-07-30 15:50 Don Cragun Final Accepted Text => 0000022:0000168
2009-07-30 16:34 Don Cragun Status Closed => Resolved
2010-08-27 13:25 ajosey Tag Attached: tc1-2008
2013-04-16 13:06 ajosey Status Resolved => Closed