Re: ReSpec updated

On 10/03/2016 2:17 PM, Shane McCarron wrote:
> Nor should you.  I will dig it out.  I was just looking for a 
> reference to something that exhibited the behavior.
I was testing a local document prior to publishing live, but using the 
absolute reference to Respec. So hard to pass a URI.

But as I mentioned in a part of the thread that crossed with this part, 
Shane's suggestion at the tail end of a telecon to force-refresh fixed 
it. I just hadn't expected that that should be necessary. So no need to 
spend time investigating.

But nonetheless felt need to push back on "just submit a pull request" 
because that is a highly unrealistic expectation for most users of 
Respec. I have a couple times tried to learn the Respec code in order to 
submit pull requests but quickly got lost; there is no hope of taking 
time to do that when I'm trying to get a publication out under pressure 
of committed dates.

Michael
>
> On Thu, Mar 10, 2016 at 1:13 PM, Michael Cooper <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     On 10/03/2016 2:06 PM, Tobie Langel wrote:
>
>         On Thu, 10 Mar 2016, at 19:53, Michael Cooper wrote:
>
>             There are still changes impacting publication; this
>             version is adding
>             "It is expected to become a W3C Note." for a Note-track
>             document that
>             pubrules rejects; the previous version did not add that,
>             and is accepted
>             by pubrules. This is the one giving me pain right now but
>             there may be
>             others. The output of the new respec needs checking
>             against pubrules
>             before it can be considered fixed. Michael
>
>         I'm sure a pull request fixing this would be most welcome. :)
>
>     When I'm in publication hell, exacerbated by a recently broken
>     tool, trying to learn the code in order to submit a pull request
>     is just not possible. I just don't have time to deal with that.
>     Michael
>
>
>         --tobie
>
>
>
>
>
>
> -- 
> Shane McCarron
> Projects Manager, Spec-Ops