Re: [tei-council] and now...

I haven't gone through and fixed the tests yet, so no surprise it's broken :-) Sent from my phone.

On Dec 14, 2015, at 14:22, Peter Stadler wrote:

The bunny seams to sit in line 475 of verbatim.xsl. (Hugh commented this line out; if I put it in again, the first test works fine but it chokes on "test15.odd.html“ were obvious PureODD stuff is missing.

Cheers Peter

...

Am 14.12.2015 um 19:39 schrieb Martin Holmes :

There's a procession of tests which are failing because an edit on the pureodd branch introduced a blank line in the output which is not reflected in the expected-results. I've fixed a few of them, in the hope that this was an isolated case, but I'm now thinking that this is a general problem that should be fixed in the place that introduced the difference. I don't have time to track that down right now, but I think Hugh made those changes; Hugh, if you can figure out what's adding that blank line, you could revert the tree to b7ee9fa3d851dbd2ce3d560a1718b4aec40588f6, prior to my changes this morning, and fix the source rather than the symptoms.

Cheers, Martin

...

On 15-12-14 09:58 AM, Martin Holmes wrote: The Stylesheets pureodd branch failed to build on Jenkins, which is why the P5 branch can't build. The Stylesheets build seems to be failing on:

diff test.html expected-results/test.html

The difference between them appears to be a single extra blank line at line 797 in test.html. I shall endeavour to fix that, and we'll see how we get on.

Cheers, Martin

...

On 15-12-14 09:22 AM, Lou Burnard wrote: If we're reaching consensus on the meta-question of how issues should be labelled, could we now collectively consider at least some of the urgent outstanding issues themselves? In particular, I am still waiting for an explicit green light from at least one other council member who has successfully built using the lb42-pure-odd-2 branch? Martin set up a Jenkins job to do this, but it seems to have fallen over at the penultimate hurdle, and I don;'t know enough about Jenkins to see why. If we get that, then I could maybe issue a pull request (whatever that is) and get this stuff merged in...

If we're looking for jobs for new council members to cut their teeth on, I'd be delighted to propose trying to build this branch! Much more fun than fixing a tedious bit of prose.

I'd also appreciate some feedback on my ticket proposing a new anyXML element...

L -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived