[1003.1(2013)/Issue7+TC1 0000867]: typographical issue in Shell Command Language 2.6.2

[Austin Group Bug Tracker]

The following issue has been SUBMITTED.
======================================================================
http://www.austingroupbugs.net/view.php?id=867
======================================================================
Reported By: ajosey
Assigned To:
======================================================================
Project: 1003.1(2013)/Issue7+TC1
Issue ID: 867
Category: Shell and Utilities
Type: Clarification Requested
Severity: Editorial
Priority: normal
Status: New
Name: Andrew Josey
Organization: The Open Group
User Reference: austin-group-l:archive/latest/21398
Section: 2.6.2
Page Number: 2328
Line Number: 73947
Interp Status: ---
Final Accepted Text:
======================================================================
Date Submitted: 2014-08-22 13:44 UTC
Last Modified: 2014-08-22 13:44 UTC
======================================================================
Summary: typographical issue in Shell Command Language 2.6.2
Description:
The 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 Action:
Re 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}").


======================================================================

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 => ---
======================================================================