View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
00008671003.1(2013)/Issue7+TC1Shell and Utilitiespublic2014-08-22 13:442019-06-10 08:54
Reporterajosey Assigned To 
PrioritynormalSeverityEditorialTypeClarification Requested
Status ClosedResolutionAccepted As Marked 
NameAndrew Josey
OrganizationThe Open Group
User Referenceaustin-group-l:archive/latest/21398
Section2.6.2
Page Number2328
Line Number73947
Interp Status---
Final Accepted TextSee 0000867:0002397.
Summary0000867: typographical issue in Shell Command Language 2.6.2
DescriptionThe sentence in section 2.6.2 Parameter Expansion in the HTML
(and on page 2328, line 73947 in the PDF) is
inconsistently formatted, making one wonder about the intended
expansion in the example (which does become apparent after
a careful reading). The problem is in the sentence that reads:

 (For example, ${foo-bar} xyz} would result in the expansion
 of foo followed by the string xyz} if foo is set, else the
 string "barxyz}").

In the HTML, the strings foo-bar, xyz, foo, and barxyz} are in
bold, while the rest of the text is in normal weight font. There
also is a space between ${ and foo-bar, and between ${foo-bar}
and xyz}.

In the PDF, the strings foo-bar, xyz and foo are also in bold,
but the string barxyz} is in monospace and normal weight. There
are no extra spaces.

In both the HTML and the PDF, only the string barxyz} is quoted.

I would expect all the strings above to be in
monospace font, and both of the two possible results of the expansion,
namely "xyz}" and "barxyz}" to be quoted.
Desired ActionRe the spaces in the HTML, the troff for the master document is coded using "\c" as a no-space continuation, so this is a translation error in the HTML.

The troff coding has "foo" and "bar" consistently coded as filenames in this area; i.e., .Fi foo. Since this text is talking about strings rather than file names we could change that to quoted strings, but it needs a closer analysis.

A proposed change that would need to be confirmed follows.

Change from:

(For example, ${foo-bar}xyz} would result in the
 expansion of [b]foo[/b] followed by the string [b]xyz}[/b] if [b]foo[/b] is set, else the string "barxyz}").

to:

(For example, ${foo-bar}xyz} would result in the
 expansion of "foo" followed by the string "xyz}" if "foo" is set, else the string "barxyz}").

Tagstc2-2008

Activities

rhansen

2014-09-25 16:41

manager   bugnote:0002397

On page 2329 lines 73947-73947 delete:
(For example, ${foo-bar}xyz} would result in the expansion of foo followed by the string xyz} if foo is set, else the string <tt>"barxyz}"</tt>).

After page 2330 line 74013 add:
${parameter-word}
This example demonstrates the difference between unset and set to the empty string, as well as the rules for finding the delimiting close brace.
foo=asdf
echo ${foo-bar}xyz}
asdfxyz}
foo=
echo ${foo-bar}xyz}
xyz}
unset foo
echo ${foo-bar}xyz}
barxyz}

Issue History

Date Modified Username Field Change
2014-08-22 13:44 ajosey New Issue
2014-08-22 13:44 ajosey Name => Andrew Josey
2014-08-22 13:44 ajosey Organization => The Open Group
2014-08-22 13:44 ajosey User Reference => austin-group-l:archive/latest/21398
2014-08-22 13:44 ajosey Section => 2.6.2
2014-08-22 13:44 ajosey Page Number => 2328
2014-08-22 13:44 ajosey Line Number => 73947
2014-08-22 13:44 ajosey Interp Status => ---
2014-09-25 16:41 rhansen Note Added: 0002397
2014-10-02 15:11 Don Cragun Final Accepted Text => See 0000867:0002397.
2014-10-02 15:11 Don Cragun Status New => Resolved
2014-10-02 15:11 Don Cragun Resolution Open => Accepted As Marked
2014-10-02 15:11 Don Cragun Tag Attached: tc2-2008
2019-06-10 08:54 agadmin Status Resolved => Closed