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

Stylesheets meeting Tue 06 Oct
by Syd Bauman 09 Oct '20

09 Oct '20

We have a Stylesheets meeting planned for Tue 06 Oct at 13:00Z; that's * 06:00 PDT * 09:00 EDT * 14:00 BST * 15:00 CEST Unless we get off our collective rear ends and do so before then, I'm thinking perhaps we should perform the release of 7.50.1 during the meeting. This is at the moment a tiny bug fix which waiting for someone other than its authors (me & Martin) to either approve and release or at least approve for release. One question this immediately raises, of course, is how do we do just a Stylesheets release? (I don't know -- I bet no one knows for sure, but I hope some of you have a good idea. :-) If folks don't like that idea, please let me know ASAP so I can have something else lined up.

5 8

Reminder: VF2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 29 Sep '20

29 Sep '20

Dear all, This is a reminder that our next virtual F2F meeting will take place from 24 to 26 October. Please add topics that we need to address during the meeting: https://docs.google.com/document/d/1nIk4x5SDB0_EqSJG-DynzLz-n9WbmR0tjzM7Aax… Best, Martina

2 1

new Stylesheets release needed
by Syd Bauman 24 Sep '20

24 Sep '20

With Martin's help, I have just fixed an egregious error in Stylesheets/bin/transformtei, which is a bad problem, but was an easy fix. (The problem was that it would always fail to find the default p5subset.xml if you started from a directory outside the Stylesheets/ tree.) I have pushed the change to the 'dev' branch. But this is a serious enough problem that the fix should be release, in Martin's humble opinion. (Mine, too.) We probably don't want to release the _other_ changes that have been made to dev since the last release. (At least, Martin doesn't. I kinda like them. :-) So we think the steps should be to cherry-pick that particular fix into the release branch. 1. git checkout released 2. git cherry-pick c615d52 3. change VERSION to 7.50.1 4. run tests, pray there are no errors 5. git commit # to get the new VERSION file 6. git push 7. Hope Stylesheets released branch build works on Jenkins 8. Read TCW 22 and figure out how to actually release the new package. 9. Read TCW 22 and figure out how to release the new oXygen package (may need to kick Jenkins to get it to build, but at least on Martin's Jenkins it should go on its own after the TEIP5-relased job completes successfully) 10. Update TCW 22 as needed to cover this process. (We don't think there has been a separate Stylesheets release for a long time.)

5 6

ISO liaison
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Sep '20

23 Sep '20

Dear all, Kathryn forwarded me some documents on Guidance for ISO liaisons. Please find them here: https://drive.google.com/drive/folders/10diuYAlKE_yYf_KwaGKiUGoHYXZZ2cf1?us… Best, Martina

1 0

Next meeting: September 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Sep '20

08 Sep '20

Dear all, This is the agenda for our meeting on Tuesday, September 8 at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30: https://docs.google.com/document/d/1gRTkIgQe7WCKSXSjgGcpFsrwHDKiwB8jhczLaRO… If you find time, please have a look at the proposal on encoding ruby glosses. Best, Martina

1 1

not so-called
by Syd Bauman 07 Sep '20

07 Sep '20

In P5/Source/Guidelines/en/ND-NamesDates.xml in the 1st paragraph of section NDORG the (organization) names “Harvard College”, “the BBC”, “Apple”, “Google”, “the Scythians”, and “the Militant Tendency” appear. They are encoded as <soCalled>. I am not sure what they should be encoded as (<mentioned> jumps to mind), but, except perhaps for the last, they are *not* so-called. Any thoughts?

2 1

Fwd: [oXygen-user] [Ann] New Oxygen add-on to help translators
by Lou Burnard 03 Sep '20

03 Sep '20

Reluctantly using Outlook for Android<https://aka.ms/ghei36> ________________________________ From: oXygen-user <oxygen-user-bounces(a)oxygenxml.com> on behalf of Radu Coravu <radu_coravu(a)sync.ro> Sent: Thursday, September 3, 2020 8:44:57 AM To: oxygen-user(a)oxygenxml.com <oxygen-user(a)oxygenxml.com> Subject: [oXygen-user] [Ann] New Oxygen add-on to help translators Hi everyone, Over the course of this summer one of our interns, Mircea Badoi, worked on a free Oxygen XML add-on designed to help translating XML content. Starting from yesterday, the add-on is available for Oxygen vesions 21.1 or newer in our default add-on repository. If you want to install it, you can use the Oxygen main menu "Help->Install new add-ons", choose the default Oxygen add-on update site and you will find an add-on named "Translator Helper (Experimental)" in the list. The add-on has two main features: 1. You can translate content using Google Translate to various languages: * Select the content to translate in the Author visual editing mode. You can also select the entire document contents. DITA topics are small so you can select the entire topic contents. * Right click. Select "Google Translate into" and choose the target language. * Copy the translated content from the opened web page. * Click Replace in the Oxygen Translate using Google Translate dialog that showed up. The original content should now be replaced with the translated content, the original element structure and attributes should remain unchanged. * In addition you can choose to show the original document content in the Translator Helper side view. This will allow you to correct the translation further by looking at the original text and the translated text side by side. 2. You can see the original content side by side with the content that you are translating, so you can translate correctly and easy by right clicking in the Author visual editing mode and invoking the Show current content in side view action. So I hope you will enjoy the add-on, if you have questions or improvement requests, they are as usual welcomed. One area in which the plugin may be useful is for example if you want to quickly demo to a customer how a topic written in English would look like in other languages like Japanese Chinese, French, German, Russian, etc. Regards, Radu Radu Coravu Oxygen XML Editor

1 0

Stylesheets meeting tomorrow
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 Sep '20

01 Sep '20

Dear all, This is the Zoom-Link for our Stylesheets Meeting tomorrow: https://us02web.zoom.us/j/88599847406?pwd=WGZJUkQ4RGhYQXplcnNyc1RWQU4xdz09 Best, Martina

4 3

Stylesheets meeting in < 12 hours
by Syd Bauman 31 Aug '20

31 Aug '20

Thank you, Martina, for the reminder. For some reason I had thought Council meeting was tomorrow, Stylesheets the week after. We will meet (without Raff -- snif!) at 13:00Z. That's: * 06:00 PDT * 09:00 EDT * 14:00 BST * 15:00 CEST Martina has set up a Zoom meeting space for us. (See [1], below for the URL.) Possible topics, in no intelligent order, include: a) Overview of new Makefile in Test/ b) Changes to Test2/, if there were any interesting changes to Test2/. c) New P5/Utilities/subset.xsl -- How often do you get to use "shallow-skip"? d) Ticket #237 -- I do not think there is any chance of solving it in 1 meeting (even if we did nothing else), but it is an interesting one and we might make some good progress in understanding exactly what is happening and why. e) Ticket #370 -- We made progress previously, and could push forward on this. f) Ticket #454 -- if anyone else has something to contribute. I put an *awful* lot of work into this just before release, and was not able to solve it. I barely remember anything about it at all now, a sign that it is gnarly enough my brain wanted to leave it behind. g) Ticket #449 -- The code that needs to be tweaked is shellscript, not XSLT, but I am not opposed to working on this if people want. h) Ticket #447 -- Perhaps we can at least figure out where that space is coming from. below ----- [1] https://us02web.zoom.us/j/88599847406?pwd=WGZJUkQ4RGhYQXplcnNyc1RWQU4xdz09

2 1

proposal for encoding ruby glosses
by Scholger, Martina (martina.scholger＠uni-graz.at) 28 Aug '20

28 Aug '20

Dear all, I'd like to share with you the proposal from Kiyonori Nagasaki and his colleagues from the East Asian / Japanese SIG on encoding ruby glosses in TEI https://docs.google.com/document/d/1rRgBRYpxUlsnMEHbOPW-92u_AIMNwq9axGtpI1U… Please have a look at it. Best, Martina

1 0

oXygen TEI plugin and debian packages
by Scholger, Martina (martina.scholger＠uni-graz.at) 21 Aug '20

21 Aug '20

Dear TEI Community, The oXygen TEI plugin has been updated with the latest version of the TEI Guidelines 4.1.0 and Stylesheets 7.50.0. A description on "How to automatically update your TEI framework in oXygen" can be found here: https://github.com/TEIC/oxygen-tei/blob/master/oxygen-tei-plugin.md Furthermore, the Debian packages are available at https://packages.tei-c.org/deb/. Best, Martina Martina Scholger Centre for Information Modeling Austrian Centre for Digital Humanities University of Graz A-8010 Graz | Elisabethstraße 59/III +43 316 380 2291 martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> | http://gams.uni-graz.at<http://gams.uni-graz.at/> Chair of the TEI Technical Council | http://www.tei-c.org/ Institut für Dokumentologie und Editorik e.V. | https://www.i-d-e.de/

1 0

No masters
by Hugh Cayless 20 Aug '20

20 Aug '20

Hi All, I have deleted the master branches for TEI and Stylesheets, and plan to gradually work through the remainder. My inclination on most of them is probably to wait until there's an automated migration tool, as I understand pull requests may break, etc. Hugh

2 2

Release 4.1.0 complete
by Hugh Cayless 19 Aug '20

19 Aug '20

Dear All, especially Martina who can now announce it, We (Jessica, Nick, and I) have completed the release. You are free to commit to dev again. Thanks to all who dropped in on Slack to help out. The only remaining bits are the Oxygen plugin, which I can't build, and the Debian packages, because I was a bad release technician and forgot to ask Peter for the passphrase. All the best, Hugh

4 7

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

19 Aug '20

Dear release technicians, here is a document were you can take notes during the release (in case this is necessary). It also contains the email to the TEI-L https://docs.google.com/document/d/1PJryKNeKIzUEpdFlaQaJAhO9F3XM23IU66lB3QR… Best, Martina

2 1

release notes
by Syd Bauman 19 Aug '20

19 Aug '20

I updated the release notes *in the release-4.1.0 branch* (because that's what Martina did). While there are always improvements to be made, I think they are mostly good to go. Still need a release code name (why do we have those -- they are fun for us, but since we do not actually use them ...?). And I think we should consider deleting the prhase "to represent primary source materials" from the 1st bullet point.

2 1

Deb build warning
by Martin Holmes 17 Aug '20

17 Aug '20

Hi all, I'm still getting this warning on the release branch of the Stylesheets: dh_clean: warning: Compatibility levels before 9 are deprecated (level 5 in use) Didn't we decide to push that compat value up to 9? Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

1 0

Release branches
by Hugh Cayless 17 Aug '20

17 Aug '20

Dear All, I've created release branches "release-4.1.0" for the Guidelines, and "release-7.50.0" for the Stylesheets. All the best, Hugh

3 3

Annotations and impasses
by Hugh Cayless 17 Aug '20

17 Aug '20

Hi All, Since we essentially have today to make the go/no-go decision for getting Annotations into this release. We seem to be deadlocked in a couple of ways, and I would like to see if we can un-jam things. Syd and I are arguing over whether annotations should look like: <annotation xml:id="anno9" target="http://example.org/image1 http://example.org/image2"> <respStmt xml:id="HAC"> <resp>creator</resp> <persName>Hugh Cayless</persName> </respStmt> <ptr target="http://example.org/description1"/> <note>tag1</note> </annotation> or <annotation xml:id="anno9" target="http://example.org/image1 http://example.org/image2"> <annMeta> <respStmt xml:id="SB"> <resp>creator</resp> <persName>Syd Bauman</persName> </respStmt> </annMeta> <annBody> <ptr target="http://example.org/description1"/> <note>tag1</note> </annBody> </annotation> Syd's argument (and you should correct me if I'm misrepresenting your opinion, Syd) is that it's cleaner to partition things this way and we might want in the future to say virtually any TEI element could be an annotation body. My counter to this is that we set out here to implement the Web Annotation Data Model (or parts of it at least) in TEI, and that WADM doesn't have extra containers for annotation metadata or bodies. Further, WADM doesn't do specialized body types. They have text and they have URIs. I'm certainly in favor of adding useful features to TEI annotations, but if we want to do that in the next round of work on annotations, we'll have to do it by adding new TEI functionality (probably via new elements), and I don't think partitioning the content of annotation will buy us anything. It might make it worse, because the extra-sparkly new TEI functionality won't be compatible with WADM:body and therefore probably shouldn't go in an <annBody> element. To compound this, Laurent seems to say that WADM was only ever meant to be an inspiration and actual interoperability with Web Annotation wasn't a goal they had in mind in requesting this feature. I'm just going to go cry for a bit...excuse me. Ok. I will sum up: I would really like to have WADM compatibility this year because I have things I want to do with it. My proposal is that we proceed with WADM-compatible annotations and then begin work on more powerful TEI annotations. I would like to keep the content model of <annotation> as simple and as close to WADM as possible, but I won't pout if I'm voted down on that. What do you all think? Hugh

7 12

Freeze
by Scholger, Martina (martina.scholger＠uni-graz.at) 16 Aug '20

16 Aug '20

Dear all, I would like to remind you that we had agreed to freeze starting tonight. Please keep that in mind and check with the release technicians in case of late changes. Best, Martina Von meinem Huawei-Mobiltelefon gesendet

2 1

Stylesheets 454 and thus TEI 1848
by Syd Bauman 16 Aug '20

16 Aug '20

I have put multiple days of debugging work into Stylesheets 454, the release-blocking error that means a <classRef>, or at least a <classRef> with an @except, is ignored when processing an ODD. While I have made serious progress (some of which is in the sydb-454 branch), it is looking like I will not have a viable solution by the end of the day. Thus I think we need an alternate solution, which would be to back out [1] and either leave title page stuff out of <lem> and <rdg> for this release, or use some other ODD mechanism to put them in there. Possibilities (listed in my order of preference) include: 1. Use a bunch of <elementRef>s 2. Use <classRef> w/o @except, and add a <constraint> to flag <binaryObject>, <graphic>, and <castList> as invalid 3. Make a new class "model.frontPart.apparatusable" and put the needed elements in it. 4. Use <classRef> w/ @include (but I am highly suspicious that this will fail in exactly the same way). We can change any of the above back to <classRef> w/ @except after 454 is fixed. The other possibility, of course, is that someone else will take a look at this and fix the bug in the next few hours. If anyone wants to join my for a screen-sharing debugging session, speak up. That said, I really have other things I need to do today, too. :-| Notes ----- [1] TEI repo commit 193e6283321aeeb68b9a93b0d95b10a82148ef74

1 0

OxGarage release
by Peter Stadler 13 Aug '20

13 Aug '20

Hi all, the last release of OxGarage was done in June 2019 and since then not much development has happened, yet there are some minor changes that IMHO qualify for a new release. Most of all, the current master branch won’t build anymore on Travis nor on DockerHub – which is already fixed in dev. While at it, I already created a new main branch to eventually replace master starting with this release. (As a side note, Hugh was right about GitHub providing tools for doing this change later this year, see https://github.com/github/renaming#later-this-year. So I won’t touch other repos …) So, my proposal is to release OxGarage v3.1.0 next week and take care of the branch name switch with this release. If I hear no objections, I will take this as silent consent and do so :) Best Peter

1 1

REGENERATING, NOT!
by Syd Bauman 11 Aug '20

11 Aug '20

Re: Stylesheets meeting further info BTW, passing REGENERATING=1 to the Stylesheets/Test/Makefile tells the Makefile to not bother doing all those `diff` commands, but it does NOT actually regenerate the expected_results/. I.e., it just generates the output files (like test15.odd.rnc), but does not move them into expected_results/. One would have to do that by hand. (I think this was a purposeful change by Martin or someone just to avoid clobbering all the expected_results/.) Moreover, back on 2020-03-18 Martin commented out the diffs of test21.rnc, test30.rnc, and test30.dtd. I think we should probably put those back, yes, Martin?

3 2

Slightly Updated: Steps for updating p5subset.xml in Stylesheets repo
by Martin Holmes 11 Aug '20

11 Aug '20

This is an outline of the process we designed for updating the local copy of p5subset.xml in the Stylesheets. The rationale for this process is that changes to P5 inevitably require changes to the Stylesheets, but it makes more sense to deal with those required changes in batches, periodically, rather than making every change to P5 trigger frantic work on the Stylesheets (which the P5 ticket implementer may not be able to undertake at the time). The Stylesheets Group should probably undertake this work, and it must happen in a timely manner before any release. This is how it goes: 1. Retrieve a fresh copy of p5subset.xml, built using the current dev branch of P5. 2. In the Stylesheets, switch to the dev branch and git pull. Switch to the subsetSetup branch, which is intended for this work, and git pull. 3. Merge any changes from the Stylesheets dev branch into the subsetSetup branch. 4. Replace the source/p5subset.xml in the subsetSetup branch with the fresh one. 5. Run the Stylesheets tests (Test and Test2) in the subsetSetup branch. 6. Fix any problems. At this point, if there are problems too difficult to fix in the time you have available, abandon the process and put in a ticket for the Stylesheets repo. If the error is serious, make it a release-blocking bug. 7. Commit changes to subsetSetup branch. git push. 8. Switch back to the dev branch, git pull, and merge changes from the subsetSetup branch. git push. 9. Watch Mr Jenkins to make sure all is well. -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

2 2

Fwd: Steps for updating p5subset.xml in Stylesheets repo
by Martin Holmes 11 Aug '20

11 Aug '20

-------- Forwarded Message -------- Subject: Steps for updating p5subset.xml in Stylesheets repo Date: Fri, 7 Aug 2020 08:41:32 -0700 From: Martin Holmes <mholmes(a)uvic.ca> To: Syd Bauman <s.bauman(a)neu.edu> CC: Martin Holmes <mholmes(a)uvic.ca> This is an outline of the process we designed for updating the local copy of p5subset.xml in the Stylesheets. The rationale for this process is that changes to P5 inevitably require changes to the Stylesheets, but it makes more sense to deal with those required changes in batches, periodically, rather than making every change to P5 trigger frantic work on the Stylesheets (which the P5 ticket implementer may not be able to undertake at the time). The Stylesheets Group should probably undertake this work, and it must happen in a timely manner before any release. This is how it goes: 1. Retrieve a fresh copy of p5subset.xml, built using the current dev branch of P5. 2. In the Stylesheets, switch to the dev branch and git pull. Switch to the subsetSetup branch, which is intended for this work, and git pull. 3. Merge any changes from the Stylesheets dev branch into the subsetSetup branch. 4. Replace the p5subset.xml in the subsetSetup branch with the fresh one. 5. Run the Stylesheets tests (Test and Test2) in the subsetSetup branch. 6. Fix any problems. 7. Commit changes to subsetSetup branch. git push. 8. Switch back to the dev branch, git pull, and merge changes. git push. 9. Watch Mr Jenkins to make sure all is well. -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

1 0

Stylesheets meeting Tue 11 Aug
by Syd Bauman 11 Aug '20

11 Aug '20

Time to get our heads spinning 'round circularity! We are planning a Stylesheets group meeting for this Tue 11 Aug at 13:00Z.[1] This is an important meeting, because we are going to step through the process of updating the p5subset.xml that the various build processes are using; i.e., we are implementing (for the first time) our planned "fix" for the circularity problem. (Not really so much a fix as a work-around, IMHO.) I expect we will be using Google Hangouts unless someone says otherwise. Notes ----- [1] 13:00 UTC is: 06:00 PDT 09:00 EDT 14:00 BST 15:00 CEST

3 2