[Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information

[Alexander Gattin]

On Fri, Mar 18, 2005 at 11:18:23PM +0100, Nicolas Fran=C3=A7ois wrote:
> On Fri, Mar 18, 2005 at 09:43:29PM +0100, Tomasz K=C5=82oczko wrote:
> > English isn't my native language so it will be good if someone will v=
erify
> > below patch before I'll commit this to shadow CVS tree.
...
> > Any volunteers on update non-english passwd(5) ? (pl is
> > mine :o)
> >=20
> > $ ls -1 */passwd.5
> > cs/passwd.5
> > fr/passwd.5
> > it/passwd.5
> > ja/passwd.5
> > ko/passwd.5
> > pl/passwd.5
> > ru/passwd.5

I may look at Russian/Ukrainian version. But I don't
promise, because now I have very urgent jub.

> > --- passwd.5    11 Dec 2004 20:05:01 -0000      1.13
> > +++ passwd.5    18 Mar 2005 20:25:48 -0000
> > @@ -48,9 +48,13 @@
> >  .PP
> >  The password field may not be filled if shadow passwords have been e=
nabled.

I have a question on the above. What does "may not be"
mean?
Does it mean slightly stronger negation than "should not
be"?
Does the phrase relate to _action_ [on the field] or to
_state_ [of the field]?
If former, then "MUST NOT be" (as for RFC conventions),
should probably be used instead.
If latter, then "MUST be empty when", or "IS empty
when" may be used.

Please consider these proposals.

> English is neither my native language,

I'm third one in your company :)).

> so the followings are only proposals:
>=20
> s/Optionaly/Optionally/

yes

> s/64 character/64 characters/

? The whole phrase is "64 character alphabet". I'm not
at all sure that pl. should be used here.
For example:
"nine inch nails", not "9 inches nails" and so on.

> I would also write "it can start with a "$" character."

'_a_ "$" character' -- yes

> "This means the encrypted password..."

"this mean_s_" -- yes

> and "For example if it starts ..."

"it start_s_" -- yes

> BTW, the same correction could be applied to shadow.5

of course.

--=20
WBR,
xrgtn