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

WG: A new tool for the TEI!
by Scholger, Martina (martina.scholger＠uni-graz.at) 29 Jun '20

29 Jun '20

Dear Council, Marjorie Burghart and Conal Tuohy have released their TEI plugin for the open source editor in jEdit. They would like to invite us for testing the tool and sending them feedback. Please see Marjorie’s email with all the details below. Best, Martina Von: Marjorie Burghart <marjorie.burghart(a)gmail.com> Gesendet: Montag, 22. Juni 2020 16:51 An: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at>; James Cummings <James.Cummings(a)newcastle.ac.uk>; louburnard <lou.burnard(a)gmail.com> Cc: Conal Tuohy <conal.tuohy(a)gmail.com> Betreff: A new tool for the TEI! Dear Martina, Lou, Hugh and James, Conal and I are very pleased to let you know that a TEI plugin for the open source editor jEdit has been officially released: http://plugins.jedit.org/plugins/?TEI The plugin is slowly propagating through the mirrors of jEdit's Plugin Central, if you don't see it there yet it should appear shortly. Before making an official announcement, we would appreciate getting feedback from "power users" of the TEI :) We thought of you (and through Martina, of all Council members). If you have the time to give it a try, we would very much appreciate your feedback on potential bugs, ergonomy issues, etc. Conal thinks those first bugs could be fixed in a new release in a couple of weeks. Conal is hosting the source code on his github, where you could report issues: https://github.com/Conal-Tuohy/jEdit-TEIPlugin/issues and he has created a wiki page: https://github.com/Conal-Tuohy/jEdit-TEIPlugin/wiki How to proceed: - Install the latest version of jEdit http://www.jedit.org/ - Through the plugin manager (Plugins > Plugin Manager...), search the "TEI" plugin and install it with all its dependencies NOTA BENE: if you already had jEdit with the XML plugin installed, you will also need to update the XML plugin to the latest version. What it does: well, not everything :) The aim is NOT to replace Oxygen entirely, but to offer the community a viable free alternative, especially for teaching workshops and users with basic needs. We tried to cover the needs listed here (basic, and even some some deemed superfluous) : https://wiki.tei-c.org/index.php?title=Editor_for_teaching_TEI_-_features Conal is currently working on two other improvements: - schematron support - a mechanism akin to Oxygen's validation scenarios. The plugin has been developed by Conal, and the first steps in its development funded by a small grant I obtained from DARIAH - but Conal has done much more work "pro bono", and is kindly continuing development to enhance the features. If the community sees some use in this first step, I am planning to do my best to get further developments funded. Best wishes, Marjorie

1 0

circular build headache suggestion
by Syd Bauman 16 Jun '20

16 Jun '20

The circularity of the P5 and Stylesheets builds depending on each other has bitten us once again. (Ouch!) We have a situation now where the Stylesheets tests can succeed only against either the release branch of P5 or the dev branch of P5, but not both simultaneously. This sucks. Right now Stylesheets dev branch is successfully building against P5 release[1], but failing against P5 dev branch[2]. We believe that the reverse would make a lot more sense. While it is desirable that it build against both branches, it is frequently impossible. So we have to pick one, and we (Martin & Syd) think we should pick them as follows: * P5 release branch should be built with the P5 release Stylesheets * P5 dev branch should be built with the P5 dev Stylesheets * Stylesheets release should be built against P5 release branch * Stylesheets dev should be built against P5 release dev as a general rule. This means we would have to always release a new Stylesheets the same day we release P5 every time. It also means that if we ever had a reason we needed to do an interim release of either, we would have to fight with the circularity problem (probably by trying to make sure both branches work against each other, or temporarily suppressing some finicky tests). But the advantage is that "normal" releases and updates would work properly. So what we would like to do is: * Update Stylesheets deb branch tests so that they work against P5 deb (which will break them against P5 release branch) * Have Peter & Martin agree on a consistent set of explicit job names in Jenkins that perform the 4 builds listed above. Notes ----- [1] E.g. on jenkins.tei-c job "Stylesheets-dev" and jenkins2.tei-c job "Stylesheets-dev-against-P5-release". [2] E.g. on jenkins.tei-c job "Stylesheets-dev-against-TEIP5-dev" and jenkins2.tei-c job "Stylesheets-dev-against-TEIP5-dev".

3 8

off topic: new ODD based non-TEI schema
by Peter Stadler 16 Jun '20

16 Jun '20

Dear all, here I want to bring to your attention a project of a colleague called "Music Performance Markup" (MPM): https://axelberndt.github.io/MPM/ I want to share this with you because it’s a great example of an ODD based non-TEI schema, and it features a nice rendering of the documentation. If we ever wanted to redesign our Spec pages, this might give us some ideas :) Have fun Peter

1 0

Another thought on <annotation>
by Hugh Cayless 12 Jun '20

12 Jun '20

Had a bit of a brainstorm this morning, and I came up with another idea re representing WADM annotations. See #9 at https://docs.google.com/document/d/15lPVs89ehDNpQQ3Qf79kfRAECSN-MT_SpBlQpHU…. I'd be grateful for your opinions. Hugh

1 0

Progress on labeling tickets
by Martin Holmes 11 Jun '20

11 Jun '20

Hi all, Today Elisa and I added all the labels we think appropriate for all tickets starting at the oldest and running up to #319. That seems to be half of the tickets, so we think our work is done. A few tickets got closed in the process. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

1 0

housekeeping: delete stale branches
by Peter Stadler 10 Jun '20

10 Jun '20

Dear all, here’s yet another(?) proposal for housekeeping: Both Stylesheets and Guidelines repo feature various stale branches which I would like to get rid off [1,2]. Some of those are prefixed with a Councilists name so I encourage everyone to look through his/her branches and eventually delete outdated/unused/forgotten branches. Some of the stale branches are even just behind dev without featuring any commits *ahead* of dev (e.g. the TEI/help branch). I think those can safely be removed and would do so in the next days if no one objects. This does include release branches which I’d also like to get rid of because IMHO they do not serve any purpose anymore (the important information is kept in the tags). Best Peter [1] https://github.com/TEIC/Stylesheets/branches/stale [2] https://github.com/TEIC/TEI/branches/stale [3] https://github.com/TEIC/TEI/tree/help

3 3

call in 10 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Jun '20

09 Jun '20

Dear all, Our call starts in 10 minutes: https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w… Best, Martina

1 0

Reminder: Council meeting tomorrow
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jun '20

08 Jun '20

Dear all, This is a reminder that our next Council meeting is tomorrow, June 9 at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30 Please find the agenda here and add topics that we should discuss https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w…<https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w…> You can find the zoom link for the meeting in the google doc. Best, Martina

1 0

Next Council meeting: Tuesday, June 9
by Scholger, Martina (martina.scholger＠uni-graz.at) 05 Jun '20

05 Jun '20

Dear all, Our next Council meeting is on Tuesday, June 9 at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30 Please find the agenda here and add topics that we should discuss https://docs.google.com/document/d/1MK5fPZS0sHMJ1HMumwU6YpqH6JKgMRhB72lv38w… You can find the zoom link for the meeting in the google doc. Best, Martina

1 0

P5/Utilities-1 and P5/Utilities
by Peter Stadler 04 Jun '20

04 Jun '20

Dear all, while working on some old TEI->LaTeX->PDF issues I stumbled (once again) across those two folders P5/Utilities-1 and P5/Utilities in the Guidelines repo. Can somebody shed some light on the difference of these folders? I’m especially interested in the file guidelines-latex.xsl which exists in both directories but only the one in Utilities seems to be used for building the PDF version of the Guidelines? Many thanks Peter

2 2