Hello Branden, On Fri, 29 Jul 2022 15:58:23 -0500 G. Branden Robinson wrote: >> -The VFS imposes limitations that an attribute names is limited to 255 bytes >> -and an attribute value is limited to 64\ kB. >> +The VFS-imposed limits on attribute names and values are 255 bytes >> +and 64\ kB, respectively. > > While you're tidying this up, I would convert the `\ ` escape sequence > to `\~`. Both are non-breaking spaces, but the latter is adjustable. > > groff_man(7) from groff 1.22.4 says: > > \~ Adjustable, non-breaking space character. Use this escape to > prevent a break inside a short phrase or between a numerical > quantity and its corresponding unit(s). > > Before starting the motor, set the output speed to\~1. > There are 1,024\~bytes in 1\~kiB. > CSTR\~#8 documents the B language. Thank you for the review! I think I disagree: IMO a number+unit should be treated as a single entity both semantically/logically and typographically (at least as far as space stretching goes), i.e., say (if I understand the effect of '\ ' and '\~' right), 255 bytes and 64 kB, respectively. would make a bit more sense to me than 255 bytes and 64 kB, respectively. Current Linux man-pages usage doesn't appear quite consistent, but '\ ' prevails over '\~' (about 6:1), and my cursory grep found only one instance of '\~' used between a number and its unit (vs. many instances of '\ ' in that context). In view of the above, failing any instruction from a man-pages maintainer to the contrary, I'd prefer leaving this as is. With best wishes, Štěpán
