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

Meeting times: Council and Stylesheets call
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Jun '21

19 Jun '21

Dear all, at our last Council meeting we agreed that we want to start with our monthly Council and Stylesheet call 30 minutes earlier. I hope this is also fine for the Council members who were not present at this meeting, and for Martin and Nicholas who regularly attend the Stylesheets meeting. This means that we start at: 10:30am PDT, 1:30pm EDT, 6:30 BST, 7:30pm CEST. Our next Stylesheets call is on Thursday, June 24. Best, Martina

2 1

renamed Jenkins repo branch to main
by Peter Stadler 15 Jun '21

15 Jun '21

Dear all, just a quick note that I changed the branch name from master to main in the Jenkins repo [1]. Additionally, I merged the current dev branch into the (new) main branch since this branch was not building anymore due to an outdated Debian package. housekeeperly greetings Peter [1] https://github.com/TEIC/Jenkins

1 0

handling multiple slots of different durations of service
by Bauman, Syd 14 Jun '21

14 Jun '21

[For Janelle our Nominations Committee representative] Problem: There are 6 positions open on Council, 4 of which are for 3-year terms (the usual), and 2 of which are for 1-year terms (due to recent by-law change). Possible solutions, from the idiotic to the clever (but not necessarily in that order here) include: 1. Elect 6 people, randomly assign who gets 1- and who gets 3-year terms. 2. Hold separate elections in OpaVote (or whatever) as if they were entirely different positions. 3. Just elect 6 people, let Council decide which ones serve for how long. 4. Just elect 6 people, let them fight it out among themselves. 5. Elect 6 people, let them each blindly choose 1- or 3-year term based on ranking 6. Elect 6 people, let them each choose 1- or 3- year term based on ranking in discussion with each other. Since #5 and #6 are my suggestions, I will detail them a bit, below. Worth noting, though, that although #2 has the huge advantage that a nominee could decide in advance that she wants to stand for only 1 year, it simultaneously has the disadvantage that each nominee has to decide in advance how many years he wants to run for, and he might win or lose depending on who else decides to go for that number of years. More importantly, perhaps, running a separate election would likely be a big pain for those running the elections. Because we are using an instant run-off election or ranked-choice voting system, whoever is running the election knows who among the 6 people elected got the most votes, the 2nd most votes, etc. (Even if that information is not shared with the electorate.) Thus for suggestions #5 the highest ranked Councilor-elect gets to choose whether she wants one of the two 1-year or one of the four 3-year terms. Then the 2nd highest is asked if he wants the one remaining 1-year or one of the four remaining 3-year terms OR if he wants one of the two remaining 1-year or four remaining 3-year terms. If any 1-year terms remain, the third ranking is asked to choose. And so on, until there is no longer any choice (because only one term length remains available). In suggestion #5, each Councilor-elect is queried in private (probably via e-mail or phone call) in rank order. Suggestion #6 is the same, but to ask the question of each in order with all 6 of them in the same (virtual) room, so haggling can take place. (So someone who really only wants to commit to 1 year can maybe convince someone higher in the rankings who doesn’t care …)

3 2

Reminder: meeting start in 90 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Jun '21

10 Jun '21

Dear all, please have a look at the agenda for our meeting at 10am-11:30pm PDT/1pm-2:30pm EDT/6pm-7:30pm BST/7pm-8:30pm CEST - which is one hour earlier than usual: https://docs.google.com/document/d/1THZdj_acrUBpBejrs7MJA7eTtDtHGTZqAEa-T8i… Best, Martina

1 0

Tomorrow's meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Jun '21

09 Jun '21

Dear all, For those who didn't see the poll on slack about the meeting times tomorrow: Would it be possible for you to start the meeting an hour earlier (at 10am PDT / 1pm EDT / 6pm BST / 7pm CEST) so that Elisa and Janelle can join the whole meeting? Best, Martina

1 0

Next Council call: June 10
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jun '21

08 Jun '21

Dear all, This is the agenda for our next Council call on Thursday, June 10 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1THZdj_acrUBpBejrs7MJA7eTtDtHGTZqAEa-T8i… Since we could not agree on a new date that suits everyone, we will stick with Thursday for the time being. Best, Martina

2 2

Stylesheets meeting?
by Bauman, Syd 27 May '21

27 May '21

Martina — I forgot ask in last e-mail that you let us know where the Stylesheets meeting will take place. If I don't hear from you in ~2 mins (here or Slack), I will post a personal Zoom meeting invitation here.

4 4

Meeting in ~46.3 hours
by Bauman, Syd 27 May '21

27 May '21

We are scheduled for a Stylesheets meeting this coming Thu 27 May, 18:00/19:30Z. That means starting at * 11:00 PDT, * 14:00 EDT, * 19:00 BST, & * 20:00 CEST, and scheduled to run for 1½ hours. Agenda items I would like to cover, other suggestions welcome: * (~4 min) Quick review of P5subset updating plans * (~4 min) report on progress on automation thereof (PS) * (~4 min) Quick report on #496<https://github.com/TEIC/Stylesheets/pull/496> progress (either MH or NC) * (~1 hour) Ticket #327 <https://github.com/TEIC/Stylesheets/pull/327>

2 1

Stylesheets meeting: May 27
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 May '21

25 May '21

Dear all, This is the zoom link for our meeting on Thursday, May 27 at 11 am PDT / 2 pm EDT / 7 pm BST / 8 pm CEST: https://zoom.us/j/94174447570?pwd=eGJmNXdkYlZsVWhSMHdNVmdONjZyQT09 And here is a blank google doc to which Syd will hopefully add some exciting issues. https://docs.google.com/document/d/1wbrqKTXN3_8cw4VCmn3rEJicu6SnwiDBcKWpwS9… Best, Martina

1 0

xmllint issues
by BERMUDEZ SABEL Helena 23 May '21

23 May '21

Hi all, At the last Stylesheets meeting, we checked how the command "xmllint --format -" that is run when testing the HTML transformations adds the XML declaration to the output file (which was a bit counterproductive because the XSLT code was explicitly demanding the omission of the declaration). Now I’ve run into another problem that is also generated due to the xmllint command: it outputs XML entities when a literal string is expected. I run the script without xmllint and the output is the expected one so it seems that it is another of the modifications done by this program. This issue primarily affects the quotation marks that are added in the HTML output using CSS. See diff: 17c16 < content:"‘"; --- > content:"‘"; 20c19 < content:"’"; --- > content:"’"; 23c22 < content:"“"; --- > content:"“"; 26c25 < content:"“"; My guess is that this wasn’t an issue before because xmllint had as an input a file with the XML declaration. Now it finds a file whose first line is the HTML doctype declaration and thus adds these modifications. Considering that in the HTML transformation Saxon already has the command to indent the results, my proposal is to modify Test/Makefile and delete the "xmllint" command ONLY for the transformations to HTML. Would this be a viable solution? Best, H. Helena Bermúdez Sabel Chercheuse FNS senior Institut des sciences du langage Université de Neuchâtel

3 4