- From: Eric Stephan <ericphb@gmail.com>
- Date: Fri, 11 Dec 2015 08:08:08 -0800
- To: Phil Archer <phila@w3.org>
- Cc: Public DWBP WG <public-dwbp-wg@w3.org>
- Message-ID: <CAMFz4jj6ARFiyXXt63XK_BA48LdrMib0v4W1j95FW3j+K6A-3g@mail.gmail.com>
Phil, Great thank you for the pointer to the validation tool and the detailed explanation. Eric S On Fri, Dec 11, 2015 at 8:04 AM, Phil Archer <phila@w3.org> wrote: > Headings, numbering, W3C boilerplate etc, is all written in my ReSpec. So > if you write: > > <section id="foo"> > <h3>This is a level 3 header</h3> > <section id="bar"> > <h1>This is a really important header</h1> > </section> > </section> > > ReSpec will change that so that the hn element always matches the nesting > so it would rewrite that as: > > <section id="foo"> > <h1>This is a level 3 header</h1> > <section id="bar"> > <h2>This is a really important header</h2> > </section> > </section> > > HTML validation can help spot these things (https://validator.w3.org). > > All the numbering, the ToC, the heading levels is all controlled by RePSec > - that, I hope, will help you spend less time fighting! > > Phil > > > > > > On 11/12/2015 15:12, Eric Stephan wrote: > >> Phil, >> >> I have to admit I spent a chunk of time yesterday debunking formatting >> mysteries with properties and it cut into my time adding properties. >> Could >> you look at our document and help me understand why a heading for a >> property is sometimes shown in a large blue letters and other times in >> smaller black? I noticed that our earlier published DUV draft in June >> exhibited the same problems. >> >> Any insights would be greatly appreciated. >> >> Thanks, >> >> Eric S >> >> > -- > > > Phil Archer > W3C Data Activity Lead > http://www.w3.org/2013/data/ > > http://philarcher.org > +44 (0)7887 767755 > @philarcher1 >
Received on Friday, 11 December 2015 16:08:37 UTC