Re: [whatwg] New HTML5 spec GIT collaboration repository
Manu Sporny wrote: Cameron McCormack wrote: Manu Sporny: 3. Running the Anolis post-processor on the newly modified spec. Geoffrey Sneddon: Is there any reason you use --allow-duplicate-dfns? I think it’s because the source file includes the source for multiple specs (HTML 5, Web Sockets, etc.) which, when taken all together, have duplicate definition. Manu’s Makefile will need to split out the HTML 5 specific parts (between the !--START html5-- and !--END html5-- markers). The ‘source-html5 : source’ rule in http://dev.w3.org/html5/spec-template/Makefile will handle that. What a great answer, Cameron! I wish I had thought of that :) Ah, that's true. I was assuming he was working on the split-up spec. Yes, that will become an issue in time and was going to have a chat with Geoffrey about how to modify Anolis to handle that as well as handling what happens when there is no definitions when building the cross-references (perhaps having a formatter warnings section in the file?). Handle that in what way? The correct way, as far as I can see, is to do what Ian does, which is to call Anolis on the already-split up spec. What do you mean about warnings? Just if there's an instance of a term which isn't defined? That can't be done, because it would mean that every abbr, code, i, span and var element would have to be an instance (whereas they can perfectly fine exist without being one). It's probably worth throwing an error/warning when data-anolis-xref is set and it is unknown, though. (But that will probably change to data-xref.) I also spoke too soon, Geoffrey, --allow-duplicate-dfns is needed because of this error when compiling Ian's spec: The term dom-sharedworkerglobalscope-applicationcache is defined more than once I'm probably doing something wrong... haven't had a chance to look at Cameron's Makefile pointer yet, so --allow-duplicate-dfns is in there for now. I expect you are doing something wrong, because that doesn't exist in Ian's copy. :) With regards to tracking Anolis, your free to pull it in if you want, but you probably don't want to track it too closely (currently there haven't been any major changes from 1.0, though they are coming soon, so it may get a miss less stable). I tend to ping James (Graham) provided it's stable, so he can update pimpmyspec.net, and I can try and remember to ping you too. -- Geoffrey Sneddon — Opera Software http://gsnedders.com/ http://www.opera.com/
Re: [whatwg] New HTML5 spec GIT collaboration repository
Manu Sporny wrote: 3. Running the Anolis post-processor on the newly modified spec. Is there any reason you use --allow-duplicate-dfns? Likewise, you probably don't want --w3c-compat (the name is slightly misleading, it provides compatibility with the CSS WG's CSS3 Module Postprocessor, not with any W3C pubrules). On the whole I'd recommend running it with: --w3c-compat-xref-a-placement --parser=lxml.html --output-encoding=us-ascii The latter two options require Anolis 1.1, which is just as stable as 1.0. I believe those options are identical to how Hixie runs it through PMS. -- Geoffrey Sneddon — Opera Software http://gsnedders.com/ http://www.opera.com/
Re: [whatwg] New HTML5 spec GIT collaboration repository
Manu Sporny: 3. Running the Anolis post-processor on the newly modified spec. Geoffrey Sneddon: Is there any reason you use --allow-duplicate-dfns? I think it’s because the source file includes the source for multiple specs (HTML 5, Web Sockets, etc.) which, when taken all together, have duplicate definition. Manu’s Makefile will need to split out the HTML 5 specific parts (between the !--START html5-- and !--END html5-- markers). The ‘source-html5 : source’ rule in http://dev.w3.org/html5/spec-template/Makefile will handle that. -- Cameron McCormack ≝ http://mcc.id.au/
Re: [whatwg] New HTML5 spec GIT collaboration repository
Geoffrey Sneddon wrote: Manu Sporny wrote: 3. Running the Anolis post-processor on the newly modified spec. Is there any reason you use --allow-duplicate-dfns? Legacy cruft. There was a time that I had duplicate dfns while attempting to figure something else out. The latest commit to the master branch has it removed - thanks :) Likewise, you probably don't want --w3c-compat (the name is slightly misleading, it provides compatibility with the CSS WG's CSS3 Module Postprocessor, not with any W3C pubrules). Ah, I thought it was required to generate some W3C-specific HTML. Removed as well, thanks for the pointer. On the whole I'd recommend running it with: --w3c-compat-xref-a-placement --parser=lxml.html --output-encoding=us-ascii Done, those are the default flags that the HTML5 git repo uses now to build all of the specifications. The latter two options require Anolis 1.1, which is just as stable as 1.0. I believe those options are identical to how Hixie runs it through PMS. Seeing as how building Python eggs and using Mercurial is scary for some people, would it be okay if I included the Anolis app into the HTML5 git repository? Your license allows this, but I thought I'd ask first in case you wanted to collaborate on it in a particular way. I can either track updates from the mercurial anolis source repo, or give you commit access to the HTML5 git repo so that you can continue to modify Anolis there. Let me know which you would prefer... -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) President/CEO - Digital Bazaar, Inc. blog: Bitmunk 3.1 Released - Browser-based P2P Commerce http://blog.digitalbazaar.com/2009/06/29/browser-based-p2p-commerce/
Re: [whatwg] New HTML5 spec GIT collaboration repository
Cameron McCormack wrote: Manu Sporny: 3. Running the Anolis post-processor on the newly modified spec. Geoffrey Sneddon: Is there any reason you use --allow-duplicate-dfns? I think it’s because the source file includes the source for multiple specs (HTML 5, Web Sockets, etc.) which, when taken all together, have duplicate definition. Manu’s Makefile will need to split out the HTML 5 specific parts (between the !--START html5-- and !--END html5-- markers). The ‘source-html5 : source’ rule in http://dev.w3.org/html5/spec-template/Makefile will handle that. What a great answer, Cameron! I wish I had thought of that :) Yes, that will become an issue in time and was going to have a chat with Geoffrey about how to modify Anolis to handle that as well as handling what happens when there is no definitions when building the cross-references (perhaps having a formatter warnings section in the file?). I also spoke too soon, Geoffrey, --allow-duplicate-dfns is needed because of this error when compiling Ian's spec: The term dom-sharedworkerglobalscope-applicationcache is defined more than once I'm probably doing something wrong... haven't had a chance to look at Cameron's Makefile pointer yet, so --allow-duplicate-dfns is in there for now. Here's the latest: http://github.com/html5/spec/commit/16514d4ec9175fdf6a408789628817d81c44e3a9 -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) President/CEO - Digital Bazaar, Inc. blog: Bitmunk 3.1 Released - Browser-based P2P Commerce http://blog.digitalbazaar.com/2009/06/29/browser-based-p2p-commerce/
