Date: Sun, 12 Nov 2006 12:22:53 +0100 From: Niclas Zeising <lothrandil@n00b.apagnu.se> To: Marc Fonvieille <blackend@freebsd.org> Cc: Johann Kois <jkois@freebsd.org>, doc-committers@freebsd.org, Giorgos Keramidas <keramida@freebsd.org>, cvs-all@freebsd.org, cvs-doc@freebsd.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/security chapter.sgml Message-ID: <4557040D.2090608@n00b.apagnu.se> In-Reply-To: <20061112111431.GA84563@abigail.blackend.org> References: <200611120013.kAC0D5GM097268@repoman.freebsd.org> <200611121144.28895.jkois@freebsd.org> <4556FE2A.1080501@n00b.apagnu.se> <20061112111431.GA84563@abigail.blackend.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marc Fonvieille wrote: > On Sun, Nov 12, 2006 at 11:57:46AM +0100, Niclas Zeising wrote: >> The difference between ssh and <application>ssh</application> is that >> ssh can be both an application and a protocol, and we have to >> differentiate that. Apart from that, I find staring a sentence with a >> non-capitalized letter looks weird. Maybe we should use the >> all-capitalized version, at least when talking about the protocol. > > SSH is the protocol, and ssh is the application/program (so > <application></application> or <command></command> according to the > situation). We also have to start a sentence with a capitalized letter, > so we used to do the same thing as in the manual page, i.e, writing "The > blahblah utility/tool/program/whatever". > Okay. I'll do an overhaul of the security chapter and see if I can make some sort of progress regarding consistency between, SSH, ssh and so on, using SSH for the protocol, and <application>ssh</application> or <command>ssh</command> depending on the situation. Thanks for the clarification! Regards! //Niclas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4557040D.2090608>