- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Tue, 15 Jul 2014 08:57:51 +1000
- To: Shane McCarron <shane@aptest.com>
- Cc: Frederick Hirsch <w3c@fjhirsch.com>, spec-prod@w3.org
Received on Monday, 14 July 2014 22:58:18 UTC
I used to use phantomjs to automate the creation before pushing to w3c CVS from GitHub, but that broke. Now I'm doing it manually too. I would prefer that worked again! Best Regards, Silvia. On 15 Jul 2014 02:39, "Shane McCarron" <shane@aptest.com> wrote: > Thanks Frederick. That's how I have done it traditionally too. But it is > hard to automate ;-) > > > On Mon, Jul 14, 2014 at 11:34 AM, Frederick Hirsch <w3c@fjhirsch.com> > wrote: > >> I have always generated a static snapshot to avoid issues with scripting >> for readers and also to ensure a non-changing version that has no >> dependencies on possibly changing code (but this was a while ago). Have >> done this by hand from within ReSpec displayed menu in the document. >> >> Once HTML has been generated have used http://services.w3.org/htmldiff >> but there are benefits from using diff integrated in git to get more >> specific diffs. >> >> regards, Frederick >> >> Frederick Hirsch, Nokia >> Chair DAP >> @fjhirsch >> >> >> >> On Jul 14, 2014, at 11:03 AM, Shane McCarron <shane@aptest.com> wrote: >> >> > Quick survey question: how are people generating static versions of >> ReSpec documents for publication? Does anyone have a nice command-line way >> to get from raw file to static file / diff-marked version, PDF version, etc? >> >> >
Received on Monday, 14 July 2014 22:58:18 UTC