19514 2012-10-12 17:19:03 +0000 Support the FIXUP directive in publish.py 2012-10-15 21:56:31 +0000 1 1 1 Unclassified HTML WG Editor tools unspecified PC All RESOLVED FIXED P2 normal --- 19515 19522 1 eoconnor eoconnor eoconnor erika.doyle robin silviapfeiffer1 travil public-html-bugzilla oldest_to_newest 76121 0 eoconnor 2012-10-12 17:19:03 +0000 The FIXUP directive is used to munge H[1-6] elements to the correct levels in some of the specs produced from the source document (2d, microdata). 76149 1 eoconnor 2012-10-12 18:49:44 +0000 I'll take a shot at this. 76172 2 eoconnor 2012-10-12 21:02:19 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: https://github.com/w3c/html/commit/7165244f9a0af773dec7d7fafb21254b0be784ff Rationale: Fixed. 76289 3 robin 2012-10-15 09:53:26 +0000 (In reply to comment #2) > Change Description: > https://github.com/w3c/html/commit/7165244f9a0af773dec7d7fafb21254b0be784ff This is great, thanks! Applying this and removing the hierarchy-wrangling code we had gets us very close to something that looks good, but not quite there entirely. The one piece that's missing is that by applying just this we get a spec in which HTMLPropertiesCollection is a subsection of Conformance Requirements — unlikely to be correct. I've tried to figure out if there's any instruction in the source to move this section around but I haven't found any. So in the meantime, I'm updating my munging script to shuffle this around — but if there's a hook I've missed please let me know. 76296 4 silviapfeiffer1 2012-10-15 11:41:23 +0000 We can always introduce our own instructions if needed. BTW it would be really valuable if we made a list of the directives that we actually care about. Right now I only know about w3c-html and FIXUP. Are there others? 76297 5 robin 2012-10-15 12:12:12 +0000 (In reply to comment #4) > We can always introduce our own instructions if needed. Sure; but before we do I want to make sure that we're not duplicating anything :) > BTW it would be really valuable if we made a list of the directives that we > actually care about. Right now I only know about w3c-html and FIXUP. Are > there others? There are a bunch. BOILERPLATE and PUB for instance, as well as SET and INSERT. toc is used once. And the START/END aren't just for w3c-html, there are a bunch of others that we care about e.g. microdata. 76339 6 eoconnor 2012-10-15 21:56:31 +0000 Silvia, I essentially made such a list when I cobbled together syntax highlighting for the spec directives in specedit.el. Roughly, there are several categories: 1. Commands our editing infrastructure supports: BOILERPLATE, END, FIXUP, INSERT, INTERFACES?, PUB, SET, START, toc. 2. Commands our tooling doesn't support (yet): ADD-TOPIC, DEFER, REMOVE-TOPIC, TOPIC. Possibly also REFERENCES. 3. It also highlights things that I don't think Ian's tools do anything with but are useful for editors to notice while editing the spec, such as WARNING comments, FORK comments, and the like.