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@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> on behalf of Syd Bauman <s.bauman@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%2FTEIC%2FTEI%2Fblob%2Fdev%2FP5%2FMakefile%23L271-L273&amp;data=02%7C01%7Cs.bauman%40northeastern.edu%7C035059cec2ad4ab3393108d682f6ad86%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C636840393325625275&amp;sdata=V7cSHZP5v5Rnsu8EBaFBNBh%2FdUxUfsBNTpb0kCeBExg%3D&amp;reserved=0

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@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council