"Todd C. Miller" <todd.mil...@courtesan.com> writes: > Currently, mklocale only ignores the first blank after the VARIABLE > definition. This means that we store the variable definition along > with the leading blanks. > > The lexer should eat the blanks after VARIABLE before storing the > variable definition.
ok The manpage documents the existing constraint, thus it should probably be amended. Index: mklocale.1 =================================================================== RCS file: /cvs/src/usr.bin/mklocale/mklocale.1,v retrieving revision 1.5 diff -u -p -p -u -r1.5 mklocale.1 --- mklocale.1 8 May 2016 15:25:44 -0000 1.5 +++ mklocale.1 28 May 2016 14:54:02 -0000 @@ -154,7 +154,7 @@ vendors of systems. .El .It Dv VARIABLE -This keyword must be followed by a single tab or space character, +This keyword must be followed by whitespace, after which encoding specific data is placed. Currently only the .Dv "EUC" -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
