View Issue Details

IDProjectCategoryView StatusLast Update
0001658Issue 8 draftsShell and Utilitiespublic2024-06-11 09:12
Reporterrillig Assigned To 
PrioritynormalSeverityEditorialTypeClarification Requested
Status ClosedResolutionAccepted As Marked 
Product VersionDraft 3 
NameRoland Illig
Organization
User Reference
Section(several)
Page Number(several)
Line Number(several)
Final Accepted Text0001658:0006244
Summary0001658: spell 'white space' consistently
DescriptionDraft 3 contains 5 instances of the word 'whitespace' and 58 instances of the word 'white space'.

For consistency, only a single term should be used.
Desired ActionReplace 'whitespace' with 'white space'.
Tagsapplied_after_i8d3, issue8

Activities

geoffclare

2023-04-03 10:02

manager   bugnote:0006244

Last edited: 2023-06-05 16:22

On page 3066 line 102981 section m4, and
page 3066 line 102983 section m4, change:
whitespace characters
to:
white-space characters


On page 3112 line 104875 section make, change:
all whitespace at
to:
all white space at


On page 3114 line 104946 section make, change:
each whitespace-separated word
to:
each white-space-separated word


(I can only find the above four uses of "whitespace"; if there really is a fifth, please give the page and line number.)

rillig

2023-04-03 15:36

reporter   bugnote:0006247

The fifth instance may be on page 3689 lines 126884 to 126885.
Since it includes a line break, it may be spelled 'whitespace' or 'white-space', that's something I cannot see from the rendered PDF version.
But since there are only few hyphenations elsewhere, I assume that hyphenation is disabled in the original document.
In that case, the 4 uses you found are indeed all.

geoffclare

2023-04-03 16:36

manager   bugnote:0006250

> Since it includes a line break, it may be spelled 'whitespace' or 'white-space'

The corresponding line in the troff source is:

(such as the shell using white-space characters to delimit arguments,

kre

2023-04-03 17:04

reporter   bugnote:0006252

When working on this bug, please also consider whether make implementations
(in general) use "white space" in accordance with the definitions in XBD 3.412
(for "white space") and 3.414 (for "white-space"), or whether some have a
more restricted syntax allowed, in which case (if the make page doesn't
already redefine those terms) perhaps more care needs to be given to exactly
how they are used.

Note: this note is not intended to be any specific objection to anything,
I haven't read the make spec, and don't intend to (current versions of make,
all of them, annoy me) just pointing out something to be aware of, and perhaps
check ... many man pages (etc) say "white space" when they really just mean
space or tab (and sometimes newline) and don't intend (the code does not
implement) the full range of characters that the XBD definitions require.

Issue History

Date Modified Username Field Change
2023-03-31 09:40 rillig New Issue
2023-03-31 09:40 rillig Name => Roland Illig
2023-03-31 09:40 rillig Section => (several)
2023-03-31 09:40 rillig Page Number => (several)
2023-03-31 09:40 rillig Line Number => (several)
2023-04-03 10:02 geoffclare Note Added: 0006244
2023-04-03 15:36 rillig Note Added: 0006247
2023-04-03 16:36 geoffclare Note Added: 0006250
2023-04-03 17:04 kre Note Added: 0006252
2023-06-05 16:21 geoffclare Note Edited: 0006244
2023-06-05 16:22 geoffclare Note Edited: 0006244
2023-06-05 16:22 geoffclare Final Accepted Text => 0001658:0006244
2023-06-05 16:22 geoffclare Status New => Resolved
2023-06-05 16:22 geoffclare Resolution Open => Accepted As Marked
2023-06-05 16:23 geoffclare Tag Attached: issue8
2023-06-27 14:56 geoffclare Status Resolved => Applied
2023-06-27 14:56 geoffclare Tag Attached: applied_after_i8d3
2024-06-11 09:12 agadmin Status Applied => Closed