And another trivial one you can squash. --- man7/filename.7 | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/man7/filename.7 b/man7/filename.7 index 0e42e39d4..d60fe08eb 100644 --- a/man7/filename.7 +++ b/man7/filename.7 @@ -141,10 +141,10 @@ termination of options processing [see but when reprocessing of shell-command text requires requotation and re-escape, the workarounds become an inconvenient, confusing, error-prone hassle. -.P +.PP The use of conventional filenames averts the hassle. It also makes filenames more recognizable to experienced users. -.P +.PP This section introduces broadly observed conventions for filenames. .TP .B The POSIX Portable Filename Character Set @@ -284,7 +284,7 @@ or Further filenaming conventions are softer. Though often observed, such softer conventions can be bent or broken without rendering filenames unconventional. -.P +.PP This section introduces soft conventions for filenames. .TP .B Low line versus hyphen-minus @@ -409,7 +409,7 @@ Approximately, in brief, Unicode is a character set, UTF-8 is a byte-oriented scheme by which Unicode characters can be encoded, and ASCII is both a character set and a byte-oriented scheme that is a subset of both Unicode and UTF-8.] -.P +.PP To suggest an exact noninternational filenaming rule, other than the .BR iswgraph (3) rule, for every locale would exceed the scope of this manual page; but @@ -421,7 +421,7 @@ exclude spaces, control characters, ASCII symbols (like\~\fB$\fR or\~\fB=\fR), and ASCII punctuators other than the three punctuators POSIX recommends, such filenames will not normally cause trouble for tools and, thus, may be regarded as conventional within the local context. -.P +.PP The use of nonbreaking spaces like\~\fB\eu00A0\fR, \fB\eu2007\fR, \fB\eu202F\fR or\~\fB\euFEFF\fR in filenames is probably inadvisable for most locales, despite that @@ -447,9 +447,9 @@ You may have noticed the unconventionally-named .I lost+found directory lurking at a filesystem's root on your computer; and there are further examples, as well. -.P +.PP There are many reasons to use unconventional filenames. -.P +.PP It is hard to give a general rule, with respect to a particular context, as to which unconventional filenames are likely to cause practical troubles and which are not. @@ -514,7 +514,7 @@ POSIX.1-2008, SUSv4. .BR locale (7), .BR unicode (7), .BR utf-8 (7) -.P +.PP info .B coreutils .\" The author, Thaddeus H. Black, thanks his wife Kristie, daughter Naomi -- 2.33.0
