W3C home > Mailing lists > Public > spec-prod@w3.org > July to September 2012

Re: biblio.js update best practice?

From: Robin Berjon <robin@w3.org>
Date: Tue, 25 Sep 2012 12:00:27 +0200
Message-ID: <506180BB.1090709@w3.org>
To: Frederick.Hirsch@nokia.com
CC: spec-prod@w3.org
On 24/09/2012 19:22 , Frederick.Hirsch@nokia.com wrote:
> What is the best way to test a change to biblio.js before pulling it
> into the main build?

In general I only do the most cursory test of biblio.js: I check the 
syntax. For that, I just do node bibrefs/biblio.js. If it doesn't blow 
up then the syntax is fine.

> Is there a way to create a local build that you can link to from your
> document to test out any bibliography changes or additions?

Yup  see other mail. With that, any change will appear immediately upon 
reload.

> I could craft a test document/Javascript to pull in biblio.js and
> generate a full bibliography for testing - has anyone already done
> this?

Apparently, I did that in 2009 :) 
http://dev.w3.org/2009/dap/ReSpec.js/biblio.html That page would need 
updating to use the new stuff.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Tuesday, 25 September 2012 10:01:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 25 September 2012 10:01:46 GMT