W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2009

Re: Editing specifications with ReSpec.js

From: Max Froumentin <maxfro@opera.com>
Date: Thu, 6 Aug 2009 12:05:03 +0200
Cc: public-device-apis@w3.org, Marcos Caceres <marcosc@opera.com>
Message-Id: <B0CF49D9-72D9-44A8-853F-22724E7F0862@opera.com>
To: Robin Berjon <robin@robineko.com>
Hi Robin,

in respec.js, line 149, you probably want:

cfg.publishDate = new Date(val.substr(0, 4), val.substr(5, 2) - 1,  
val.substr(8, 2));

(because months start at 0)

Max.
[unless people insist that I don't, I'll report other bugs offline]

On 6. aug.. 2009, at 01.49, Robin Berjon wrote:

> Hi all,
>
> one of the annoying decisions one has to make when editing a  
> specification is which tool to use to generate the final, PubRules  
> compliant HTML.
>
> I don't intend to impose a solution on this — it is up to editors to  
> decide collectively — but I would like to suggest my favourite  
> option: ReSpec.js.
>
> Its chief advantage is that it does not require running any external  
> tool, one simply edits an HTML document according to some  
> conventions, reloads it in the browser, and voilà. It also has built- 
> in support for WebIDL, which'll come in handy for us. Unless you hit  
> a bug it should provide you with PubRules compliant HTML very easily  
> (the checker complains about a couple small things, but I would  
> think that they're wrong).
>
> I won't bend your ear longer than necessary here, you can read more  
> about it at:
>
>  http://dev.w3.org/2009/dap/ReSpec.js/documentation.html
>
> and in general poke around http://dev.w3.org/2009/dap/ReSpec.js/ to  
> see what it's made of.
>
> Enjoy!
>
> --
> Robin Berjon
>  robineko — setting new standards
>  http://robineko.com/
>
>
>
Received on Thursday, 6 August 2009 10:05:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:13:59 GMT