Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Dec 2008 13:22:57 -0800
From:      "Murray Stokely" <murray@stokely.org>
To:        "Giorgos Keramidas" <keramida@freebsd.org>
Cc:        freebsd-doc@freebsd.org
Subject:   Re: [PATCH] Adding <acronym> elements to wlan Handbook section
Message-ID:  <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com>
In-Reply-To: <878wqnafso.fsf@kobe.laptop>
References:  <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop>

next in thread | previous in thread | raw e-mail | index | archive | help
In that case this looks great to me.  I agree with Manolis that adding
the role="definition" for the first instance of each acronym is
helpful.  I really thought we were already doing this in parts of the
Handbook, but I may be misremembering.

           - Murray

On Wed, Dec 10, 2008 at 1:20 PM, Giorgos Keramidas <keramida@freebsd.org> wrote:
> On Wed, 10 Dec 2008 13:10:31 -0800, "Murray Stokely" <murray@stokely.org> wrote:
>> Is the stylesheet now smart enough to only markup the first occurrence
>> differently?  I seem to recall these could get distracting if all
>> instances of an acronym are replaced (either with hyperlinks to
>> definition, or bold, or however we are currently rendering them).
>
> All the instances of am <acronym> are rendered in HTML as
>
>    <acronym class="ACRONYM">FOO</acronym>
>
> with the current DSSSL code.  We don't color or otherwise reformat
> either 'acronym' or '#acronym' in our current docbook.css stylesheet, so
> they are not distracting if the patch goes in.
>
> We might have to make DSSSL a bit smarter about what to send to the
> output HTML text if we start colorizing acronyms in CSS though.
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a7894eb0812101322o77b12fc9k8208f83d62481ad3>