commit: f7cbd623b8477919674855d0afe7eb8b50d01ada Author: Kerin Millar <kfm <AT> plushkava <DOT> net> AuthorDate: Mon Aug 11 00:38:28 2025 +0000 Commit: Kerin Millar <kfm <AT> plushkava <DOT> net> CommitDate: Mon Aug 11 00:38:48 2025 +0000 URL: https://gitweb.gentoo.org/proj/locale-gen.git/commit/?id=f7cbd623
Eliminate all unescaped line continuations from the man pages Presently, some of the paragraphs in the man pages are wrapped at the 80 column mark. However, the effect of an unescaped newline is significant. As groff(7) states, a newline "puts an inter-word space onto the output and, if filling is enabled, triggers end-of-sentence recognition on the preceding text." Address this issue by observing the status quo and refraining from wrapping the affected text. Signed-off-by: Kerin Millar <kfm <AT> plushkava.net> locale-gen.8 | 19 +++---------------- locale.gen.5 | 41 ++++++++++------------------------------- 2 files changed, 13 insertions(+), 47 deletions(-) diff --git a/locale-gen.8 b/locale-gen.8 index 51e573a..4d163dd 100644 --- a/locale-gen.8 +++ b/locale-gen.8 @@ -18,24 +18,11 @@ locale\-gen - safely compile and install a glibc locale archive .B \-V .YS .SH "DESCRIPTION" -The locale\-gen utility provides a means by which a system administrator may -conveniently manage the set of locales that are made available to the GNU C -Library. It accomplishes this by acting as a user-friendly frontend for the -standard \fBlocaledef\fR(1) utility, which is used to compile locales and -integrate them into a central archive. +The locale\-gen utility provides a means by which a system administrator may conveniently manage the set of locales that are made available to the GNU C Library. It accomplishes this by acting as a user-friendly frontend for the standard \fBlocaledef\fR(1) utility, which is used to compile locales and integrate them into a central archive. .P -A default installation of Gentoo Linux provides an archive that contains all -supported locales, numbering 500 or more. However, it is typical for an -administrator to require only one or two of these. In that case, the -\fI/etc/locale.gen\fR configuration file may be populated with a list of the -required locales. By default, locale\-gen shall read this file and compile only -the locales that are specified, saving both time and space in the longer term. +A default installation of Gentoo Linux provides an archive that contains all supported locales, numbering 500 or more. However, it is typical for an administrator to require only one or two of these. In that case, the \fI/etc/locale.gen\fR configuration file may be populated with a list of the required locales. By default, locale\-gen shall read this file and compile only the locales that are specified, saving both time and space in the longer term. .P -If the configuration file is missing, empty, or consists only of comments, -locale\-gen shall act in one of two ways, depending on whether the \fB\-c\fR -option was specified. If specified then locale\-gen shall abort with a suitable -diagnostic message. Otherwise, locale\-gen shall act as if the \fB\-A\fR option -had been specified. +If the configuration file is missing, empty, or consists only of comments, locale\-gen shall act in one of two ways, depending on whether the \fB\-c\fR option was specified. If specified then locale\-gen shall abort with a suitable diagnostic message. Otherwise, locale\-gen shall act as if the \fB\-A\fR option had been specified. .SH "OPTIONS" .TP \fB\-A\fR, \fB\-\-all\fR diff --git a/locale.gen.5 b/locale.gen.5 index e5bf25c..3eb25af 100644 --- a/locale.gen.5 +++ b/locale.gen.5 @@ -2,29 +2,15 @@ .SH "NAME" locale.gen - configuration file for locale\-gen .SH "DESCRIPTION" -The \fBlocale\-gen\fR(8) utility compiles the locales specified by the -\fI/etc/locale.gen\fR file and integrates them into a locale archive. +The \fBlocale\-gen\fR(8) utility compiles the locales specified by the \fI/etc/locale.gen\fR file and integrates them into a locale archive. .P -If present, the file must be comprised by zero or more lines, each of which -must be comprised by two fields, separated by one or more <blank> characters. -Leading and trailing <blank> characters are permitted. The first field shall be -considered as a \fIlocalename\fR and the second field as a \fIcharmap\fR. The -\fI/usr/share/i18n/SUPPORTED\fR file contains a complete list of the supported -combinations. +If present, the file must be comprised by zero or more lines, each of which must be comprised by two fields, separated by one or more <blank> characters. Leading and trailing <blank> characters are permitted. The first field shall be considered as a \fIlocalename\fR and the second field as a \fIcharmap\fR. The \fI/usr/share/i18n/SUPPORTED\fR file contains a complete list of the supported combinations. .P -Lines that are empty, or which contain only <blank> characters, shall be -disregarded. Lines that begin with zero or more <blank> characters, followed by -a <number\-sign> character, shall be considered as comments and disregarded. -Further, the two fields that form a locale definition may be followed by a -comment, provided that its leading <number\-sign> character is enclosed by -<blank> characters. +Lines that are empty, or which contain only <blank> characters, shall be disregarded. Lines that begin with zero or more <blank> characters, followed by a <number\-sign> character, shall be considered as comments and disregarded. Further, the two fields that form a locale definition may be followed by a comment, provided that its leading <number\-sign> character is enclosed by <blank> characters. .P -The definition of a <blank> character is that it is either the <tab> or <space> -character. +The definition of a <blank> character is that it is either the <tab> or <space> character. .SH "LOCALE NAMES" -The GNU C Library employs a locale naming scheme that is based upon the X/Open -Common Applications Environment (CAE) Portability Guide Issue 4 (XPG4) -specification. A \fIlocalename\fR is composed of between one and four parts. +The GNU C Library employs a locale naming scheme that is based upon the X/Open Common Applications Environment (CAE) Portability Guide Issue 4 (XPG4) specification. A \fIlocalename\fR is composed of between one and four parts. .P .RS .EX @@ -32,22 +18,15 @@ language[_territory][.codeset][@modifier] .EE .RE .P -A complete list of supported \fIlocalename\fR values can be obtained by reading -the first column of the \fI/usr/share/i18n/SUPPORTED\fR file. +A complete list of supported \fIlocalename\fR values can be obtained by reading the first column of the \fI/usr/share/i18n/SUPPORTED\fR file. .P -Assuming that a given locale is available, it can be effected by assigning its -\fIlocalename\fR to the LANG environment variable. +Assuming that a given locale is available, it can be effected by assigning its \fIlocalename\fR to the LANG environment variable. .SH "CHARACTER MAPS" -A \fIcharmap\fR, also known as a character set or codeset, is a mapping of -character symbols and collating element symbols to actual character encodings, -allowing for computers to encode and decode text in a standard way. +A \fIcharmap\fR, also known as a character set or codeset, is a mapping of character symbols and collating element symbols to actual character encodings, allowing for computers to encode and decode text in a standard way. .P -A complete list of supported \fIcharmap\fR values can be obtained by reading -the second column of the \fI/usr/share/i18n/SUPPORTED\fR file. +A complete list of supported \fIcharmap\fR values can be obtained by reading the second column of the \fI/usr/share/i18n/SUPPORTED\fR file. .P -Given that not all values of \fIlocalename\fR incorporate a codeset, the -configuration file requires for the second field of each line to define a -\fIcharmap\fR. +Given that not all values of \fIlocalename\fR incorporate a codeset, the configuration file requires for the second field of each line to define a \fIcharmap\fR. .SH "EXAMPLES" .EX # This is a comment, followed by some valid locale declarations.
