NOTE: Most CSSWG specs are now edited with Bikeshed, a more advanced preprocessor with virtually all of the features of the old preprocessor.
For the CSSWG and other groups, you'll likely be editing a file called:
that you'll need to turn into (and update in place when it's already there)
BEFORE committing your work.
Overview.src.htmlfile on your local machine that you want to post-process (you should do this when you're ready to check it in).
Overview.html(without the quotes), and save it right next your
Overview.src.html- you'll likely be replacing an older version, that's ok, go ahead and confirm (command-R in the replace dialog).
If you're on a system with curl on it, just save the following line to a file somewhere in your executable path:
curl -u USERNAME:PASSWORD -F file=@Overview.src.html -F group=CSS -F output=html -F method=file https://www.w3.org/Style/Group/process.cgi -o Overview.html
(Replace the USERNAME:PASSWORD with your W3C username and password, the same that you would enter when visiting the web form linked above.)
Mark the file as executable, then just run it from within the folder of the spec you're working on. It will automatically submit
Overview.src.html to the post-processor and save the results to
If you use the Keyring extension for Mercurial you can use this script instead, to avoid storing the password in the script:
W3C_USER='your username' curl -u $W3C_USER:$(python -c "import keyring;print(keyring.get_password('Mercurial', '$W3C_USER@@https://dvcs.w3.org/hg/'))") -F file=@Overview.src.html -F group=CSS -F output=html -F method=file http://cgi.w3.org/member-bin/process.cgi -o Overview.html
(Before using this script you need to push at least once so that the password is in the keyring.)
For the WebApps working group (e.g. for the Fullscreen specification), you have to install more tools:
cd /mirror/hg/dvcs.w3.org/fullscreen # or wherever you have it locally make