[Bug 19541] New: Specification split marks are out of kilter

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19541

          Priority: P2
            Bug ID: 19541
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org
          Assignee: robin@w3.org
           Summary: Specification split marks are out of kilter
        QA Contact: public-html-bugzilla@w3.org
          Severity: blocker
    Classification: Unclassified
                OS: All
          Reporter: robin@w3.org
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: HTML5 spec
           Product: HTML WG

I've written a tool to check that the START and END marks in the spec source
are correct. You can find it as scripts/check-split-markers.js.

Currently it reports:

Consecutive END for dev-html at 118071 line 2730
Consecutive START for dev-html at 147695 line 3418
Consecutive END for w3c-html at 2774443 line 65146
Consecutive END for w3c-html at 3070938 line 72661
Consecutive END for w3c-html at 3109311 line 73695
Consecutive END for w3c-html at 3115561 line 73854
Consecutive END for dev-html at 3923610 line 94425
Consecutive START for dev-html at 4001247 line 96370
Consecutive END for dev-html at 4006880 line 96530
Consecutive START for dev-html at 4090450 line 98625
Consecutive END for dev-html at 4132792 line 99799
Consecutive START for dev-html at 4164965 line 100545
Consecutive END for w3c-html at 4894314 line 118216

For each line, the first number given is the character offset; the line number
might be easier to use. When it reports a duplicate, it reports the second (or
more) consecutive instance (so if you grep upwards for the same key you'll find
the initial instance).

Each of those we need to fix.

Note that the first dupe END for w3c-html corresponds to the section which is
currently gobbling up all the subsequent spec sections in the generated draft.
In others words, that's what's killing the splitter.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.