This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19514 - Support the FIXUP directive in publish.py
Summary: Support the FIXUP directive in publish.py
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Editor tools (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 19515 19522
  Show dependency treegraph
 
Reported: 2012-10-12 17:19 UTC by Edward O'Connor
Modified: 2012-10-15 21:56 UTC (History)
5 users (show)

See Also:


Attachments

Description Edward O'Connor 2012-10-12 17:19:03 UTC
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).
Comment 1 Edward O'Connor 2012-10-12 18:49:44 UTC
I'll take a shot at this.
Comment 2 Edward O'Connor 2012-10-12 21:02:19 UTC
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.
Comment 3 Robin Berjon 2012-10-15 09:53:26 UTC
(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.
Comment 4 Silvia Pfeiffer 2012-10-15 11:41:23 UTC
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?
Comment 5 Robin Berjon 2012-10-15 12:12:12 UTC
(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.
Comment 6 Edward O'Connor 2012-10-15 21:56:31 UTC
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.