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

Issue Assignments
by Hugh Cayless 09 Aug '16

09 Aug '16

Hi all, I've gone through and assigned all of the unassigned issues (except for a couple of red ones). Your task is to at least investigate enough to form an opinion and make a comment on each ticket recommending a course of action. If there's a consensus in the comments, you can turn it green and do it, or if you can't do it yourself, hand it over to someone who can. Kevin has asked that we freeze posting in the CMS until it has been migrated, so I'm behind on posting the minutes with no way to catch up. I'm thinking I may just start a "documentation" repo and put both the minutes and the TCW docs there. I don't really like having documentation in the TEI repo, as updating the docs really shouldn't trigger a Jenkins build. We talked about this a bit at the last F2F iirc, but I don't remember if we reached a consensus on it. All the best, Hugh

3 8

Question for Mac Users
by Lou Burnard 03 Aug '16

03 Aug '16

A Mac user of my acquaintance is trying to use the TEI Stylesheet library command teitoslides, which converts TEI XML to LaTeX and then to PDF. He seems to have hit a problem that I don't know how to solve, namely that the Minion and MyriadPro fonts which the Stylesheets expect to be available by default, are not. On my Ubuntu system, I just grab a copy of the opentype fonts and put them in the right place in /usr/share/fonts/ and Everything Just Works. But I haven't the faintest idea how to do the equivalent, if there is one, on a Mac. Has anyone tried this? If you've ever tried to build the Guidelines PDF you must have hit the same problem, I think, since they expect you to have these fonts too. Any advice gratefully received

3 4

Re: [tei-council] Simple : victory declared, going home.
by Lou Burnard 29 Jul '16

29 Jul '16

Hi Martin Thanks for your quick reaction. I hope you'll find time to re-read and nitpick the text of the document in the near future: there are undoubtedly passages that need some further work. Just a few comments on your more general comments below: On 29/07/16 14:53, Martin Mueller wrote: > > From the perspective of the newcomer it may be confusing that there is > something called TEI Lite and TEI Simple. The newcomer, however, may not > discover either because on the TEI Web site they are squirreled away under > the subheading "Customization." That's a fair point, which I hope the designers of the new Website will take on board. In French, rather than "customization", we tend to say "personnalisation" which sounds more, um, personal. But clearly the website ought to alert the first time reader to the fact that (a) the DTD is not a single monolithic entity (b) amongst its many incarnations, Simple is a good starting point for a range of applications. > > Assuming newcomers discover both Lite and Simple they may ask "Which > should I use?" Indeed. They may also ask wonder whether maybe TEI_bare would be suitable. Or Epidoc, or any of a number of other possibilities. > And if they look at the documentation they may be confused > by the fact that, leaving aside the Processing Model, the documentation > for the two customizations is virtually the same. Much of it is the same. But there is also quite a lot that's different. Lite represents the state of the TEI of about 10 years ago, when we deliberately decided not to adapt it further, but move it to a "bugfix only" state of support. Simple has some (though not all) of what we've learned in the last decade. > So for most practical purposes TEI Simple is TEI Lite with a Processing > Model, a few elements removed on the basis of usage figure, and a few > elements added. I think that's an oversimplification. There are a few policy-like decisions reflected in Simple which are not in Lite: e.g. use of @ref rather than @key, use of @rendition rather than @rend. > From which I draw the conclusion that Lite and Simple should be merged, > given a name that more accurately describes what either of them can do, > and put very prominently as the recommended point of entry into the TEI > world. I couldn't agree less. They are different documents, representing a consensus as to what's a useful minimal subset at different times in different situations. You could argue that Simple should *replace* Lite possibly, but "merging" makes no sense at all. > > I have spent a fair amount of time with versions of the Best Practices in > Libraries document.By far the most important section of that document has > always been "Level 4". Much can be said in favour of merging Level 4 with > that general introduction. Time and energy are in short supply, and > maintaining one entry-level version with really good documentation is a > lot better than sort of supporting three. Besides, "TEI in Libraries" is a > very different thing from what it was twenty years ago. The modal library > TEI project may no longer be something like "Wright American fiction." > It's more likely to be some project where a faculty member or student goes > to the Library for some help because the Library is the go to place for DH > stuff. That's the case at Northwestern, and it's the case in many other > places. I have no views on BPL. Though it would obviously be nice to know what that group thinks of Simple's header section.

1 0

Agenda for Friday
by Hugh Cayless 29 Jul '16

29 Jul '16

Hi All, Here's the draft agenda for our meeting on the 29th at 09:00 EST / 14:00 BST / 15:00 CEST: https://docs.google.com/document/d/1_wHUlbsZSOEeeGDXqHR3gnp9c4LILL-hlpy8DXK… As always, please add any items you want to discuss.

2 2

f2f council logistics
by Stefan Majewski 29 Jul '16

29 Jul '16

Hi, just returned from a fortnight of cycling through Europe. Offline. I noticed that people started discussing where to stay. Unfortunately, accomodation in Vienna is well booked as there are floods of tourists through all seasons and hotels for this reason usually don't give special deals (at least not without prepayment, which most institutions cannot do). Something from 80 to 120 EUR a night is quite normal for accommodation in a rather central location. Public transport is very efficient, though. I would try to get something in walking distance to the venue. The closest and still rather inexpensive choice is Hotel Post [1] (2 available)(646EUR/7Nights), there is a Pension Dr. Greissler very close that looks nice and is also close to the venue. I do not have experience with them but the have a good deal today on booking.com [2] 665EUR/7Nights. And there are some others not far that look quite good [3]. We have a room from Sunday to Wednesday morning. Sunday will be a smaller room, where we most likely will have to arrange for food and coffee on our own. I hope that we can coordinate with the workshops and other activites Mo-Tue for catering (CC@tei2016 for that purpose) cheers, Stefan [1] http://www.booking.com/hotel/at/post-wien.de.html?aid=304142;label=gen173nr… [2] http://www.booking.com/hotel/at/pension-dr-geissler.de.html?aid=304142;labe… [3] http://www.booking.com/hotel/at/parkview-residences.de.html?aid=304142;labe… I filtered by up to 150 EUR and vienna city centre, hope this is somewhat persistent. Everything within the inner ring-like central street should be roughtly walking distance. The conference venue is in the north-western quarter of the ring: http://www.booking.com/searchresults.de.html?aid=304142&label=gen173nr-1DCA…

2 1

simple : attribute classes and valLists
by Lou Burnard 28 Jul '16

28 Jul '16

Today I have been mostly looking at attribute classes and valLists 1. deleted att.declaring (not much point in keeping it, since att.declarable is already gone) 2. Simplified att.editLike by - deleting @evidence and @instant - deleting @precision from att.dimension - deleting att.ranging I wrote a stylesheet to re-insert valLists supplied by the ODD into the body of the text (there are about five of them). In the process I noticed that one of my favourite examples is no longer viable. It starts like this: On those remote pages it is written that animals are divided into <list rendition="#runOn"> <item n="a">those that belong to the Emperor,</item> <item n="b"> embalmed ones, </item> <item n="c"> those that are trained, </item> <item n="d"> suckling pigs, </item> ... There is no simple:runOn rendition defined anywhere, so that @rendition value is dead in the water. And maybe it should be a @type="runOn" anyway. What do you suggest? At this late stage, despite the pain, I am tending to think I may have to sacrifice the whole example.

1 0

Build failed in Jenkins: TEIP5-Documentation-dev #2196
by Victoria TEI Jenkins 25 Jul '16

25 Jul '16

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation-dev/2196/changes> Changes: [martindholmes] Trying to fix a third unwrapped example causing horizontal scrolling, ------------------------------------------ Started by upstream project "TEIP5-Test-dev" build number 2914 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 -c core.askpass=true 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 1b9514167249dddc0fb478af41c76edcbf6918c7 (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f 1b9514167249dddc0fb478af41c76edcbf6918c7 > git rev-list e079d7e2ec3f504d5900b527769307177c49cb80 # timeout=10 [workspace] $ /bin/bash -xe /tmp/hudson1628410566021146508.sh + svn update Skipped '.' Summary of conflicts: Skipped paths: 1 [workspace] $ /bin/bash -xe /tmp/hudson1230391083340030462.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: 42 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 -s http://www.tei-c.org/index.xml | sed 's/content="text\/html"/content="text\/html; charset=utf-8"/' | xmllint --html --noent --dropdtd --xmlout - > Utilities/teic-index.xml;fi -:9: HTML parser error : Unexpected end tag : p Reason: Error reading from remote server ^ 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: 53 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: 56 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 19 seconds Build step 'Console output (build log) parsing' changed build result to FAILURE

1 1

Re: [tei-council] Simple : facsimile
by James Cummings 25 Jul '16

25 Jul '16

That is how I would have suggested doing it. So works for me. James -- Dr James Cummings, Academic IT Services, University of Oxford On 23 Jul 2016 09:09, Lou Burnard <lou.burnard(a)retired.ox.ac.uk> wrote: Also, having looked more closely, it seems that if you want to encode page openings, you're probably better off encoding the opening as a single surface and each page as zone within it, since you can't define a coordinate system for a pageGrp. So, pending further clarification of this issue, surfaceGrp is OUT. On 22/07/16 20:48, Lou Burnard wrote: > In general, I am all in favour of reducing complexity in Simple, as I > hope is by now evident. But I seriously do think we should include > surfaceGrp, because the distinction between a single page (a surface) > and a page opening (a surfaceGrp containing two surfaces) is a crucial > one for many people. But I can survive being outvoted! > > > On 22/07/16 20:43, Scholger, Martina (martina.scholger(a)uni-graz.at) > wrote: >> +1 >> >> Best, Martina >> >> -----Ursprüngliche Nachricht----- >> Von: tei-council-bounces(a)lists.tei-c.org >> [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von James >> Cummings >> Gesendet: Donnerstag, 21. Juli 2016 19:35 >> An: tei-council(a)lists.tei-c.org >> Betreff: Re: [tei-council] Simple : facsimile >> >> >> Sure, I agree. Just suggesting that if you are grouping surfaces and >> such then you are starting to leave the realm of Simple and should >> maybe do your own customisation. ;-) >> >> -James >> >> On 21/07/16 18:34, Lou Burnard wrote: >>> Just to repeat, what I said below, surfaceGrp is nothing to do with >>> sourceDoc. It's for grouping surfaces such as page openings, or faces >>> of a monument. >>> >>> >>> On 21/07/16 19:29, James Cummings wrote: >>>> I'm understanding this discussion correctly (and I've just skimmed it >>>> in a hurry), then I would be saying that we want facsimile, surface, >>>> zone, and graphic, but don't want surfaceGrp, line or sourceDoc. >>>> >>>> i.e. we want to be able to do TEI Simple facsimiles as long as they >>>> are basic, but not sourceDoc non-interpretative transcriptions. If >>>> you need surfaceGrp or sourceDoc, in my mind what you are doing isn't >>>> Simple. ;-) >>>> >>>> >>>> -James >>>> >>>> >>>> On 21/07/16 17:42, Lou Burnard wrote: >>>>> >>>>> On 21/07/16 15:50, Scholger, Martina >>>>> (martina.scholger(a)uni-graz.at) wrote: >>>>>> I think that <surfaceGrp> goes beyond a Simple document, therefore >>>>>> I would remove it. >>>>> Well, my reasoning is that whether or not you're doing transcription >>>>> you will definitely want some way of distinguishing between single >>>>> page images and images of a page opening, which is precisely ewhat >>>>> surfaceGrp is for, imho. >>>>> >>>>>> Concerning the <line>: If I understand it correctly, <sourceDoc> is >>>>>> not provided within a Simple document? >>>>> Krekt >>>>> >>>>>> Is it meant to have a transcription within <facsimile> instead? >>>>>> I don't think that <facsimile> should contain a transcription (see >>>>>> also line 790-793 in tei_simple.odd: "A more powerful approach, >>>>>> discussed in section <ptr target="#simple-facs"/> below, is to use >>>>>> the <gi>facsimile</gi> element to define the organization of the >>>>>> set of images representing the text, and then use >>>>>> the <att>facs</att> attribute to point to individual components of >>>>>> that representation.") >>>>> Agreed, that putting transcription inside <zone> seems a bit >>>>> (ahem) odd, but you still need to ability to identify zones on an >>>>> image, whether or not you put text inside them, and the content >>>>> model for <zone> allows text. >>>>> Are you are saying that it should actually be forbidden if the >>>>> ancestor of <zone> is a <facsimile> rather than a <sourceDoc>? >>>>>> Therefore I wouldn't restore <line>. >>>>> Understood. >>>>>> >>>>>> -----Ursprüngliche Nachricht----- >>>>>> Von: tei-council-bounces(a)lists.tei-c.org >>>>>> [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Lou >>>>>> Burnard >>>>>> Gesendet: Donnerstag, 21. Juli 2016 13:42 >>>>>> An: tei-council(a)lists.tei-c.org; Martin Mueller >>>>>> Betreff: [tei-council] Simple : facsimile >>>>>> >>>>>> The schema currently makes available within <facsimile> : >>>>>> surface, surfaceGrp, and zone, but not line. >>>>>> >>>>>> Is that balance about right? Should I restore <line> (which is >>>>>> sugar for <zone type="line">) ? Should I remove <surfaceGrp>? >>>>>> >>>>>> The purpose is to support a Simple document which contains just >>>>>> images and the lightest of transcriptions, such as you might get >>>>>> from a crowd sourcing transcription experiment for example, not to >>>>>> do full blown genetic transcriptions, obvs. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> 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 >>>> >> >> -- >> Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, >> University of Oxford >> -- >> 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 > -- 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

3 2

Simple : facsimile
by Lou Burnard 23 Jul '16

23 Jul '16

The schema currently makes available within <facsimile> : surface, surfaceGrp, and zone, but not line. Is that balance about right? Should I restore <line> (which is sugar for <zone type="line">) ? Should I remove <surfaceGrp>? The purpose is to support a Simple document which contains just images and the lightest of transcriptions, such as you might get from a crowd sourcing transcription experiment for example, not to do full blown genetic transcriptions, obvs.

3 8

July meeting poll
by Hugh Cayless 21 Jul '16

21 Jul '16

Please fill in your availability at: https://doodle.com/poll/m79mta983dd32ree Thanks, Hugh Sent from my phone.

4 6