- Tei-council - lists.tei-c.org

Fwd: Re: evilinhd
by James Cummings 01 Jul '16

01 Jul '16

-------- Forwarded Message -------- Subject: Re: evilinhd Date: Fri, 1 Jul 2016 13:44:46 +0200 From: Elena Gonzalez-Blanco <egonzalezblanco(a)flog.uned.es> To: James.Cummings(a)it.ox.ac.uk <James.Cummings(a)it.ox.ac.uk> CC: TEI Council <tei-council(a)lists.tei-c.org> Thanks James! it is a pleasure to share our new "baby TEI" with the Council. As I said to James, it was launched on Monday and it is a very beta version, but we'll be happy to receive your feedback and improvement suggestions before opening it to the community. And yes, the name is not by chance: EVI (Entorno Virtual de Investigación = VRE Virtual Research Environment) + LINHD (Laboratorio de Innovación en Humanidades Digitales / Digital Humanities Innovation Lab) is the result... and nobody will forget easily :) Best Elena Elena González-Blanco García Dpto. de Literatura Española y Teoría de la Literatura, Despacho 722 Facultad de Filología, UNED Paseo Senda del Rey 7 28040 MADRID tel. 91 3986873 http://linhd.uned.es <http://linhd.uned.es/> http://filindig.hypotheses.org/ www.uned.es/personal/elenagonzalezblanco <http://www.uned.es/personal/elenagonzalezblanco> @elenagbg 2016-07-01 13:39 GMT+02:00 James Cummings <James.Cummings(a)it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk>>: Hi TEI Council, Elena González-Blanco García (CC'd) drew to my attention a beta release of a system they have built at UNED for the creation and publication of TEI documents. It uses a web-based visual editor they've created TEI Scribe (think lots of nested boxes rather than WYSIWYG) allows you to upload documents and DTDs (ick) to validate them against, and then seamlessly uses the eXist-db Instant Publishing Toolbox (that Wolfgang and Magdalena have worked on) as its publication system. I'm sure this will build more on the processing model aspects eventually. I thought some of you might be interested in having a look. http://www.evilinhd.com/ (And yes, my brain parses that as Evil In HD... ;-) ) -James -- Dr James Cummings, Academic IT Services, University of Oxford, TEI Consultations: tei(a)it.ox.ac.uk <mailto:tei@it.ox.ac.uk> -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

evilinhd
by James Cummings 01 Jul '16

01 Jul '16

Hi TEI Council, Elena González-Blanco García (CC'd) drew to my attention a beta release of a system they have built at UNED for the creation and publication of TEI documents. It uses a web-based visual editor they've created TEI Scribe (think lots of nested boxes rather than WYSIWYG) allows you to upload documents and DTDs (ick) to validate them against, and then seamlessly uses the eXist-db Instant Publishing Toolbox (that Wolfgang and Magdalena have worked on) as its publication system. I'm sure this will build more on the processing model aspects eventually. I thought some of you might be interested in having a look. http://www.evilinhd.com/ (And yes, my brain parses that as Evil In HD... ;-) ) -James -- Dr James Cummings, Academic IT Services, University of Oxford, TEI Consultations: tei(a)it.ox.ac.uk

1 0

some progress on fx build
by Syd Bauman 01 Jul '16

01 Jul '16

As y'all know the TEIP5-Test-dev project on Jenkins is broken. I just spent some time looking into this, and have some information, but no answers yet. * The problem is in the "detest" target of P5/Test/Makefile. * The problem seems to be from `$(ANT) -f antruntest.xml -Doutputname=detest -DoddFile=detest.odd validateodd`, which is generating unexpected output. * I added a -d switch to the ANT calls, and deleted the `rm` commands from the detest and clean targets in Test/Makefile and ran the build locally. The output put into detest1.log (which is both STDOUT and STDERR from the above ANT command, and which, after filtering with `grep` and `sed`, is expected to be a bunch of Schematron error messages like 'Error: both the versionDate and xml:lang attributes on "gloss" are required when it is a child of "elementSpec".') is: | [xslt] Using class org.apache.tools.ant.taskdefs.optional.TraXLiaison | [xslt] In file /home/syd/Documents/TEI-dev/P5/Test/detest.odd time: 1457836257000 | [xslt] Out file /dev/null time: 1467305096000 | [xslt] Style file ../p5odds.message.isosch.xsl time: 1467333273000 | [xslt] to /dev/null | [xslt] And there is one very interesting line that gets filtered out: | java.lang.NoSuchFieldException: _isNotSecureProcessing This output is from the validateodd ANT target. Anyone have any useful insight?

1 0

Re: [tei-council] TEI Simple ODD update
by Lou Burnard 29 Jun '16

29 Jun '16

On 29/06/16 17:26, Martin Mueller wrote: > > <desc> shows up in Sebastian’s EEBO texts as a child of <gap> , but nowhere else. There are ways of doing without it. > Ah! OK, tx. This is presumably because EEBO texts can contain relatively extensive descriptions of why something has not been transcribed. I will add it accordingly.

1 0

Re: [tei-council] TEI Simple ODD update
by Lou Burnard 29 Jun '16

29 Jun '16

Hi Martin, and thanks for quick reply. On 29/06/16 14:56, Martin Mueller wrote: > Lou, > > > I cc Hugh Cayless, because I’m not sure that I can write to the Council list > > > The only use case envisaged in Simple for facsimile was a basic “digital combo” that lets you go from text to image. Do we need more than ‘facsimile’ for that? It seems to me that ‘surface’, ‘surfaceGrp’ and ‘zone’ take us into concerns with the “materiality” of the text that I explicitly marked as out of scope for the Simple project. You need surface and surfaceGrp to cope with the not uncommon situation where your page images don't correspond tidily with the structure of your text e.g. you have images of a double page spread. Adding zone is very little extra overhead for quite a lot of benefit (e.g. aligning image and transcription) > > We purposely included “rhyme” the schema in September 2014, and I remember Martin Holmes writing at the time that this was a useful element for tagging a very primitive but important component of poetry. OK, no problem to put it back, though I cannot say that I agree with Martin H. on this one. > > “desc” is used all the time in Sebastian’s P5 version of the EEBO texts, and it was a basic design decision that Simple needed to do EEBO, whatever else it did. Agreed, but where is <desc> used in the EEBO texts? (as opposed to EEBO headers)? > > Is ‘c’ in the element list? It seems to be commented out, but it should be in. I have put it back now. > What are the current header elements that you’d like to throw out rather than restrict just to the header? Is particDesc one of them? The list of elements rejected from the header module is in my mail below. particDesc is not included partly because its provided by the corpus module, but mainly because it is pointless having it unless you also provide <listPerson>, and <person>, and all (or at least some of) the many many possible children of <person> . Which I think is overkill for a simple schema. > There is a larger issue here about the place of TEI Simple in the TEI ecosystem. To my mind, the larger issue is the lack of clarity as to what the design goals of Simple actually are. > I recently went through the Council minutes and came across the first discussion of TEI Simple. Sebastian at the time said “If all this goes forward, we would eventually end up with something like TEI Tite or Lite, and Council would inherit it; we might then decide to retire Lite and use this instead. One of the work packages is to extend ODD anyway, so there would be a lot of input by Council.” As indeed there was. And that is why the Procmod is now in the TEI. > The main point of that project was always the Processing Model. If we now end up with something called ‘Simple’ and something called ‘Lite’ we just add confusion and force newbies to ponder when they should use Lite and when Simple. Ditto for Best Practices in Libraries Level 4. I disagree. The whole point of the TEI is that it offers multiple entry points. And long may it continue to do so. > What we need is a single point of entry into the TEI ecosystem. It is in many ways misleading to call it either ‘lite’ or ‘simple’. It would be better to choose a name that articulates the goal admirably stated in the introduction to Lite: “meet 90 percent of the needs of 90 percent of the users.” And that single point of entry should be readily accessible to a person who knows next to nothing about XML. > You cannot use Simple or any other TEI schema without some knowledge of XML. Sorry, but that's life. You need to know how to operate a keyboard too. > MM > > > > > > > On 6/29/16, 5:25 AM, "Lou Burnard" <lou.burnard(a)retired.ox.ac.uk> wrote: > > Here's what I have so far done to the tei_simple.odd document so far, and > why. Sadly this is not the end of the story, but I will send another > message about that anon. > > 1. The original draft contained large amounts of promotional material > about the Simple project, and some tutorial material about XML and > about the processing model. I removed all of it, on the grounds that > it was either inappropriate or unnecessary in a tutorial introduction > to the Simple schema. > > > 2. The schema included a large number of elements which seemed quite > inappropriate for something called "simple" -- notably elements > relating to detailed genetic transcription, or manuscript > description. I removed these: if you want to make a detailed > transcript of a manuscript, you need more than TEI Simple, but your > task isn't simple either. > > 3. The schema originally included "all" of the TEI Header (in practice > this seems to have meant "all of the TEI Header when only some modules > are included", as opposed to "the TEI Header as defined by TEI > All"). I can see no good reason for this, so I have defined a subset > of the Header, excluding some dozen or so highly specialised elements > (specifically: appInfo application cRefPattern calendar calendarDesc > correction correspAction correspContext correspDesc geoDecl > hyphenation interpretation normalization punctuation quotation > refState refsDecl samplingDecl scriptNote segmentation styleDefDecl > stdVals typeNote). Simple should make it easier to create a new > header; if you want to import an arbitrary header created by someone > else, use TEI All. > > 4. As a consequence of (3) above, the schema originally specified by > schematron rule that several elements were permitted only in the > header and not in the text. I have simplified these rules > considerably; what would be more useful in my view would be to add > rules reducing the number of elements permitted in the Header. > > 6. I removed a few elements which did not seem to me to be either > necessary or simple (addSpan, desc, handShift, rhyme, spGrp); I added > a few elements which were needed to cope with the presence of bibl in > the body of a document (biblScope, editor, email, relatedItem); I > added facsimile, surface, surfaceGrp, and zone since the text seemed > to imply that there was a Simple use case for digital facsimiles. > > 5. I systematically checked that every element defined by the schema > was at least referenced by a specDesc in the body of the doc, and > where possible accompanied by some minimal explanation or > exemplification. This turned out to be a lot of work, since the > original document was extremely detailed in some cases and entirely > silent in others. I also took the opportunity to bring some of the > prose up to date and to simplify some of its language, though > undoubtedly there is more to be done there. > > You can see the current state of the draft in the dev repo, at > P5/Exemplars/tei_simple.odd > > >

1 0

TEI Simple ODD update
by Lou Burnard 29 Jun '16

29 Jun '16

Here's what I have so far done to the tei_simple.odd document so far, and why. Sadly this is not the end of the story, but I will send another message about that anon. 1. The original draft contained large amounts of promotional material about the Simple project, and some tutorial material about XML and about the processing model. I removed all of it, on the grounds that it was either inappropriate or unnecessary in a tutorial introduction to the Simple schema. 2. The schema included a large number of elements which seemed quite inappropriate for something called "simple" -- notably elements relating to detailed genetic transcription, or manuscript description. I removed these: if you want to make a detailed transcript of a manuscript, you need more than TEI Simple, but your task isn't simple either. 3. The schema originally included "all" of the TEI Header (in practice this seems to have meant "all of the TEI Header when only some modules are included", as opposed to "the TEI Header as defined by TEI All"). I can see no good reason for this, so I have defined a subset of the Header, excluding some dozen or so highly specialised elements (specifically: appInfo application cRefPattern calendar calendarDesc correction correspAction correspContext correspDesc geoDecl hyphenation interpretation normalization punctuation quotation refState refsDecl samplingDecl scriptNote segmentation styleDefDecl stdVals typeNote). Simple should make it easier to create a new header; if you want to import an arbitrary header created by someone else, use TEI All. 4. As a consequence of (3) above, the schema originally specified by schematron rule that several elements were permitted only in the header and not in the text. I have simplified these rules considerably; what would be more useful in my view would be to add rules reducing the number of elements permitted in the Header. 6. I removed a few elements which did not seem to me to be either necessary or simple (addSpan, desc, handShift, rhyme, spGrp); I added a few elements which were needed to cope with the presence of bibl in the body of a document (biblScope, editor, email, relatedItem); I added facsimile, surface, surfaceGrp, and zone since the text seemed to imply that there was a Simple use case for digital facsimiles. 5. I systematically checked that every element defined by the schema was at least referenced by a specDesc in the body of the doc, and where possible accompanied by some minimal explanation or exemplification. This turned out to be a lot of work, since the original document was extremely detailed in some cases and entirely silent in others. I also took the opportunity to bring some of the prose up to date and to simplify some of its language, though undoubtedly there is more to be done there. You can see the current state of the draft in the dev repo, at P5/Exemplars/tei_simple.odd

1 0

Build failed in Jenkins: Stylesheets-dev #2017
by Victoria TEI Jenkins 29 Jun '16

29 Jun '16

See <http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/2017/changes> Changes: [s.bauman] Fix problem I described in mail I did *not* send to Council on [s.bauman] Addresing (new) ticket #159, this change is an attempt to fix extraction ------------------------------------------ Started by an SCM change Building in workspace <http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/TEIC/Stylesheets.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/Stylesheets.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/TEIC/Stylesheets.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/dev^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10 Checking out Revision 16b9414294230518abec6255a751d1105b56337d (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f 16b9414294230518abec6255a751d1105b56337d > git rev-list 0d226da4e850bb84120856b73cebb1fe11a31bec # timeout=10 > git tag -a -f -m Jenkins Build #2017 jenkins-Stylesheets-dev-2017 # timeout=10 [workspace] $ /bin/bash -xe /tmp/hudson7149243504749472648.sh + make clean test deb dist (for i in css/*; do rm -f `basename $i`;done) echo "" > test~ rm -f profile1.html profile2.html profile.xml find . -name "*~" | xargs rm rm -f tei-xsl-*.zip rm -rf tei-xsl_* rm -f Documentation/stylebear Documentation/style.xml Documentation/customize.xml Documentation/teixsl.html Documentation/index.xml rm -rf release dist (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/Test'> (cd ..; for i in css/*; do rm -f `basename $i`;done) rm -f test*.odd.rnc test*epub test*pdf test*rdf test*text test*.xml.docx test*.xml.odt test*.tex test*.fo *.html *.xhtml *~ dummy* test.html test3.html test4.html *aux *vrb *out *log *nav *ent *snm *toc *.end *.1 *.2 test.xsd test.zip test*.dtd test-indexes.xml test37.xml test38.xml test39.xml test40.xml rm -f test*.rnc test*.json test*.rnc test*.combined.odd test*listing* test*.tei test*.rng test*.html5 test*.processedodd *.isosch rm -f oddbyexample.* index*div*html rm -f testdrama.compiled.xml rm -f test5.odt test7.xml test18.xml test19.xml test-index.xml test7.zip test11.xml test9.docx test9.odt content.xml.odt.listing content.xml.odt test.xml.docx.core test7.docx rm -f A54031.xml dcr.result test-rtf2tei.xml test29.xml rm -f xml.result rm -rf charts/ embeddings/ media/ _rels/ \[Content_Types\].xml rm -rf temp-dir-for-ant Pictures OEBPS META-INF mimetype files rm -f test.xlsx.xml *.result.tex *.result.pdf _slidelogo.png rm -f content.xml rm -f cocoatest*.xml make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/Test'> rm -rf tei-p5-xsl_* rm -rf tei-p5-xsl2_* (cd debian-tei-xsl/debian; rm -rf tei-xsl) rm -f teioo.jar rm -rf docx/ImageInfo/bin rm -f names.xml licensekey.txt runDoc.sh (for i in sciencejournal/*.html; do rm -f sciencejournal/`basename $i`;done) (for i in sciencejournal/*.xml; do rm -f sciencejournal/`basename $i`;done) BUILD Copy main XSL files test -d release/xsl/xml/tei/stylesheet || mkdir -p release/xsl/xml/tei/stylesheet/ for i in bibtex cocoa common csv docx dtd docbook epub epub3 fo html wordpress markdown html5 json latex latex nlm odd odds odt p4 pdf profiles/default rdf relaxng rnc schematron simple slides tbx tcp tite tools txt html xsd xlsx pdf verbatimxml ; do \ tar cf - $i | (cd release/xsl/xml/tei/stylesheet; tar xf - ); \ done java -jar lib/saxon9he.jar -it:main tools/getnames.xsl > names.xml BUILD Copy common files and documentation test -d release/xslcommon/xml/tei/stylesheet || mkdir -p release/xslcommon/xml/tei/stylesheet cp names.xml catalog.xml VERSION css/*.css i18n.xml release/xslcommon/xml/tei/stylesheet sh ./tools/mydch debian-tei-xsl/debian/changelog update debian changelog with 7.42.0 BUILD Run tests (cd Test; make) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/Test'> ../bin/teitorelaxng --odd test.odd test.rng WARNING: No localsource set. Will get a copy from http://www.tei-c.org/Vault/P5/. Convert test.odd to <http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/Test/test.rng> (tei to relaxng) using profile default [echo] Do ODD expand processing (schema ) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 16 seconds perl -i -p -e 's/generated from ODD source.*//' test.rng xmllint --format test.rng > temp; mv temp test.rng perl -i -pe 'BEGIN{undef $/;} s/<!--\n ?Schema[^>]+>//smg' test.rng if [ 0 -ne 1 ]; \ then diff test.rng expected-results/test.rng; fi (cd ..; for i in css/*; do test -f `basename $i` || ln -s $i `basename $i`;done) BUILD: testing html java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test.xml ../html/html.xsl cssFile=../tei.css useFixedDate=true | xmllint --format - > test.html if [ 0 -ne 1 ]; \ then diff test.html expected-results/test.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test.html checklinks.xsl <?xml version="1.0" encoding="UTF-8"?>java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test.xml ../html/html.xsl cssFile=../tei.css pageLayout=Complex useFixedDate=true | xmllint --format - > test-complex.html if [ 0 -ne 1 ]; \ then diff test-complex.html expected-results/test-complex.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test.xml ../profiles/ota/html/to.xsl cssFile=../tei.css useFixedDate=true | xmllint --format - | perl cleanup.pl > test-ota.html if [ 0 -ne 1 ]; \ then diff test-ota.html expected-results/test-ota.html; fi ../bin/teitohtml5 test.xml test.html5 WARNING: No localsource set. Will get a copy from http://www.tei-c.org/Vault/P5/. Convert test.xml to <http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/Test/test.html5> (tei to html5) using profile default [echo] XSLT generate HTML files (language en) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 6 seconds xmllint --encode utf-8 --format test.html5 | perl cleanup.pl > test.temp mv test.temp test.html5 if [ 0 -ne 1 ]; \ then diff test.html5 expected-results/test.html5; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test20.xml ../html/html.xsl useFixedDate=true | xmllint --format - > test20.html if [ 0 -ne 1 ]; \ then diff test20.html expected-results/test20.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar -versionmsg:off test3.xml ../html/html.xsl useFixedDate=true| xmllint --format - > test3.html java -Djava.awt.headless=true -jar ../lib/saxon9he.jar -versionmsg:off test4.xml ../html/html.xsl useFixedDate=true| xmllint --format - > test4.html if [ 0 -ne 1 ]; \ then diff test4.html test3.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test5.xml ../html/html.xsl autoBlockQuote=true useFixedDate=true | xmllint --format - > test5.xhtml if [ 0 -ne 1 ]; \ then diff test5.xhtml expected-results/test5.xhtml; fi java -Djava.awt.headless=true -jar lib/jing-20120724.0.0.jar -c xhtml.rnc test5.xhtml java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test6.xml ../html/html.xsl autoBlockQuote=true useFixedDate=true | xmllint --format - > test6.html if [ 0 -ne 1 ]; \ then diff test6.html expected-results/test6.html; fi java -Djava.awt.headless=true -jar lib/jing-20120724.0.0.jar -c xhtml.rnc test6.html java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test14.xml ../html/html.xsl useFixedDate=true| xmllint --format - > test14.html if [ 0 -ne 1 ]; \ then diff test14.html expected-results/test14.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test22.xml ../html/html.xsl useFixedDate=true| xmllint --format - > test22.html if [ 0 -ne 1 ]; \ then diff test22.html expected-results/test22.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test23.xml ../html/html.xsl useFixedDate=true| xmllint --format - > test23.html if [ 0 -ne 1 ]; \ then diff test23.html expected-results/test23.html; fi (mkdir files; cd files;java -Djava.awt.headless=true -jar ../../lib/saxon9he.jar ../testnotes1.xml ../../html/html.xsl splitLevel=4 useFixedDate=true STDOUT=false cssFile=../../tei.css) xmllint --format files/index.html > x ; mv x files/index.html xmllint --format files/one.html > x ; mv x files/one.html xmllint --format files/two.html > x ; mv x files/two.html xmllint --format files/three.html > x ; mv x files/three.html if [ 0 -ne 1 ]; \ then diff -r files expected-results/testnotes; fi rm -rf files (mkdir files; cd files;java -Djava.awt.headless=true -jar ../../lib/saxon9he.jar ../testnotes2.xml ../../html/html.xsl splitLevel=0 useFixedDate=true STDOUT=false cssFile=../../tei.css) xmllint --format files/index.html > x ; mv x files/index.html xmllint --format files/one.html > x ; mv x files/one.html xmllint --format files/three.html > x ; mv x files/three.html if [ 0 -ne 1 ]; \ then diff -r files expected-results/testnotes2; fi rm -rf files (mkdir files; cd files;java -Djava.awt.headless=true -jar ../../lib/saxon9he.jar ../testnotes2.xml ../../html/html.xsl splitLevel=4 useFixedDate=true STDOUT=false cssFile=../../tei.css) xmllint --format files/index.html > x ; mv x files/index.html xmllint --format files/one.html > x ; mv x files/one.html xmllint --format files/two.html > x ; mv x files/two.html xmllint --format files/three.html > x ; mv x files/three.html if [ 0 -ne 1 ]; \ then diff -r files expected-results/testnotes3; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test24.xml ../html/html.xsl useFixedDate=true | xmllint --format - > test24.html if [ 0 -ne 1 ]; \ then diff test24.html expected-results/test24.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test25.xml ../html/html.xsl useFixedDate=true | xmllint --format - > test25.html if [ 0 -ne 1 ]; \ then diff test25.html expected-results/test25.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test27.xml ../html/html.xsl useFixedDate=true cssFile=../tei.css cssSecondaryFile=../css/msdescription.css | xmllint --format - > test27.html if [ 0 -ne 1 ]; \ then diff test27.html expected-results/test27.html; fi rm -rf files java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test28.xml ../html/html.xsl splitLevel=0 STDOUT=false useFixedDate=true xmllint --format index.html > x ; mv x index.html if [ 0 -ne 1 ]; \ then diff index.html expected-results/test28.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test31.xml ../html/html.xsl cssFile="" cssInlineFiles=../tei.css useFixedDate=true | xmllint --format - > test31.html if [ 0 -ne 1 ]; \ then diff test31.html expected-results/test31.html; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test32.xml ../html/html.xsl cssFile="" cssInlineFiles=../tei.css useFixedDate=true | xmllint --format - > test32.html if [ 0 -ne 1 ]; \ then diff test32.html expected-results/test32.html; fi BUILD: testing p4top5 java -Djava.awt.headless=true -jar ../lib/saxon9he.jar -o:test17.tei test17.xml ../profiles/default/p4/from.xsl if [ 0 -ne 1 ]; \ then diff test17.tei expected-results/test17.tei; fi java -Djava.awt.headless=true -jar ../lib/saxon9he.jar A54031.tcp ../tcp/tcp2tei.xsl | xmllint --format - > A54031.xml if [ 0 -ne 1 ]; \ then diff A54031.xml expected-results/A54031.xml; fi BUILD: testing oddity ../bin/teitohtml5 --summaryDoc --odd test.odd test.odd.html WARNING: No localsource set. Will get a copy from http://www.tei-c.org/Vault/P5/. Convert test.odd to <http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/Test/test.odd.html> (tei to html5) using profile default [echo] Do ODD expand processing and conversion to TEI Lite (schema ) Warning: XML resolver not found; external catalogs will be ignored Warning: XML resolver not found; external catalogs will be ignored [echo] XSLT generate HTML files (language en) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 20 seconds xmllint --encode utf-8 --format test.odd.html | perl cleanup.pl> test.temp ; mv test.temp test.odd.html if [ 0 -ne 1 ]; \ then diff test.odd.html expected-results/test.odd.html; fi ../bin/teitoodd test.odd test.processedodd WARNING: No localsource set. Will get a copy from http://www.tei-c.org/Vault/P5/. Convert test.odd to <http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/Test/test.processedodd> (tei to odd) using profile default [echo] Do ODD expand processing (schema ) BUILD SUCCESSFUL Total time: 10 seconds java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test.processedodd ../odds/extract-isosch.xsl > test.isosch perl -i -p -e 's/generated .* by /generated by /' test.isosch if [ 0 -ne 1 ]; \ then diff test.isosch expected-results/test.isosch; fi 162,166c162 < < < < < <pattern id="test-div-constraint-abstractModel-structure-l-29"> --- > <pattern id="test-div-constraint-abstractModel-structure-l-29"> make[1]: *** [test-oddity] Error 1 make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/Test'> make: *** [test] Error 2 Build step 'Execute shell' marked build as failure Archiving artifacts

1 3

Reminder: Telecon next Thursday
by Hugh Cayless 28 Jun '16

28 Jun '16

Hi all, I know it's summer now, so I expect there will be a bit of a drop-off in availability, but we have a telecon scheduled for the 30th, at 09:00 EDT / 13:00 UTC / 14:00 BST / 15:00 CEST. Elli, will you be able to initiate a Google Hangout again? Please add any items you wish to discuss on the draft agenda at https://docs.google.com/document/d/1ly9QnWtGvU43ZgP139lwftlr7mT5TDV2pR0DS6D… Hugh

3 4

Stylesheets trip over whitespace
by Syd Bauman 27 Jun '16

27 Jun '16

I've apparently broken the Stylesheets build, but it doesn't look like it's anything I *did*. It looks like the output of running the extract-isosch.xsl program I was working on against the Test/test.processedodd does not match the output in Test/expected-results/test.isosch ... because of different whitespace. However, when I run that same transform locally, the result does match -- there is no blob of extra whitespace before the line '<pattern id="test-div-constraint-abstractModel-structure-l-29">', and thus my output matches that in Test/expected-results/. I am tempted to just ignore whitespace in the comparison, i.e. with `diff -Bb`, but that's probably a bad plan. :-| I'll try to mess with this some more today, but in the meantime, if anyone has any ideas ...

1 0

gitHelp
by Syd Bauman 27 Jun '16

27 Jun '16

I went to push up a commit. As is my usual habbit, I issued a `git status -uno` first. Git told me: | On branch dev | Your branch is ahead of 'origin/dev' by 4 commits. | (use "git push" to publish your local commits) | ... So that means I've committed 3 times that I don't remember. How do I find out what those commits were? (I.e. to what files, and what changes were made?) It's probably safe to just push (those other commits are probably just me saving work as I went along), but I'd prefer to know. Thanks.

3 2