[tei-council] New problem with stylesheet processing of the Guidelines?

[Martin Holmes]

I don't see this problem on the Oxford server:

<http://bits.nsms.ox.ac.uk:8080/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/SA.html#SAPT>

so clearly something has changed on one or the other that's put them out 
of sync. My server has version 6.21 of the TEI packages, but the 
Guidelines _should_ be generated using the latest artifact from the 
Stylesheets job.

I'm going to try triggering another Stylesheets build on my server; that 
should generate a rebuild of all the P5 jobs when it's done, and the 
results should confirm whether it's just a glitch on my server. 
Sebastian, could you do the same? I see that your last successful builds 
are showing as six days ago, whereas mine are only a few hours old, so 
it looks like the changes to Stylesheets since then might have a bug 
which has found its way through as far as my Glines build, but hasn't 
shown up in yours yet.

Cheers,
Martin

On 12-12-10 01:31 PM, Martin Holmes wrote:
> Hi all,
>
> I was just looking at the latest Jenkins build of the Guidelines, and I
> see that processing of examples seems to have been buggered up somehow.
> For instance, if you look here:
>
> <http://teijenkins.hcmc.uvic.ca/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/SA.html#SAPT>
>
> you'll see that an example that in the TEI source looks like this:
>
> <egXML xml:lang="und" xmlns="http://www.tei-c.org/ns/Examples"><ptr
> xml:id="sa-p1" target="#sa-p2"/><ptr xml:id="sa-p2"
> target="#sa-p1"/></egXML>
>
> comes out looking like this on the Glines page:
>
> <span class="element"><ptr xml:id="<span
> class="attributevalue">sa-p1</span>" target="<span
> class="attributevalue">#sa-p2</span>"/></span><br/><span
> class="element"><ptr xml:id="<span class="attributevalue">sa-p2</span>"
> target="<span class="attributevalue">#sa-p1</span>"/></span>
>
> It looks as though any instance of an attribute value is being wrapped
> in a <span class="attributevalue">, when I suspect that should actually
> only be happening to things that are tagged as <val>, not which _are_
> vals. A sort of use-mention problem.
>
> Cheers,
> Martin
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)