W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2014

Re: Spec authoring tools

From: Tobie Langel <tobie.langel@gmail.com>
Date: Fri, 12 Dec 2014 22:55:54 +0100
Message-ID: <CAMK=o4cT-GTJ=D-A_7ckw-k473YX=SrgM9Ch=v=Ux-JQ20Sv8Q@mail.gmail.com>
To: David Carlisle <davidc@nag.co.uk>
Cc: "spec-prod@w3.org Prod" <spec-prod@w3.org>
On Fri, Dec 12, 2014 at 10:22 PM, David Carlisle <davidc@nag.co.uk> wrote:

> On 12/12/2014 21:14, Tobie Langel wrote:
>> Which uses concatenated &nbsp; entities to mimic nested content in
>> the ToC. #sadpanda
> yes I should probably have changed that this time round.
> when we tried originally couldn't get anything that worked well enough
> (but that was probably ie4 and netscape 4, it goes back a while:-)


the editors draft is public of course, if (when you're done) there is a
> spec for the rules the html version should follow, we/I can easily fit
> just as the current html output is designed to fit pubrules.

That would be grand.

The other option would be to simply add support for it in the tools
themselves, once they're published.

Scraping structure from generated html when that's generated from well
> structured XML seems backwards, but I know that's the world we live in

Heh. Is the src code even available online?

> so if there is a spec for the required structure can generate that.

I don't think there'll be a spec per se, but at least a list of
requirements and tests to pass.

> Can't do much about the documents already in TR of course.

Which is why adding support in the toolset might end up being a more
productive route.


Received on Friday, 12 December 2014 21:56:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:20 UTC