W3C home > Mailing lists > Public > www-archive@w3.org > July 2009

Re: PROPOSAL: Procedure to Promote Progress With Accessibility Issues in HTML5

From: Cameron McCormack <cam@mcc.id.au>
Date: Wed, 22 Jul 2009 18:03:48 +1000
To: Sam Ruby <rubys@intertwingly.net>, Steven Faulkner <faulkner.steve@gmail.com>, Shelley Powers <shelleyp@burningbird.net>, www-archive@w3.org, ian@hixie.ch
Message-ID: <20090722080348.GA2190@arc.mcc.id.au>
Cameron McCormack:
> If, hypothetically, I were interested in producing one of these branched
> specs, I would want to be able to do something like:

Doing is better than complaining, I guess.  Although I’m dubious that the
duelling specs approach is the right one, I’ve checked in a template
directory to CVS (http://dev.w3.org/html5/spec-template/).  Perhaps it
will be useful to someone.

Let’s say I want to work on a branched spec.  I would need to have a
Unix-y environment (so that means Cygwin on Windows) that can execute
these commands, at least: make, perl, python, svn, grep, sed, head,
patch, anolis.  I would download and install Anolis from:


Then, I check out the HTML WG repository somewhere:

  $ cvs -d :ext:username@dev.w3.org/sources/public co html5

add a directory for my spec:

  $ cd html5
  $ mkdir spec-mccormack
  $ cp spec-template/{*,.cvsignore} spec-mccormack
      (ignore the error about not being able to copy the CVS directory)

initialise it with the current spec source:

  $ cd spec-mccormack
  $ make init

variables in Makefile.  Also, I’d change THIS_SPEC in Makefile to be set
to the directory I created (in this case, “spec-mccormack”).

Then, to build the spec and check it in:

  $ make
  $ cvs add Makefile header source util.pl Overview.html
  $ cvs commit -m "Initial check-in."

Now I can edit the “source” file and run “make” to regenerate
Overview.html.  To merge in recent changes from Ian’s spec:

  $ make merge

That could fail if the merged changes are to the same parts of the
document that I’ve been editing.  In this case, rejected patch files
named *.rej will be dumped out into the directory.  I’d then merge them
manually, and then indicate that I’ve resolved the conflicts:

  $ make resolved

The ‘header’ file is just a copy of the current document header
(everything before the ToC) from the W3C copy of the spec.  The build
scripts here will modify various parts of this in the generated
Overview.html, which is a “willful violation” of the comments Ian has
included in the spec source. :-)  I’m presuming this is OK since this
isn’t editing Ian’s document.  Ian, let me know if you’d like me to do
less/different munging.

Also note that if you want the images in the spec
(http://dev.w3.org/html5/spec/images/) you’ll need to copy them over

Cameron McCormack ≝ http://mcc.id.au/
Received on Wednesday, 22 July 2009 08:04:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:43:34 UTC