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

OxGarage and Roma updated
by Peter Stadler 31 Jan '19

31 Jan '19

Dear all, I just had an excellent admin session with Christof Schöch (many thanks!) and we managed to restart the Roma and OxGarage services. Both should now run with the current Stylesheets and TEI sources. So, OxGarage, Roma, and the Debian packages should be updated to the current release (please test!), let alone the Oxygen plugin still needs some attention. Best Peter

2 1

Updating Roma
by Hugh Cayless 30 Jan '19

30 Jan '19

Hi Ian, We're working on completing the latest TEI release. Can you update the Roma Docker container? Thanks, Hugh

3 3

Hands off the release branches
by Hugh Cayless 29 Jan '19

29 Jan '19

Hi All, we're in the process of releasing 3.5.0, so please do not push anything to either the Guidelines or Stylesheets release branches! Thanks, Hugh and Elli

2 2

release minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 29 Jan '19

29 Jan '19

Dear all, in case we need to take some notes during the release process, here is a document. It also contains the draft of the email for the TEI-L. https://docs.google.com/document/d/1fTrCQrC8tRTZWLGScXKb0R_brwhOoRA6uta4c1h… Martina

1 0

release branch
by Mylonas, Elli 29 Jan '19

29 Jan '19

Dear TEI Council: I am about to create the release branch for the release that Syd suggests several code names. I am unilaterally selecting the name "Raven" because Providence has a strong Edgar Allan Poe connection. Please do not commit any further changes, unless they are to the release notes or unless you communicate first with the release technicians or the chair. Release technicians are Hugh Cayless and myself. Thank you! --elli

6 14

Release Branch for release "The Raven" has been created
by Mylonas, Elli 25 Jan '19

25 Jan '19

Jenkins Maintainers please add built of the release branch "release-3.5.0" Thank you! --elli

1 0

Re: [Tei-council] first draft release notes
by James Cummings 25 Jan '19

25 Jan '19

Re: html:* passthrough. Sure, but I know SPQR used it for things locally in Oxford as well. But you could probably remove without side-effect. I doubt many other people are using them. (Though, how would we know?) re: highlighting github lines in a link. Cool isn't it. ;-) It is the way we should talk about code when discussing where some error is, by URI that references the lines (of a particular revision even better for historical completeness) Re: nuking ref I'm assuming you mean only the ones wrapped around gi? As there are some (pointing to things like classes etc) that we do need, obviously. Let me know if I can help, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu> Sent: 25 January 2019 19:45:16 To: TEI Council Subject: Re: [Tei-council] first draft release notes > That is the standard way that those profiles work, ... Yes, indeed. I was just listing 'em as that's the set of files I looked through. > The HTML is just a pass through for those doing readme files that > have some html embedded. Ummm ... OK. But of the 35 readme-*.xml files we have in P5/RelaseNotes/, not one has a single non-TEI element. > The makefile I was referring to was the P5 one at: > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com… Wow. Thanks. (Not so much for the Makefile pointer, but for the cool demo of highlighting lines in GitHub source!) > You are right that grabbing version is a problem, but you've > omitted the _real_ problem which is that xslt is run over every xml > file in the directory. So you can't pass it the current version. > Instead, you would need to get it from the filename itself. Oh, good point! > Note, if doing this that it would have to be > tei:gi[not(ancestor::tei:ref)] or something, right? (Since there > are readme files that already have the refs around them. ;-) Sure, but my plan was to just nuke those <ref> elements. (After all, there are only 35 files ...) > Just thinking out loud, Thanks for doing so. I will get on that v. important version number bit in a few mins. Also need to add code for <att> and <ident>, which also occur inside <ref> in our collection of readmes. _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

Re: [Tei-council] first draft release notes
by James Cummings 25 Jan '19

25 Jan '19

Hi Syd, That is the standard way that those profiles work, by importing html.xsl (which of course imports all the common and html xslt), isn't it? The HTML is just a pass through for those doing readme files that have some html embedded. The makefile I was referring to was the P5 one at: https://github.com/TEIC/TEI/blob/dev/P5/Makefile#L271-L273 But that was just how I was figured out which XSLT profile is being called for the release notes. You are right that grabbing version is a problem, but you've omitted the _real_ problem which is that xslt is run over every xml file in the directory. So you can't pass it the current version. Instead, you would need to get it from the filename itself. So we'd have to get it from the filename. We should be able to do something like: <xsl:variable name="filename" select="(tokenize($document-uri,'/'))[last()]"/> to get the filename and then remove the version number from that. Note, if doing this that it would have to be tei:gi[not(ancestor::tei:ref)] or something, right? (Since there are readme files that already have the refs around them. ;-) Just thinking out loud, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu> Sent: 25 January 2019 17:36:38 To: TEI Council Subject: Re: [Tei-council] first draft release notes Boy, I never looked at it before, but profiles/readme/html/to.xsl looks like a very weird animal. It has templates that match the HTML namespace and ones that match the TEI namespace. That file imports html/html.xsl, which itself imports: common/verbatim.xsl, html/html_param.xsl, and common/common.xsl, which itself imports: common/common_param.xsl, common/common_core.xsl, common/common_textstructure.xsl, common/common_header.xsl, common/common_linking.xsl, common/common_msdescription.xsl, common/common_figures.xsl, common/common_textcrit.xsl, common/common_gaiji.xsl, common/i18n.xsl, and common/functions.xsl I've just looked through all of those (quickly), and none seem to have a template that matches <gi> explicitly. So I think it's probably quite reasonable to just tuck it in here. How would the code in to.xsl get the version number (to point to the Vault)? A parameter? Read P5/VERSION (in which case it needs to be updated before this is run)? > Not sure it does work automatically, one would think that it would > follow the same thing that happens with the Guidelines but looking > back through some earlier ones I'm not sure it does. > > Looking at the makefile which calls the ant script, I think that > the release notes are generated using the 'readme' profile of the > stylesheets. So: > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com… > > If we put a template in to handle tei:gi in that stylesheet that > would probably do it. (Anyone else see a problem with that?) > > And yes, I think release notes should always point to the Vault of > that version of the the Guidelines because if they point to the > live site then by next version they might be out of date. _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

2 1

Re: [Tei-council] first draft release notes
by James Cummings 25 Jan '19

25 Jan '19

Hi Martina, Not sure it does work automatically, one would think that it would follow the same thing that happens with the Guidelines but looking back through some earlier ones I'm not sure it does. Looking at the makefile which calls the ant script, I think that the release notes are generated using the 'readme' profile of the stylesheets. So: https://github.com/TEIC/Stylesheets/blob/dev/profiles/readme/html/to.xsl If we put a template in to handle tei:gi in that stylesheet that would probably do it. (Anyone else see a problem with that?) And yes, I think release notes should always point to the Vault of that version of the the Guidelines because if they point to the live site then by next version they might be out of date. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: 24 January 2019 21:38:27 To: James Cummings; TEI Council Subject: AW: first draft release notes Hi James, That would be convenient! But I can’t find an example where this works – do you have one? I have seen that in some older versions the links point to the Vault. Should we change that? Best wishes, Martina Von: James Cummings <James.Cummings(a)newcastle.ac.uk> Gesendet: Donnerstag, 24. Januar 2019 18:07 An: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at>; TEI Council <tei-council(a)lists.tei-c.org> Betreff: Re: first draft release notes I notice in the Release Notes that we seem to be putting both <ref> and <gi> around element names? This only seems to have started in the last few releases where before we just put <gi> and the magic of the build process turned this into a link in the release notes. Can someone confirm/deny whether we need to do this or not? If we do it seems like we should change the script rather than the encoding. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>> Sent: 23 January 2019 23:41:16 To: TEI Council Subject: [Tei-council] first draft release notes Dear all, I made a first draft of the release notes: https://github.com/TEIC/TEI/blob/dev/P5/ReleaseNotes/readme-3.5.0.xml. There are still some TEI issues missing (from #1479 to #1645), which I will add tomorrow. For the Stylesheets release notes: should we add them to the same document? Martina

2 2

Re: [Tei-council] first draft release notes
by James Cummings 24 Jan '19

24 Jan '19

I notice in the Release Notes that we seem to be putting both <ref> and <gi> around element names? This only seems to have started in the last few releases where before we just put <gi> and the magic of the build process turned this into a link in the release notes. Can someone confirm/deny whether we need to do this or not? If we do it seems like we should change the script rather than the encoding. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: 23 January 2019 23:41:16 To: TEI Council Subject: [Tei-council] first draft release notes Dear all, I made a first draft of the release notes: https://github.com/TEIC/TEI/blob/dev/P5/ReleaseNotes/readme-3.5.0.xml. There are still some TEI issues missing (from #1479 to #1645), which I will add tomorrow. For the Stylesheets release notes: should we add them to the same document? Martina

2 1