W3C home > Mailing lists > Public > www-style@w3.org > August 2013

Re: [css3-text] indices and animatable

From: John Daggett <jdaggett@mozilla.com>
Date: Wed, 21 Aug 2013 18:26:05 -0700 (PDT)
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>
Message-ID: <1086075044.4466399.1377134765415.JavaMail.zimbra@mozilla.com>

Tab Atkins wrote:

>> I'm aware it's auto-generated via the 'title' attribute.  My point
>> was the resulting index needs cleaning up.  For example, the "tab
>> size" entry really isn't a definition in this case, it justs says
>> "the tab size is given by the ‘tab-size’ property."
> So what you're actually saying is that some things shouldn't be
> definitions, right?  We can't actually clean up the index itself,
> without manually tweaking the generated file.  (Or adding
> functionality to Bikeshed and converting Text to it.)

Yes, that's right, the definitions/titles need to be tidied to make
the index more concise.  Having gone through this with the Fonts spec,
it feels like busywork but I think it's important busywork for the
resulting document.

>> It's also puzzling why the index ends up with a '.' at the end of
>> all section numbers.
> Because that's the text content of the heading's number span, which
> is what Bert's processor uses.  (Bikeshed doesn't do this.)

So the Fonts spec doesn't end up with the '.' appended so I'm not quite
sure what you mean.  This seems to be preprocessor voodoo:

Fonts spec:
<h3 id="font-fetching-requirements">Font fetching requirements</h3>

Output TOC:
==> 4.9 Font fetching requirements

Text spec:
  <h3 id="white-space-rules">
    The White Space Processing Rules</h3>

Output TOC:
==> 4.1. The White Space Processing Rules

Ah, voodoo, where's that chicken when I need it...


John Daggett
Received on Thursday, 22 August 2013 01:26:36 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:31 UTC