Re: [Tei-council] first draft release notes
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@newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Scholger, Martina (martina.scholger@uni-graz.at) <martina.scholger@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@newcastle.ac.uk> Gesendet: Donnerstag, 24. Januar 2019 18:07 An: Scholger, Martina (martina.scholger@uni-graz.at) <martina.scholger@uni-graz.at>; TEI Council <tei-council@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@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@lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> on behalf of Scholger, Martina (martina.scholger@uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger@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
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.
James (or anyone else) -- What Makefile and what ant script? I've whipped up a possible fix for to.xsl, but don't know how to test it off top of my head. BTW, can't get version from http://www.tei-c.org/Vault/P5/current/doc/tei-p5-doc/VERSION, as that's the current release, not the new one we want the 'readme' to point at, right?
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:
participants (2)
-
James Cummings -
Syd Bauman