From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 16:47:38 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02FD1106564A; Fri, 12 Dec 2008 16:47:38 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (unknown [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id B9E4B8FC08; Fri, 12 Dec 2008 16:47:37 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p2191-ipbf1403funabasi.chiba.ocn.ne.jp [118.7.161.191]) (authenticated bits=128) by mail.allbsd.org (8.14.2/8.14.2) with ESMTP id mBCGlPAE010816; Sat, 13 Dec 2008 01:47:36 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id mBCGlFJa090153; Sat, 13 Dec 2008 01:47:19 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sat, 13 Dec 2008 01:43:25 +0900 (JST) Message-Id: <20081213.014325.183748569.hrs@allbsd.org> To: sonic2000gr@gmail.com From: Hiroki Sato In-Reply-To: <4941F694.3040600@gmail.com> References: <49403656.4020303@gmail.com> <8763lq14yo.fsf@kobe.laptop> <4941F694.3040600@gmail.com> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.1 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Sat_Dec_13_01_43_25_2008_690)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.allbsd.org [133.31.130.32]); Sat, 13 Dec 2008 01:47:36 +0900 (JST) Cc: freebsd-doc@FreeBSD.org, keramida@FreeBSD.org Subject: Re: [PATCH] Adding elements to wlan Handbook section X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 16:47:38 -0000 ----Security_Multipart(Sat_Dec_13_01_43_25_2008_690)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Manolis Kiagias wrote in <4941F694.3040600@gmail.com>: so> Giorgos Keramidas wrote: so> > On Wed, 10 Dec 2008 23:36:22 +0200, Manolis Kiagias wrote: so> > so> >> I've seen it in the Handbook, but in very few parts. It is also rendered so> >> very nicely, and is not at all distracting. (A lightweight, dotted so> >> underline). See here for an example: so> >> so> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ftp.html so> >> so> > so> > That looks good. I've started pushing to hg.hellug.gr some commits that so> > add this sort of role="" attribute to the wlan section :-) so> > so> > Manolis, I have a question that is mostly a style issue though. so> > so> > There are some compound acronyms in the wlan section, i.e. "WPA-TLS". so> > Would you prefer a separate for "WPA" and "TLS" like so> > so> > WPA- > role="Transport Layer Security">TLS so> > so> > or a single element like so> > so> > WPA-TLS so> > so> > The first seems more logical, and it would fit nicely with the set of so> > acronym entities (acronyms.ent) I proposed in another email of the so> > thread (eg. we won't have to introduce a new, special entity for so> > &acronym.wlan.wpa-tls; but we can reuse the WPA and TLS entities). I am so> > not sure if it would result in aesthetically pleasing output when the so> > dotted underlines appear in separate words though. so> > so> > so> > so> I agree that the first seems more logical and more effective as the so> entities can be reused. However the difference is really very small, so so> go along with the one you prefer. so> As for the dotted lines, they are so subtle anyway that it won't make so> much of a difference if they appear in separate words. This decision depends on the context, I think. "EAP" and "TLS" are words describing individual elemental technologies, and "EAP-TLS" describes a different one using these technologies, not simple combination of the two. In such a case, we should not reuse the definition in a way that it looks a combination of two acronyms. -- | Hiroki SATO ----Security_Multipart(Sat_Dec_13_01_43_25_2008_690)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAklClK0ACgkQTyzT2CeTzy0WAwCgumGQs2NR0ZQ4D5CSpSc09bMo 4GEAoNQemKJq2meNuZBV0d7bn53BScxM =Pvx1 -----END PGP SIGNATURE----- ----Security_Multipart(Sat_Dec_13_01_43_25_2008_690)----