Re: editorial nit wrt publishing working draft

thanks for the info and your efforts on this Angelo.

On 8/14/17, 3:46 PM, "Angelo Liao" <huliao@microsoft.com> wrote:
[...]
> Specific to why the title isn't matching the editor's draft, the 
> reason is I manually deleted the <br> elements in the title. This is
> because the PubRules (spec compliance checker) demands the title to
> match: https://www.w3.org/pubrules/doc/rules/?profile=WD#title. The 
> new version of bikeshed would automatically add <br> element to the 
> title string to make things fit. But doing so would not make the <h1>
> element match and therefore make PubRules unhappy.
Sigh.

 > It's really a bug to be fixed in either bikeshed or Pubrules.

did you submit an issue on BS ?

If not, lets reopen the issue I originally submitted on this:

   https://github.com/tabatkins/bikeshed/issues/1065


 > But waiting for the bug to be fixed would take forever.

maybe not forever, but not quickly enough to get WD-06 out ;-)


> I actually read bikeshed source code and sort of found a way to fix
> it?
very cool.


 > But my brain was tired to test the fix.

propose the fix in a comment on bikeshed/issues/1065 ?


THANKS again,

=JeffH

-----Original Message-----
From: =JeffH [mailto:Jeff.Hodges@KingsMountain.com]
Sent: Monday, August 14, 2017 3:33 PM
To: W3C Web Authn WG <public-webauthn@w3.org>
Subject: editorial nit wrt publishing working draft

thanks again, Angelo, for "turning the crank" to get WD-06 published.

one nit I've noticed is that the formatting of the spec title in WD-06 
does not match how it is working in the editor's draft, nor when using 
https://api.csswg.org/bikeshed/.

I am suspecting that this is due to a different (likely older?) version 
of bikeshed (BS) was used to produce the WD-06 spec than the latter two 
examples. If so, then when publishing working drafts we ought to ensure 
we're using the latest BS version. For locally-installed BS this is done 
as described here 
<https://tabatkins.github.io/bikeshed/#install-common>, which is (at 
this time):

###
To update bikeshed to its latest version at any time, just enter 
Bikeshed’s folder and run:

$ git pull --rebase
$ bikeshed update

This’ll pull the latest version of Bikeshed, and ensure that you’re 
looking at the latest version of the data files, rather than whatever 
stale version is currently sitting in the repo.
###

HTH,

=JeffH

Received on Tuesday, 15 August 2017 15:36:10 UTC