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

monthly call: new meeting times
by Scholger, Martina (martina.scholger＠uni-graz.at) 18 Dec '20

18 Dec '20

Dear all, We have a decision for the new meeting times for the monthly Council call in 2021. The meeting will be held every second Thursday of the month from 11am-12:30pm PST/2pm-3:30pm EST/8pm-9:30pm CET. The first meeting will be on Thursday, January 14. Please check the Google calendar for the meeting times (Janelle and Helena - you should have access to the calendar). As always I will send the agenda and the zoom link a few days in advance. Best, Martina

2 1

ticket assignments and mentors
by Bauman, Syd 15 Dec '20

15 Dec '20

[Janelle and Helena — every month 1 person from Council is the “ticket triage” person. This person pays attention to new or otherwise unassigned tickets (actually called “issues”) on GitHub, and assigns them to one or more Council members; might also assign labels and milestone to each. This month I am the ticket triager.] IIRC at our last meeting we did not decide on mentors for our new members, instead deferring that decision to January. Does that mean I should not assign tickets to Janelle and Helena, either? My instinct is that I should go ahead and assign tickets to our new members now (so as to avoid forgetting or having unassigned tickets; besides, one of them requires a native Spanish speaker :-), with the understanding that until they have each gone through some orientation with their mentor next month, there is no expectation of actually tackling the tickets yet. As soon as they are ready, the tickets would be waiting for them, though. Any objections?

4 4

new meeting times
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Dec '20

09 Dec '20

Dear all, I've set up a doodle to coordinate the meeting times for the monthly Council meetings in 2021. I suggest to stick with the second week of each month (2nd Mon/2nd Tue etc.). In the doodle I have put in the January dates as an example. Please fill in the doodle by 2020-12-14: https://doodle.com/poll/486ypeh2nkzgtp9v?utm_source=poll&utm_medium=link Best, Martina

1 0

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

04 Dec '20

Dear all, This is the agenda for our next meeting on Tuesday, Dec 8 at 6:00-7:30 PST, EST 09:00-10:30, GMT 14:00-15:30, CET 15:00-16:30: https://docs.google.com/document/d/1sToQJklZ9ZdXSE5nMXpxN9P1yZho9IVYvXW--u1… Please find the zoom link in the google doc. Best, Martina

1 0

virtual short F2F meeting January/February
by Scholger, Martina (martina.scholger＠uni-graz.at) 04 Dec '20

04 Dec '20

Dear Council, During the three days virtual F2F meeting in October we agreed on a VSF2F (virtual short face-to-face meeting) in late January or early February: * US/CA meet Friday afternoon / evening (~3 hours) * Europeans meet Saturday morning (~3 hours) * Council convenes as a whole on Saturday (morning for US/CA, afternoon for Europeans) (~4 hours) Please fill in the doodle: https://doodle.com/poll/8958wr5fqecfqxne?utm_source=poll&utm_medium=link For our new members: In addition to the monthly meetings we have in person meetings twice a year for three days (one in spring and one before or after the TEI Conference). This year we had two very successful meetings, but it is not possible to meet online for full three days, also because of the time difference. Since we do not expect in person meetings in 2021 (at least not in the first half of the year) we agreed to hold an additional meeting in January/February. Best, Martina

1 0

Stylesheets meeting addendum
by Bauman, Syd 03 Dec '20

03 Dec '20

Attn: Meaghan Brown, Martin Holmes, Martina Scholger, Elisa Beshero-Bondar, and Raff Viglianti Please see 2nd page of today’s notes<https://docs.google.com/document/d/11aTpKoEaXfYuHTbtCd7Vh6rxdeM-QVxcCp8Ej7V…>; if in a rush skip down to last section, “Current State of Play”.

4 7

Stylesheets meeting, Tue 01 Dec
by Bauman, Syd 01 Dec '20

01 Dec '20

We are scheduled to hold a Stylesheets meeting this coming Tue 01 Dec 20, 14:00Z, which is: * 06:00 PST (Victoria) * 09:00 EST (New York) * 14:00 GMT (London) * 15:00 CET (Berlin) I do not know on which platform we will meet, or who will be hosting. (I suppose as chair of this group I am supposed to figure that out, but so far y’all have pretty cleverly kept me out of the communication technology end of things.) Is Google Hangouts still viable? Anyway, topics include (but are not limited to): * ticket #471<https://github.com/TEIC/Stylesheets/issues/471>: Add permalink for examples * language processing; see https://wiki.tei-c.org/index.php?title=Mapping_language_processing * and, if we have ample time left over, we could re-tackle ticket #399<https://github.com/TEIC/Stylesheets/issues/399>: <code> in <desc> gets dropped in rng

4 3

run XSLT 1 from ant?
by Bauman, Syd 29 Nov '20

29 Nov '20

How do we run XSLT 1 from ant? (In particular, from P5/antbuilder.xml. I tried "trax", but get a fatal “XSLT 1.0 compatibility mode is not available in this configuration”.)

3 5

Welcome to our new members!
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Nov '20

23 Nov '20

Dear all, Welcome to our new Council members Helena and Janelle! Our webmaster Luis Meneses added you to the Council's and Board-Council's mailing lists to give you an opportunity to keep up to date with what is going on before your term starts officially in January. You should also have received an invitation for the Google Drive folder "TEI-Technical-Council" were we collect our meeting minutes, the GitHub repository, the shared Google calendar, and the Slack channel. New Council members will be assigned a mentor to help you get started. If you have any questions please do not hesitate to contact me. 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

Meeting in 30 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Nov '20

10 Nov '20

Hi all, our call starts in 30 minutes: https://docs.google.com/document/d/1P-DFu-mPB9Xhva2Up2oXTG7HY55l-QgR6zOZLKU… Best, Martina

1 0

Next Council meeting: Nov 10
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Nov '20

09 Nov '20

Dear all, This is the agenda for our meeting tomorrow at EST 09:00, GMT 14:00, CET 15:00 https://docs.google.com/document/d/1P-DFu-mPB9Xhva2Up2oXTG7HY55l-QgR6zOZLKU… The zoom is linked in the google doc. Best, Martina

1 0

Evaluating the "Copia" version of the Guidelines
by Elisa Beshero-Bondar 04 Nov '20

04 Nov '20

Dear Council, After I had to exit early from this morning's Stylesheets meeting I was eager to see how Syd's "Copia" output of the Guidelines turned out. (For those who missed it, Syd found a quick way to output the Guidelines in a way that would prevent suppression of examples in other languages, and this seems mainly to affect the way the Guidelines Spec pages turn out (not the Guidelines chapter examples). I saw in the minutes that we're asked to review Syd's interesting output, named "Copia" (for more copious examples) and report back to the Council list. So started exploring element spec pages a little this evening. Here's what I'm finding: The bibl element is much improved by the Copia output: the examples are far more diverse, but not bewildering in number. I think it is fascinating to see non-English variety: - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-bibl.… - Current: https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-bibl.html The byline element is similarly a lot more interesting now: - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-bylin… - Current: https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-byline.html The gap element seems similarly improved, though there's a little problem here: - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-gap.h… - Current: https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html What I noticed right away was, the number of examples did not seem overwhelming, and the variety of languages evident before you had to click "Show All" reflects a good diversity with Asian languages rising to the fore. However(!) the duplicate example jumps out--duplicates in English. Turns out the French exemplum is identical to the English here, and I"m not really sure why. I think I've seen that in other specs as well. Meanwhile, the element p looks a bit more interesting now, and I think it improves on the current output: - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-p.html - Current: https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-p.html How about ab? Completely boring: no change at all, and it's sadly evident that we don't have enough examples in the first place. (If that isn't a ticket yet, it should be!) - Copia: https://bauman.zapto.org/~syd/temp/4TEICouncil/html_GLs_all_eg_en/ref-ab.ht… - Current: https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-ab.html Okay-that's a start: a review of 5 out of 582 element specs (less than one percent...sigh). But so far I like the Copia version for what it illuminates about our range of exempla, both where it is diverse and where it is lacking. Looking forward to hearing what others think! Elisa -- Elisa Beshero-Bondar, PhD Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

5 6

Stylesheets meeting Tue 03 Nov 20
by Bauman, Syd 01 Nov '20

01 Nov '20

We are scheduled to hold a Stylesheets meeting this coming Tue 03 Nov 22. Note the time may be different due to recent DST shift in north America: * 06:00 PST * 09:00 EST * 14:00 GMT (and UTC) * 15:00 CET The topic is pre-ordained from the VF2F Council meeting. The goal is to generate a version of the Stylesheets (in a branch, of course) that puts all examples in every language into the Guidelines outputs. Our fearless leader has prepared a GoogleDoc for us, which has the notes from the VF2F and can be used to take notes during the Stylesheets meeting.[1] Is Hangouts still OK for everyone? Note [1] https://docs.google.com/document/d/1uk_6CtLQIM9lrLPDWcFni48sfTqc9CtSk6SWcXl… [https://lh5.googleusercontent.com/oSVfkHOctyKLYcUfUFycQIkOu3kes8AUpXkCTuzR1…]<https://docs.google.com/document/d/1uk_6CtLQIM9lrLPDWcFni48sfTqc9CtSk6SWcXl…> 2020-11-03_StylesheetsGroup<https://docs.google.com/document/d/1uk_6CtLQIM9lrLPDWcFni48sfTqc9CtSk6SWcXl…> Stylesheets 2020-11-03 https://github.com/TEIC/TEI/issues/1934 Subgroup suggests this ticket for consideration by i18N SIG. 2020-10-24: HC: examples are on the agenda for future discussion of i8N group. RV: What would we be asking i18n? Shouldn't Council be doing the mechanism of this work... docs.google.com

1 0

TEI Customizations ODD issues?
by Hugh Cayless 29 Oct '20

29 Oct '20

Hi All, I guess this question is mostly for Syd, but since the customizations ODD is an exemplar, we're all kind of responsible for it. If I have bug reports, should I make GitHub issues for them? Issues I've run into: 1) @role="nonfatal" I think is not understood as a warning, and gets you the usual red underline/error presentation. I feel like warn and/or info might be better. Oxygen's supported role levels seem to be: "warn" or "warning" "error" "fatal" "info" or "information" 2) default values for required attributes are flagged. I can sort of see the logic there, but they're not *really* the same thing. 3) non-"tei:" schemes in @source are discouraged, but what if your source isn't a TEI release? I've got a couple of these, and I'd like to be able to put a URI in there without being yelled at. Hugh

2 2

VF2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Oct '20

23 Oct '20

Dear Council, our VF2F meeting starts tomorrow at 9 EDT, 14 BST, 15 CEST Please find the agenda here: https://docs.google.com/document/d/1nIk4x5SDB0_EqSJG-DynzLz-n9WbmR0tjzM7Aax… Best, Martina

1 0

VF2F -- time change in Europe
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Oct '20

19 Oct '20

Dear all, I noticed today that Europe switches to standard time from Saturday to Sunday. Please find the updated meeting times (in red) in the google doc. I hope that one hour lunch break on Sunday is enough before we start with the full Council session. https://docs.google.com/document/d/1nIk4x5SDB0_EqSJG-DynzLz-n9WbmR0tjzM7Aax… Best, Martina

1 0

Stylesheets 7.50.1
by Syd Bauman 16 Oct '20

16 Oct '20

This morning Martin & I released Stylesheets 7.50.1 on GitHub, Sourcefoge, and as the Debian packages. We did not release a new oXygen plug-in, as the bug that was fixed was part of the commandline `transformtei` script, which oXygen does not use to run the stylesheets. We (actually, Martin gets the credit) realized that our previous concern about the `tei-install.sh` program with respect to the oXygen plug-in was incorrect, so closed that ticket. Worth noting it took us nearly an hour, even though we had all the pieces ready to rock-and-roll. If we were doing this every week, it could be done a whole lot faster. But infamiliarity and insecurity makes it a slow process. Martin -- are there any updates we would recommend to TCW 22?

3 2

Meeting, Oct 13
by Scholger, Martina (martina.scholger＠uni-graz.at) 12 Oct '20

12 Oct '20

Dear all, This is the agenda for our meeting tomorrow, October 13 at EST 09:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30´ https://docs.google.com/document/d/1F2hc2cVyS2UzxSILqrRtMnTQuy1DH18bTdJv6mz… Please do also have a look at the reminder section. The zoom link is in the google doc. Best, Martina

1 0

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