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-framewor... (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@newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: tei-council-bounces@lists.tei-c.org on behalf of Peter Stadler Sent: 13 May 2018 20:35:17 To: tei-council@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-in..., so this is merely to confirm the wrong URL. Best Peter

Am 11.05.2018 um 22:39 schrieb Elisa Beshero-Bondar :

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@pitt.edu Development site: http://newtfire.org -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived