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

website archeology: symlinks
by Kevin Hawkins 16 Jul '18

16 Jul '18

Folks, The backup of the TEI's web presence didn't include symlinks, we Ian (copied here) is having to recreate these. He has some notes from when the TEI website was moved to the ADHO infrastructure, but there are still some open questions, especially regarding the configuration used for P5 releases. He's looked at tei-install.sh (used in the release process) but still has some questions. I'm not sure who knows this process best. It might even be someone no longer on Council like James Cummings or Martin Holmes. Could someone get in touch with him to answer some questions? Kevin

2 1

listObject, objectName, object
by James Cummings 16 Jul '18

16 Jul '18

Hi all, In case you didn't notice, I added a comment to https://github.com/TEIC/TEI/issues/327#issuecomment-405109022 detailing my work today on the listObject, objectName, and object element. I was tasked with producing a strawman proposal. However, this strawman is fairly complete, and is fully implemented (saving prose in the Guidelines...there are some placeholder div/p) in the jamescummings-object branch of the repo. What I'm intending to do here is give a way for people to describe objects (text-bearing or otherwise) with the minimal number of changes to the existing TEI but with the maximal amount of expressiveness. Since the ticket has been hanging around since 2011 (and was certainly discussed before that), and we discussed it in detail at the F2F in Victoria, I think it better to get something minimal into the Guidelines and the develop it based on requests thereafter. I'm hoping that *after* the current release we might get it into the dev branch with some tweaks. The objectName, listObject, and object have the same relational semantics as you'd guess from persName/listPerson/person or placeName/listPlace/place. The content model is sort of like msDesc but without msIdentifier (but with model.nameLike so the objectName and idno etc) and without msContents. The example I've used is the text-bearing object: the Alfred Jewel. In any case, thought I'd mention it in case any of you not frantically doing tickets before our upcoming freeze would want to check it out and suggest any (hopefully minor) changes that you think should change before it works its way into the Guidelines after the release, then let me know. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University

1 0

test
by Scholger, Martina (martina.scholger＠uni-graz.at) 15 Jul '18

15 Jul '18

Hi all, this is just a test to check if the Council list is affected by the disk failure as well... Best, Martina

1 0

Stylesheets group meeting 2018-07-03 summary
by Syd Bauman 04 Jul '18

04 Jul '18

Quick summary of today's meeting: * SB, EB, HC, MH, RV * Seems no one has made any significant progress * Discussed tickets 136 and 138 * Consensus was that we think it is right that 138 is a "go". * MH has already committed code that adds rend="outOfDateTranslation" to the TEI Lite intermediate stage in ODD processing. * As for display, we lean towards something relatively subdued: a following asterisk with a mouse-over of "translation may be out of date" or some such. * We also think it would be a good idea if the interface allowed the reader to provide a suggested translation on the spot. E.g., there could be a "provide improved translation" link, which would launch an e-mail (or perhaps a web form) with the English value and space for a suggested translation. We opened a new ticket for this suggestion: TEI#1780. * Spent quite a bit of time on the tangential issue as to whether or not *all* constructs (elements, attributes, attribute value enumerations) should have glosses. In doing so we discovered that there are a few elements that should have glosses under the current editorial rules do not (e.g., <macroRef> and <modelGrp>). I do not think we created ticket for either of these issues, though. * It was proposed that we try meeting a week before Council regularly. We decided to keep with the current schedule (of the Tue following Council) for the summer, and that SB will post a Doodle poll or some such to figure out a new meeting time-slot for the next semester.

1 0

Stylesheets group - when to meet?
by Syd Bauman 22 Jun '18

22 Jun '18

We hold our meetings the Tue following the TEI Council meeting. Thus we had originally scheduled Tue 07-03 (at 13:00Z). However, Council has moved their Thu 06-28 meeting to Mon 07-09. Do we want to keep our meeting at the same slot, or move it? A) Tue 07-03 (keep it the same) B) Tue 07-10 (move it to the Tue after Council) C) Tue 07-17 (move it to the Tue the week after Council) D) Something else (will probably require Doodle poll) Personally, I am currently available all 3 of those, so I don't really care.

4 3

Connecting to teic.org?
by Hugh Cayless 19 Jun '18

19 Jun '18

Can anyone else connect to tei(a)teic.org? It's timing out for me. Just trying to figure out whether the problem's on my end or the server's. Thanks, Hugh

1 1

Re: [tei-council] TEI to Spanish meet-up at DH Mexico
by Alejandro Bia 16 Jun '18

16 Jun '18

Yes. I can also send it to the members of the HDH Association. Let me know the email address you prefer to use. Estimados colegas, En un esfuerzo por promover la disponibilidad y distribución plurilingüe de la Guía/manual del TEI, el Consejo Técnico del TEI desea invitarlo a una reunión informal y a una sesión de planificación a realizarse durante la próxima conferencia anual ADHO-DH que se celebrará en la Ciudad de México, para planificar y debatir la traducción de las especificaciones de la Guía del TEI al español. Nos encantaría contar con su participación en este esfuerzo después de la recepción inaugural del congreso DH el martes 26 de junio a las 8 pm. Si desea unirse a nosotros, por favor escriba una breve confirmación a martina.scholger(a)uni-graz.at <mailto: martina.scholger(a)uni-graz.at>. Best, Alex.- At 14:57 14/06/2018, you wrote: >Hi all, > >I'd like to send out the invitation for the >informal TEI to Spanish meet-up tomorrow and have some questions: > > 1. Alex, could you help me with the > translation? I think it would be nice to have one for Spanish mailinglists. > 2. I can remember that James recently told > me that there is an email address for the > Council chair which I can use for such > purposes. Can you tell me again what it is? I cannot find it... > 3. Does anyone have more ideas for channels: > TEI-L, redHD (mailinglist), Humanidades > Digitales on Slack, http://listserv.uleth.ca/mailman/listinfo/globaloutlookdh-l > 4. See the draft below... > >I'm glad to report that Gimena del Rio Riande and Luis Meneses will join us! > >Dear colleagues, > >in an effort to promote the multi-lingual >availability and distribution of the TEI >Guidelines, the TEI Council would like to invite >you to an informal meet-up and planning session >at the upcoming ADHO DH annual conference in >Mexico City, to plan and discuss the translation >of the TEI Guidelines specifications into Spanish. >We would be delighted if you would participate >in this endeavor after the DH Opening Reception >on Tuesday 26 June, at 8 pm. If you would like >to join us, please write a brief confirmation to >martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>. > >Best wishes, >Martina > > > >Martina Scholger >Zentrum für Informationsmodellierung >Austrian Centre for Digital Humanities >Universität Graz >A-8010 Graz | Elisabethstraße 59/III >+43 316 380 2291 >martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> >http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> >| http://gams.uni-graz.at<http://gams.uni-graz.at/> > >Institut für Dokumentologie und Editorik e.V. | https://www.i-d-e.de/ >Chair of the TEI Technical Council | http://www.tei-c.org/ > >-- >tei-council mailing list >tei-council(a)lists.tei-c.org >http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >PLEASE NOTE: postings to this list are publicly archived --------------------------------------------------------- ALEJANDRO BIA e-mail: abia(a)umh.es CIO - DEMI Centro de Investigación Operativa Departamento de Estadística, Matemáticas e Informática Área de Lenguajes y Sistemas Informáticos Universidad Miguel Hernández Ed. Torretamarit, Av. Universidad s/n, CP:03202, Elche, ESPAÑA Web: http://dhw.umh.es/alex-bia/ Tel: +34 966658973 Skype: alex-bia Twitter: @alex_bia --------------------------------------------------------- --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 3

TEI to Spanish meet-up at DH Mexico
by Scholger, Martina (martina.scholger＠uni-graz.at) 14 Jun '18

14 Jun '18

Hi all, I'd like to send out the invitation for the informal TEI to Spanish meet-up tomorrow and have some questions: 1. Alex, could you help me with the translation? I think it would be nice to have one for Spanish mailinglists. 2. I can remember that James recently told me that there is an email address for the Council chair which I can use for such purposes. Can you tell me again what it is? I cannot find it... 3. Does anyone have more ideas for channels: TEI-L, redHD (mailinglist), Humanidades Digitales on Slack, http://listserv.uleth.ca/mailman/listinfo/globaloutlookdh-l 4. See the draft below... I'm glad to report that Gimena del Rio Riande and Luis Meneses will join us! Dear colleagues, in an effort to promote the multi-lingual availability and distribution of the TEI Guidelines, the TEI Council would like to invite you to an informal meet-up and planning session at the upcoming ADHO DH annual conference in Mexico City, to plan and discuss the translation of the TEI Guidelines specifications into Spanish. We would be delighted if you would participate in this endeavor after the DH Opening Reception on Tuesday 26 June, at 8 pm. If you would like to join us, please write a brief confirmation to martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>. Best wishes, Martina Martina Scholger Zentrum für Informationsmodellierung Austrian Centre for Digital Humanities Universität Graz A-8010 Graz | Elisabethstraße 59/III +43 316 380 2291 martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> | http://gams.uni-graz.at<http://gams.uni-graz.at/> Institut für Dokumentologie und Editorik e.V. | https://www.i-d-e.de/ Chair of the TEI Technical Council | http://www.tei-c.org/

1 0

example examples; where is our <schemaSpec>?
by Syd Bauman 13 Jun '18

13 Jun '18

I'm confused. I am trying to remove macro.anyXML from P5 per its deprecation message. You might think this would be trivial. Remove the one reference to it from Source/Guidelines/en/ST-Infrastructure.xml,[1] and `git mv Source/Specs/macro.anyXML.xml Source/Defunct/`. Presto. No such luck. I've been at this for hours, now, and I'm getting quite close. The problem I'm running into now is that (in my local directory) <egXML> is now defined by <anyElement>, not by macro.anyXML, as the latter does not exist. But when used in a content model, <anyElement> (for reasons I cannot explain and I doubt anyone can) does not permit elements from the TEI namespace or the <teix:egXML> element. In P5 itself, it makes sense to disallow elements from the TEI namespace in <teix:egXML>. But I don't think it makes sense to disallow <teix:egXML> from being used inside <teix:egXML> itself. In fact, *we use a <teix:egXML> inside a <teix:egXML> twice in P5*, both in the tagdoc for <egXML>. So I thought I would try removing the restriction for P5 itself that <anyElement> not allow <teix:egXML>. The tagdoc for <anyElement> says Default elements and namespaces to be excluded are set on the <att>defaultExceptions</att> attribute of the <gi>schemaSpec</gi>. <att>except</att> may be used when the exceptions need to be locally specified. So, I went off looking for the <schemaSpec defaultExceptions="teix:egXML http://www.tei-c.org/ns/1.0"> for P5. To my surprise, I could not find *any* <tei:schemaSpec> that seems to be the definition of our schema.[2] Anyone know where the <schemaSpec> generated by the source in Source/ is? I'm guessing there isn't one, and that's why you *always* need to use a customization file (if only tei_all), because it is what has the <schemaSpec>. But then, where are the default exclusions for @except of <anyElement> declared? I tried changing the <anyElement> in the <content> declaration of <egXML> to just except="http://www.tei-c.org/ns/1.0", in the hopes that that would override (rather than add to) the default. Didn't work. So I went back to re-defining <teix:egXML> in p5odds.odd. But I think that has always been a mistake, and hope we can find some other fix. Committed at b1e0267. Hope Mr. Jenkins is happy. Notes ----- [1] Like many other macros, it is part of ST via an XInclude, so you just have to delete the one line. [2] Excluding Exemplars/ and Test/, the following are all the .xml or .odd files that have a <schemaSpec>, and their attributes: | ---------Incubator/TBX/TEI-TBX.odd | ident=TBXBasic | start=TEI teiCorpus | | ---------P5/p5odds-examples.odd | ns=http://www.tei-c.org/ns/Examples | ident=p5odds-examples | prefix=TEI_ | start=p egXML | | ---------P5/p5odds.odd | ident=p5odds | prefix=TEI_ | start=TEI schemaSpec elementSpec classSpec macroSpec dataSpec div | | ---------Extensions/Menota/menota.odd | ident=menota | start=TEI teiCorpus | | ---------Extensions/Lite/teilite.xml | ident=teilite | start=TEI | | ---------Extensions/ProtestantCemetery/cem.odd | ident=teicem | start=TEI teiCorpus | | ---------Extensions/BNC/bncxml.odd | ident=bncxml | xml:lang=en | prefix= | ns= | start=teiHeader bncDoc teiCorpus | | ---------Extensions/Lampeter/lampext.xml | ident=lamptei | start=TEI teiCorpus | | ---------Documents/notatedMusic/notatedMusic.xml | ident=tei_notatedmusic | docLang=en | xml:lang=en | targetLang=en | start=TEI TEICorpus | | ---------Documents/TCW/anyXML.odd | ident=anyXML | | ---------Documents/oddmanual/index.xml | ident=oddex1 | start=TEI | | ---------Documents/oddmanual/teidoc.odd | ident=teidoc | | ---------Documents/Object/object.odd | ident=object | start=TEI | | ---------Documents/pureODD/chainingTuto/justTranscription.xml | ident=justTranscription | start=text | source=motherODD.compiled | | ---------Documents/pureODD/chainingTuto/motherODD.xml | ident=mother | start=TEI | | ---------Documents/pureODD/chainingTuto/justMetadata.xml | ident=justMetadata | start=teiHeader | source=motherODD.compiled | | ---------genetic/geneticTEI-0.xml | ident=geneticTEI | docLang=en | prefix=tei_ | start=teiCorpus TEI | xml:lang=en | targetLang=en | | ---------genetic/geneticTEI.xml | ident=geneticTEI | docLang=en | xml:lang=en | targetLang=en | | ---------genetic/p5genetic.xml | ident=testgenetic | start=TEI | | ---------I18N/examples.odd | ident=examples | prefix=TEI_ | start=TEI | | ---------I18N/testodd.xml | ident=test | start=TEI | | ---------I18N/teilite-es.xml | ident=teilite-es | start=TEI

1 0

Re: [tei-council] Fwd: oxygen-tei plugin versioning and release process
by Syd Bauman 08 Jun '18

08 Jun '18

From: Martin Holmes <mholmes(a)uvic.ca> Subject: oxygen-tei plugin versioning and release process Hi all, I've been talking with Alex from Oxygen on a ticket on the oxygen-tei plugin repo about something that Council really needs to decide on. One of the reasons we release the stable plugin is so that people who use older versions of Oxygen and can't afford to upgrade can still get the latest TEI and Stylesheets code. For that reason, we've tried to keep our plugin compatible with older versions (currently we still support 15.2). The problem with that is that as Oxygen moves forward and adds new features, we're still building our plugin against an older Oxygen codebase, and therefore installing the plugin can't take advantage of newer features that might be available (such as the Image Map functionality that's recently been added). What I hadn't really realized before Alex explained it is that you can have multiple versions of a plugin which are targeted at different versions of Oxygen. That would enable us to do something like this: 1. Make a tag of the current master branch as 15.2-compatible (so master can be moved forward later without confusion). 2. Create tags for each significant Oxygen version change which may prevent an older version from installing the plugin, or will impact its behaviour. The Oxygen folks will help us with that. 3. Build stable versions of the plugin for release based on each of these, and link to them in the update file, with their maximum supported Oxygen version number specified. 4. Build our "bleeding edge" plugin version against the oxygen_integration branch, which is up to date with the latest Oxygen dev code, so that we get some warning of any upcoming changes to Oxygen that may affect the plugin. Pros: End-users should have more reliable Oxygen functionality within the plugin, and be able to take advantage of all the Oxygen features supported by whatever version they're using. Cons: More complexity in the build process, and more versions of the plugin to version, store, serve and explain. Does this make sense to everyone? Do we want to continue to maintain compatibility with version 15.2, or should we move that forward a bit, and if so how much? Cheers, Martin

1 0

Time to pack up the family silver again?
by Lou Burnard 08 Jun '18

08 Jun '18

Migration to gitlab anyone? Sent from my Huawei Mobile

4 4

Ontologies SIG revival
by Elisa Beshero-Bondar 07 Jun '18

07 Jun '18

Hi everyone! Connie Crompton and I have just had a lovely chat here at the DHSI about reviving the Ontologies SIG. She has been in touch with Kathryn Tomasek and Christian-Emil Ore about this already, but wants to make it official and will likely be writing us with some questions. I'd like to help her with this...wonder if anyone else here is interested, too? Our discussion was about finding ways to help the TEI community (and ourselves) with researching and working out good practices for mapping TEI to other ontologies--and to try to bring people together who already have significant experience with this (I'm thinking people like Jeff Witt of SCTA). Perhaps we might have a first meeting of the revived SIG in Tokyo (Connie plans to be there)--and we were wondering if we might even host a hackathon, if that's possible. We'll be hearing more from Connie pretty soon--but in the meantime, does anyone have ideas to help kick this off? Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

1 0

Next Council call
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Jun '18

06 Jun '18

Hi all, thank you for voting! Our next call is on Monday, July 9 (08:00 EDT, 13:00 BST, 14:00 CEST). Best, Martina

1 0

future of SIG on Libraries; best practices for <sourceDesc>
by Kevin Hawkins 05 Jun '18

05 Jun '18

Hello Council members, Ian, our sysadmin, and I have been corresponding and working through the details of the plan to switch over from OpenCMS to WordPress. As with the rest of the process, we keep turning up details that we want to get right to minimize breakage and downtime. We're making progress, so I still think we'll manage to wrap up this work soon! Anyway, I'm writing today about the future of the SIG on Libraries. (Any other SIG convenor would write to the Council chair and ask for the Council to discuss, but since I can still post to this list, I thought I'd just write to you directly.) As in our SIG report delivered in Victoria and as I wrote to the SIG's email list in November, Stefanie Gehrke and I (the currently named convenors of the SIG) need to step down from our roles. No one else has stepped forward to take over. I suggest we retire the SIG until the day when someone else wants to revive it. (You might want to do the same for the other long inactive SIGs. We can certainly update the website to show which are actually active.) Separately, though, you might remember a discussion in mid-May on TEI-L about best practices around use of <sourceDesc>. Martin Mueller suggested that the SIG on Libraries prepare a proposal on this, and he volunteered to lead such an effort: https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;93f8cf13.1805 It seems that this might be better handled as a Council-chartered task force rather than as an activity of the SIG on Libraries, which in theory addresses an ongoing set of interests. Please feel free to get that work going. Neither Stefanie nor I are able to take on this work at this time. Kevin

2 3

Build failed in Jenkins: TEIP5-Documentation-dev #2751
by Victoria TEI Jenkins 05 Jun '18

05 Jun '18

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/2751/display/red…> Changes: [s.bauman] More work on #1476 ------------------------------------------ Started by upstream project "TEIP5-Test-dev" build number 3573 originally caused by: Started by an SCM change Building in workspace <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-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/TEI.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/TEI.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/TEIC/TEI.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 b25ef697601e033efac2eb36139d814401f1ce47 (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f b25ef697601e033efac2eb36139d814401f1ce47 Commit message: "merge in latest BIB changes" > git rev-list --no-walk bd322052549d1bccbd9b0c96556c0f6047e84bae # timeout=10 [workspace] $ /bin/bash -xe /tmp/jenkins7816725202958381506.sh + svn update Skipped '.' Summary of conflicts: Skipped paths: 1 [workspace] $ /bin/bash -xe /tmp/jenkins4894001607420041581.sh + cd P5 ++ pwd + make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> clean html-web epub3 Guidelines.pdf (cd Exemplars; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/Exemplars'> mv tei_lite_fr.nvdl tei_lite_fr.nvdl.bak rm -f *.processed *.xsd *.dtd *.doc.* *.rnc tei*.xsl tei*.rng *.compiled* *~ *.xi *.isosch *.epub *.pdf *.html *.nvdl *-teix* mv tei_lite_fr.nvdl.bak tei_lite_fr.nvdl rm -f exnames.xml rm -f enrich.rng isofs.rng rm -f names.xml *properties rm -f [A-Z]*xml make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/Exemplars'> (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/Test'> rm -f test*.doc.xml test*.rnc test*.dtd test*.compiled.* test*.xsd test*.rnc test*.rng test*.xsl test*.isosch rm -rf LOG *~ *.xsd Schema RomaResults DTD rm -rf *.doc.* rm -f detest.log detest.log.all rm -f *-examples.rng *-examples.rnc *test*.nvdl *-ex.odd rm -f detest.rnc detest.rng detest.dtd detest.isosch make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/Test'> rm -rf release Guidelines Guidelines-web Schema DTD dtd Split rm -rf Guidelines.??? Guidelines-* rm -f *.isosch.xsl rm -f *.stamp rm -f *.xsd rm -f Exemplars/stdout rm -f Test/*.isosch rm -f Test/detest.dtd Test/detest.rnc Test/detest.rng Test/detest.xsl rm -f Test/stdout rm -f Utilities/guidelines.xsl rm -f anything buildweb.xml rm -f p5.sch p5.isosch p5.xml p5subset.xml p5subset.json p5subset.js rm -f p5attlist.txt rm -f p5odds-examples.rng p5odds-examples.rnc p5odds.rng p5odds.rnc p5odds.isosch rm -f pdfbuild.log rm -f stripspace.xsl.model rm -f tei-*.zip rm -f tei-p5-*_*build rm -f tei-p5-*_*changes rm -f tei-p5-*_*deb rm -f teiwebsiteguidelines.zip rm -rf FASC-* rm -rf catalogue.* modList rm -rf valid v.xml ValidatorLog.xml Utilities/pointerattributes.xsl graphics.sh missfont.log v.body v.header Schematron1.xml Schematron2.xml Checking you have running XML tools and Perl before trying to run transform... Ant:/usr/bin/ant Perl:/usr/bin/perl Java:/usr/bin/java xmllint:/usr/bin/xmllint touch check.stamp get latest date: VCS is git if [ "git" = "svn" ] ; \ then \ if [ true = "true" ] ; \ then svn info --xml svn://svn.code.sf.net/p/tei/code/trunk/P5 ; \ else svn info --xml ; \ fi > repodate.xml ; \ fi if [ git = "git" ] ; \ then \ git log --max-count=1 --pretty=format:"<info type=\"git\"><entry><commit revision=\"%h\"><date>%ai</date></commit></entry></info>" > repodate.xml ; \ fi BUILD: Generate modular DTDs, Schemas, Schematron and miscellaneous outputs ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> -DDRIVER=Source/guidelines-en.xml base subset outputs [echo] make modular DTDs, RELAXNG schemas, json, odd schemas, schematron files [echo] Using <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> for XSL stylesheets [echo] Do ODD processing for p5odds.odd [echo] Do ODD processing for p5odds-examples.odd BUILD SUCCESSFUL Total time: 53 seconds BUILD: Generate modular RELAX NG (compact) schemas using trang (cd Schema; for i in *rng; do java -jar ../Utilities/lib/trang.jar $i `basename $i .rng`.rnc;done) touch schemas.stamp BUILD: Making HTML Guidelines for language en rm -rf Guidelines-web perl -p -e \ "s+http://www.tei-c.org/release/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…;> \ s+/usr/share/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…;"> \ Utilities/guidelines.xsl.model > Utilities/guidelines.xsl if [ -n ] ; then curl -sL http://www.tei-c.org/ | sed 's/content="text\/html"/content="text\/html; charset=utf-8"/' | xmllint --html --noent --dropdtd --xmlout - > Utilities/teic-index.xml;fi for i in en ;do \ mkdir -p Guidelines-web/$i/html; \ cp odd.css guidelines.css guidelines-print.css Guidelines-web/$i/html; \ (cd Source/Guidelines/en; tar --exclude .svn -c -f - Images) | (cd Guidelines-web/$i/html; tar xf - );\ (cd webnav; tar --exclude .svn -c -f - .) | (cd Guidelines-web/$i/html; tar xf - ); \ done echo '<project basedir="." default="html" name="buildweb"><import file="antbuildweb.xml"/><target name="html">' \ > buildweb.xml for i in en ;do \ echo "<buildweb lang=\"$i\"/>" >> buildweb.xml; \ done echo '</target></project>' >> buildweb.xml ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f buildweb.xml -DgoogleAnalytics= [echo] Make Guidelines web pages for language en BUILD SUCCESSFUL Total time: 1 minute 21 seconds # commented out for DEBUGing: rm -f buildweb.xml Utilities/teic-index.xml touch html-web.stamp ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -f <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> -lib Utilities/lib/saxon9he.jar -Dprofiledir=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> -Dprofile=tei -DinputFile=`pwd`/p5.xml -DoutputFile=`pwd`/Guidelines.epub -Dcoverimage=`pwd`/Utilities/cover.jpg BUILD SUCCESSFUL Total time: 1 minute 20 seconds java -jar Utilities/epubcheck3.jar Guidelines.epub Epubcheck Version 3.0.1 Validating against EPUB version 3.0 ERROR: Guidelines.epub: OPS/XHTML file OPS/ref-egXML.html is missing ERROR: Guidelines.epub/OPS/TD.html(1,16120): 'OPS/ref-teix_egXML.html': referenced resource is not declared in the OPF manifest. ERROR: Guidelines.epub/OPS/BIB.html(1,150820): 'index-egXML-d41e143502': fragment identifier is not defined in 'OPS/ref-egXML.html' WARNING: Guidelines.epub: item (OPS/ref-teix_egXML.html) exists in the zip file, but is not declared in the OPF file Check finished with warnings or errors make: *** [epub3] Error 1 Build step 'Execute shell' marked build as failure Not sending mail to unregistered user s.bauman(a)neu.edu

1 2

Re: [tei-council] upcoming Stylesheets meeting prep
by James Cummings 04 Jun '18

04 Jun '18

Hi all, Just to note that I'll be absent for the next Stylesheets meeting (I've got an appointment with someone from another institution that I can't miss.) I think all the info required is on the ticket I was assigned to but just needs to be done. Apologies, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: tei-council-bounces(a)lists.tei-c.org <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu> Sent: 03 June 2018 15:42:13 To: TEI Council; Lou Burnard; Martin Holmes Subject: Re: [tei-council] upcoming Stylesheets meeting prep Reminder, that we are planning on meeting on Tue 05 Jun at 13:00Z.[1] It seems like other folks are not having trouble with screen sharing in Google Hangouts, so I guess we should just use that again. HOWEVER, I have foolishly double-booked myself, and am scheduled to be on duty Tue day. Thus there is a good chance (perhaps 33%) that I myself will miss some or all of this meeting. Sigh. But that shouldn't slow y'all down. With three mildly complex tickets, which, of course, everyone will have made at least some progress on, there is plenty to talk about. List of timezones and tickets are in the quoted mail, below. > We are planning to meet in 10 days, on Tue 05 Jun at 13:00Z.[1] > > Last time we agreed to work on our current tickets in our current > medium-sized teams to report back to the group. Tickets and teams > are unchanged from last month.[2] > > Communication, however, may have to change. We have been using > Google Hangouts, but as far as I know (which is not far at all), > Google Hangouts no longer supports screen sharing. Any thoughts on > what we should do? (Does Brown's paid Google Hangouts support > screen sharing? Does Skype allow conference calls of nearly a > dozen people? Should we ask TEI-C to just buy a conferencing > system? Are there any open source alternatives, whether free or > costly?) > > Notes > ----- > [1] I believe that would be > 06:00 PST (Martin) > 09:00 EST (Syd, Hugh, Raff, Elisa, Elli, Sarah) > 10:00 ART (Alejandro?) > 14:00 BST (James, Magdelena?) > 15:00 CET (Alejandro?, Lou, Martina, Peter, Magdelena?) > > [2] > 1. Ticket 125 (https://github.com/TEIC/Stylesheets/issues/125) > * Elisa Beshero-Bondar > * Alejandro Bia > * Hugh Cayless > * James Cummings > > 2. Ticket 138 (https://github.com/TEIC/Stylesheets/issues/138) > * Lou Burnard > * Martin Holmes > * Martina Scholger > * Magdalena Turska > > 3. Ticket 136 (https://github.com/TEIC/Stylesheets/issues/136) > * Syd Bauman > * Peter Stadler > * Sarah Stanley > * Raffaele Viglianti -- tei-council mailing list tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived

1 0

upcoming Stylesheets meeting prep
by Syd Bauman 03 Jun '18

03 Jun '18

We are planning to meet in 10 days, on Tue 05 Jun at 13:00Z.[1] Last time we agreed to work on our current tickets in our current medium-sized teams to report back to the group. Tickets and teams are unchanged from last month.[2] Communication, however, may have to change. We have been using Google Hangouts, but as far as I know (which is not far at all), Google Hangouts no longer supports screen sharing. Any thoughts on what we should do? (Does Brown's paid Google Hangouts support screen sharing? Does Skype allow conference calls of nearly a dozen people? Should we ask TEI-C to just buy a conferencing system? Are there any open source alternatives, whether free or costly?) Notes ----- [1] I believe that would be 06:00 PST (Martin) 09:00 EST (Syd, Hugh, Raff, Elisa, Elli, Sarah) 10:00 ART (Alejandro?) 14:00 BST (James, Magdelena?) 15:00 CET (Alejandro?, Lou, Martina, Peter, Magdelena?) [2] 1. Ticket 125 (https://github.com/TEIC/Stylesheets/issues/125) * Elisa Beshero-Bondar * Alejandro Bia * Hugh Cayless * James Cummings 2. Ticket 138 (https://github.com/TEIC/Stylesheets/issues/138) * Lou Burnard * Martin Holmes * Martina Scholger * Magdalena Turska 3. Ticket 136 (https://github.com/TEIC/Stylesheets/issues/136) * Syd Bauman * Peter Stadler * Sarah Stanley * Raffaele Viglianti

5 4

doodle next call
by Scholger, Martina (martina.scholger＠uni-graz.at) 31 May '18

31 May '18

Hi all, here is the doodle poll for our next call: https://doodle.com/poll/ns9ciwf5xt65up4v Best, Martina Martina Scholger Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz Austria martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at> https://informationsmodellierung.uni-graz.at<https://informationsmodellierung.uni-graz.at/> | https://gams.uni.graz.at<https://gams.uni.graz.at/> Institut für Dokumentologie und Editorik e.V. | https://i-d-e.de<https://i-d-e.de/> Chair of the TEI Technical Council | http://tei-c.org

1 0

Hangout
by Scholger, Martina (martina.scholger＠uni-graz.at) 31 May '18

31 May '18

Elli, could you start the call? Martina Mag. Dr.phil. Martina Scholger Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz Austria martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at> https://informationsmodellierung.uni-graz.at<https://informationsmodellierung.uni-graz.at/> | https://gams.uni.graz.at<https://gams.uni.graz.at/> Institut für Dokumentologie und Editorik e.V. | https://i-d-e.de<https://i-d-e.de/> Chair of the TEI Technical Council | http://tei-c.org

2 1

Call on Thursday 31st
by Scholger, Martina (martina.scholger＠uni-graz.at) 28 May '18

28 May '18

Hi all, our next conference call is scheduled for Thursday 31st (08:00 EDT, 13:00 BST, 14:00 CEST). Here is the agenda - please add your topics: http://tinyurl.com/y77zcw4j Could you, Elli or Raff, start the call? Best wishes, Martina

1 0

F2F Tokyo
by Scholger, Martina (martina.scholger＠uni-graz.at) 15 May '18

15 May '18

Dear all, I want to confirm that our meeting in Tokyo can take place on Friday 7th and Saturday 8th. What we still have to clarify is the internet connection, since the conference venue only provides Eduroam. I think that not all Council members do have Eduroam, is that correct? In this case Kyionori will organize a room at another place. Please let me know soon in case you don't have Eduroam access. Best wishes, Martina

2 2

Re: [tei-council] oXygen Add-ons error for GitHub tei-releases page
by James Cummings 14 May '18

14 May '18

Just to note that the URL that Peter mentioned at Oxford should be replaced with: https://faqingperplxd.wordpress.com/2014/04/02/auto-update-your-tei-framewo… (even though it is, of course, out of date.) I can't expect that my blog at blogs.it.ox.ac.uk will continue to be available and I'm unable to edit it any more. (Whereas I can with the wordpress one.) Just thought I'd mention it. James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: tei-council-bounces(a)lists.tei-c.org <tei-council-bounces(a)lists.tei-c.org> on behalf of Peter Stadler <stadler(a)edirom.de> Sent: 13 May 2018 20:35:17 To: tei-council(a)lists.tei-c.org Subject: Re: [tei-council] oXygen Add-ons error for GitHub tei-releases page Elisa, ad 1) Pointing at the GitHub release pages seems wrong and probably never worked? The oXygen „Add-On-Update-Site“ is actually supposed to be a file, in our case „updateSite.oxygen" which can be found e.g. at http://jenkins.tei-c.org/job/oxygen-tei-stable/lastSuccessfulBuild/artifact… But you probably knew before from reading http://blogs.it.ox.ac.uk/jamesc/2014/04/02/auto-update-your-tei-framework-i…, so this is merely to confirm the wrong URL. Best Peter > Am 11.05.2018 um 22:39 schrieb Elisa Beshero-Bondar <ebb8(a)PITT.EDU>: > > Council-- For a long while now, my oXygen has included this site in its > Add-ons list in Preferences: > https://github.com/TEIC/oxygen-tei/releases I can't remember when I set > this, but it might have been a year or more ago. I'm now noticing some > errors I don't recall seeing before--and I don't know if this is connected > to my updating oXygen to the latest maintenance build of version 20 or not? > Here are the errors I see: > > 1) > Description Invalid update site. Cause: Cannot find the declaration of > element 'html'. > Severity Error > System ID https://github.com/TEIC/oxygen-tei/releases > > 2) Problem while trying to acquire lock: > > 404 Not Found for: https://github.com/TEIC/oxygen-tei/releases > If the current lock expires during editing you could overwrite changes made > by the current lock owner. > It is strongly recommended to cancel the open operation. > > Is anyone else seeing anything like this? Apologies if this is a known > issue, but I didn't see anything that looked like documentation of this on > the GitHub repo in question! > > Thanks for any perspective... > Elisa > -- > Elisa Beshero-Bondar, PhD > Director, Center for the Digital Text | Associate Professor of English > University of Pittsburgh at Greensburg | Humanities Division > 150 Finoli Drive > Greensburg, PA 15601 USA > E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> > Development site: http://newtfire.org > -- > tei-council mailing list > tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > PLEASE NOTE: postings to this list are publicly archived

2 1

oXygen Add-ons error for GitHub tei-releases page
by Elisa Beshero-Bondar 14 May '18

14 May '18

Council-- For a long while now, my oXygen has included this site in its Add-ons list in Preferences: https://github.com/TEIC/oxygen-tei/releases I can't remember when I set this, but it might have been a year or more ago. I'm now noticing some errors I don't recall seeing before--and I don't know if this is connected to my updating oXygen to the latest maintenance build of version 20 or not? Here are the errors I see: 1) Description Invalid update site. Cause: Cannot find the declaration of element 'html'. Severity Error System ID https://github.com/TEIC/oxygen-tei/releases 2) Problem while trying to acquire lock: 404 Not Found for: https://github.com/TEIC/oxygen-tei/releases If the current lock expires during editing you could overwrite changes made by the current lock owner. It is strongly recommended to cancel the open operation. Is anyone else seeing anything like this? Apologies if this is a known issue, but I didn't see anything that looked like documentation of this on the GitHub repo in question! Thanks for any perspective... Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

3 3

Stylesheets group meeting 2018-05-01 summary
by Syd Bauman 06 May '18

06 May '18

Quick summary of last week's meeting: * We talked aobut tickets that had been assigned.[1] * We agreed to continue working on them as currently assigned, and report back to the group at our next meeting (06-05 13:00Z). * New system seems good overall but probably needs tweaking; Syd thinks smaller groups and earlier notification would be in order, but there was not a lot of concensus on that. * One possibility is to not triage and assign tickets separately, but rather just use this monthly mtg as an opportunity for people to present their work on tickets so far (allowing the monthly ticket triage person to assign 'em as usual). [1] 1. Ticket 125 (https://github.com/TEIC/Stylesheets/issues/125) * Alejandro Bia * Elisa Beshero-Bondar * Hugh Cayless * James Cummings 2. Ticket 138 (https://github.com/TEIC/Stylesheets/issues/138) * Lou Burnard * Magdalena Turska * Martin Holmes * Martina Scholger 3. Ticket 136 (https://github.com/TEIC/Stylesheets/issues/136) * Peter Stadler * Raffaele Viglianti * Sarah Stanley * Syd Bauman

1 0

Build failed in Jenkins: TEIP5-Documentation-dev #2744
by Victoria TEI Jenkins 01 May '18

01 May '18

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/2744/display/red…> Changes: [elli_mylonas] adding @source attribute to egXML per #1476 again [elli_mylonas] fix jenkins error from previous commit for #1476 ------------------------------------------ Started by upstream project "TEIP5-Test-dev" build number 3566 originally caused by: Started by an SCM change Building in workspace <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-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/TEI.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/TEI.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/TEIC/TEI.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 777bbcf034810b617375d4effc688a41bfb80452 (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f 777bbcf034810b617375d4effc688a41bfb80452 Commit message: "fix jenkins error from previous commit for #1476" > git rev-list --no-walk 6c27e740433e7feabae1881820165d074ac1fa89 # timeout=10 [workspace] $ /bin/bash -xe /tmp/jenkins5200974305358788284.sh + svn update Skipped '.' Summary of conflicts: Skipped paths: 1 [workspace] $ /bin/bash -xe /tmp/jenkins1680818638670853255.sh + cd P5 ++ pwd + make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> clean html-web epub3 Guidelines.pdf (cd Exemplars; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/Exemplars'> mv tei_lite_fr.nvdl tei_lite_fr.nvdl.bak rm -f *.processed *.xsd *.dtd *.doc.* *.rnc tei*.xsl tei*.rng *.compiled* *~ *.xi *.isosch *.epub *.pdf *.html *.nvdl *-teix* mv tei_lite_fr.nvdl.bak tei_lite_fr.nvdl rm -f exnames.xml rm -f enrich.rng isofs.rng rm -f names.xml *properties rm -f [A-Z]*xml make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/Exemplars'> (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/Test'> rm -f test*.doc.xml test*.rnc test*.dtd test*.compiled.* test*.xsd test*.rnc test*.rng test*.xsl test*.isosch rm -rf LOG *~ *.xsd Schema RomaResults DTD rm -rf *.doc.* rm -f detest.log detest.log.all rm -f *-examples.rng *-examples.rnc *test*.nvdl *-ex.odd rm -f detest.rnc detest.rng detest.dtd detest.isosch make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/Test'> rm -rf release Guidelines Guidelines-web Schema DTD dtd Split rm -rf Guidelines.??? Guidelines-* rm -f *.isosch.xsl rm -f *.stamp rm -f *.xsd rm -f Exemplars/stdout rm -f Test/*.isosch rm -f Test/detest.dtd Test/detest.rnc Test/detest.rng Test/detest.xsl rm -f Test/stdout rm -f Utilities/guidelines.xsl rm -f anything buildweb.xml rm -f p5.sch p5.isosch p5.xml p5subset.xml p5subset.json p5subset.js rm -f p5attlist.txt rm -f p5odds-examples.rng p5odds-examples.rnc p5odds.rng p5odds.rnc p5odds.isosch rm -f pdfbuild.log rm -f stripspace.xsl.model rm -f tei-*.zip rm -f tei-p5-*_*build rm -f tei-p5-*_*changes rm -f tei-p5-*_*deb rm -f teiwebsiteguidelines.zip rm -rf FASC-* rm -rf catalogue.* modList rm -rf valid v.xml ValidatorLog.xml Utilities/pointerattributes.xsl graphics.sh missfont.log v.body v.header Schematron1.xml Schematron2.xml Checking you have running XML tools and Perl before trying to run transform... Ant:/usr/bin/ant Perl:/usr/bin/perl Java:/usr/bin/java xmllint:/usr/bin/xmllint touch check.stamp get latest date: VCS is git if [ "git" = "svn" ] ; \ then \ if [ true = "true" ] ; \ then svn info --xml svn://svn.code.sf.net/p/tei/code/trunk/P5 ; \ else svn info --xml ; \ fi > repodate.xml ; \ fi if [ git = "git" ] ; \ then \ git log --max-count=1 --pretty=format:"<info type=\"git\"><entry><commit revision=\"%h\"><date>%ai</date></commit></entry></info>" > repodate.xml ; \ fi BUILD: Generate modular DTDs, Schemas, Schematron and miscellaneous outputs ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> -DDRIVER=Source/guidelines-en.xml base subset outputs [echo] make modular DTDs, RELAXNG schemas, json, odd schemas, schematron files [echo] Using <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> for XSL stylesheets [echo] Do ODD processing for p5odds.odd [echo] Do ODD processing for p5odds-examples.odd BUILD SUCCESSFUL Total time: 54 seconds BUILD: Generate modular RELAX NG (compact) schemas using trang (cd Schema; for i in *rng; do java -jar ../Utilities/lib/trang.jar $i `basename $i .rng`.rnc;done) touch schemas.stamp BUILD: Making HTML Guidelines for language en rm -rf Guidelines-web perl -p -e \ "s+http://www.tei-c.org/release/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…;> \ s+/usr/share/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…;"> \ Utilities/guidelines.xsl.model > Utilities/guidelines.xsl if [ -n ] ; then curl -sL http://www.tei-c.org/ | sed 's/content="text\/html"/content="text\/html; charset=utf-8"/' | xmllint --html --noent --dropdtd --xmlout - > Utilities/teic-index.xml;fi for i in en ;do \ mkdir -p Guidelines-web/$i/html; \ cp odd.css guidelines.css guidelines-print.css Guidelines-web/$i/html; \ (cd Source/Guidelines/en; tar --exclude .svn -c -f - Images) | (cd Guidelines-web/$i/html; tar xf - );\ (cd webnav; tar --exclude .svn -c -f - .) | (cd Guidelines-web/$i/html; tar xf - ); \ done echo '<project basedir="." default="html" name="buildweb"><import file="antbuildweb.xml"/><target name="html">' \ > buildweb.xml for i in en ;do \ echo "<buildweb lang=\"$i\"/>" >> buildweb.xml; \ done echo '</target></project>' >> buildweb.xml ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f buildweb.xml -DgoogleAnalytics= [echo] Make Guidelines web pages for language en BUILD SUCCESSFUL Total time: 1 minute 20 seconds # commented out for DEBUGing: rm -f buildweb.xml Utilities/teic-index.xml touch html-web.stamp ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -f <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> -lib Utilities/lib/saxon9he.jar -Dprofiledir=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> -Dprofile=tei -DinputFile=`pwd`/p5.xml -DoutputFile=`pwd`/Guidelines.epub -Dcoverimage=`pwd`/Utilities/cover.jpg BUILD SUCCESSFUL Total time: 1 minute 24 seconds java -jar Utilities/epubcheck3.jar Guidelines.epub Epubcheck Version 3.0.1 Validating against EPUB version 3.0 No errors or warnings detected. check if XeLaTeX exist /usr/bin/xelatex perl -p -e \ "s+http://www.tei-c.org/release/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…;> \ s+/usr/share/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…;"> \ Utilities/guidelines-latex.xsl > Utilities/guidelines.xsl BUILD: build Lite version of Guidelines, then LaTeX version of Guidelines from Lite, then run to PDF using XeLaTeX Make sure you have Junicode, Arphic and Mincho fonts installed ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/ws/P5/../../../S…> -DXELATEX=xelatex pdfonce [echo] make LaTeX and PDF BUILD SUCCESSFUL Total time: 1 minute 40 seconds Build step 'Console output (build log) parsing' changed build result to FAILURE Not sending mail to unregistered user elli_mylonas(a)brown.edu

1 1