[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#428195: krb5: [debconf_rewrite] Debconf templates review



Summary at the end of this mail that addresses a few remaining issues.

> > (Was the conclusion to use single quotes?  I should probably join
> > debian-l10n-english in my copious free time.)
> 
> There was no conclusion. If someone wanted to make a statement that only
> one should be used and pick one then we could follow it, but maybe we
> should stick with a more organic approach, where we just use whatever
> comes out at the end of the maintainer->reviewers->maintainer interaction.

I agree with this. My feeling up to now is that there are little more
arguments for single quotes than double ones, but the difference is
small enough for not carving such rule in stone.

So, again, I have used single ones here, but if Russ feels
uncomfortable about them, it's OK to revert back to double ones.

> You would be very welcome to join in with the list. Now we have got
> going it seems to be clear that English as a first language is far from
> necessary. Christian does large parts of the rewrites himself, and
> Justin and MJ do a good job of picking up on the language issues.

Very politically correct way to say "pick on Christian's awful usage
of the English language"..:-)


> > > Type: note
> > Oh, and while we're reviewing this -- is this note debconf note abuse?  I
> > didn't remove it the last time I changed the templates, but I wasn't
> > sure.
> 
> Well, Christian is the one to ask, but I believe it might be.

Yes, it is debconf abuse in my opinion. I tend to avoid enforcing the
removal of such notes during the rewrite on packages with a high
popularity (which ar eusually well maintained).

But, if Russ asks, that means that he probably feels like this could
be debconf abuse..:-)

> >     krb524d is a daemon that converts Kerberos V5 tickets into Kerberos V4
> >     tickets for the krb524init program and other programs that obtain
> >     Kerberos V4 tickets for compatibility with old applications.
> > 
> > I don't want to give the impression that krb524d is only used if you're
> > running krb524init, since the latter is not one of the more common ways of
> > getting Kerberos V4 tickets.  Most users actually use krb524d because of
> > old versions of aklog, although the version in Debian hasn't required this
> > for quite some time.  The Red Hat Kerberos PAM module is another likely
> > use.
> > 
> 
> Your new wording is fine. However can I suggest
> 
>    krb524d is a daemon that converts Kerberos V5 tickets into Kerberos V4
>    tickets for programs, such as krb524init, that obtain Kerberos V4 tickets
>    for compatibility with old applications.

I adopted that one, with a minor change:

 The krb524d daemon converts Kerberos V5 tickets into Kerberos V4
 tickets for programs, such as krb524init, that obtain Kerberos V4 tickets
 for compatibility with old applications.

which avoid the issue of having a program name at the beginning of a
sentence.

For such cases where we can't avoid program names to begin a sentence,
I suggest quoting them, which is a way to circumvent the "sentence has
no initial capital" impression.

> That seems like a good convention to me, and one that I use. However it
> does push technical writing conventions up against those of more
> traditional writing. Much like the "V5" vs. "v5" issue, which I did not
> speak up on before, but I would like to put a vote in for the latter if
> it is not too late.


It's never too late.

We might need someone to record such conventions on the wiki
page. Speaking for myself, I can't do it as I mostly work offline (and
it would anyway be good to have someone else handling such important
task.

Summary: 

-need Russ' final word on quotes. We seem to agree to use whatever he
feels appropriate even if I have a small preference for single ones

-need aproval for the final wording of the 'krb524d' daemon

-decision about removal of the debconf note (I can include removing it
from the maintainers scripts in the patch).

As soon as these three have been settled on, i'll send a corrected patch.

Attachment: signature.asc
Description: Digital signature


Reply to: