Hi Jeremie, Jeremie Courreges-Anglas wrote on Sat, May 28, 2016 at 04:56:52PM +0200: > "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. This matters even less. On OpenBSD, you could put almost arbitrary garbage in between without breaking anything, but i doubt we want to document that. Besides, running this program on OpenBSD outside the build makes very little sense in the first place. Maybe OpenBSD manuals are renowned for their quality and people using other systems will look at them? But then, will those other systems support the less strict syntax? I think researching that would be a waste of time. That said, feel free if you think it makes anything better. Yours, Ingo > 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"
