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

Mr. Jenkins is ignoring me
by Bauman, Syd 10 Feb '21

10 Feb '21

Attn: Peter & Martin I committed to dev branch at 20:50:00 localtime (± 6 sec), commit #9d8122417ee2ec8d05f979bf920f98069586817a. That was over 2 hours ago, and yet neither Jenkins[1] seems to have noticed. Worse, one of them seems to have kicked off a build at roughly halfway between then and now, but it does not list my commit as its reason for existing. Snif! What is going on? — Syd “I’ve been ghosted by a CI server!” Bauman [1] https://jenkins.tei-c.org/view/TEI%20dev/ https://jenkins2.tei-c.org/view/Dev%20branch%20jobs/

2 1

Re: [Tei-council] Next Stylesheets meeting
by BERMUDEZ SABEL Helena 09 Feb '21

09 Feb '21

Hello! No issues with the proposed date. Best, H. Helena Bermúdez Sabel Chercheuse FNS senior Institut des sciences du langage Université de Neuchâtel ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: 08 February 2021 18:08:07 To: tei-council(a)lists.tei-c.org; Martin Holmes; Nicholas Cole Subject: [Tei-council] Next Stylesheets meeting Dear all, The next Stylesheets meeting is scheduled for February 25, the day of our release. I propose to postpone the meeting to March 4. Please let me know if this works for you. Best, Martina

6 5

PDF build with Japanese
by Martin Holmes 08 Feb '21

08 Feb '21

Hi all, The ruby stuff is now merged into the repo, and I've spent a good few hours now trying to get the PDF to build properly. It dies with this error: ! LaTeX3 Error: The key 'fontspec-opentype/...' is unknown and is being (LaTeX3) ignored. which is something to do with xml:lang='ja' appearing in the source. At one point I got it to build, but without the Japanese language attributes, the characters just come out as square boxes. Can anyone who knows more about LaTeX than me suggest anything? I don't really want to go round removing xml:lang attributes just to get past the PDF problem, but I don't know what else to do at this point. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

4 8

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

08 Feb '21

Dear all, This is the preliminary agenda for our next Council call on February 11 at 11am-12:30pm PST/2pm-3:30pm EST/7pm-8:30pm GMT/8pm-9:30pm CET: https://docs.google.com/document/d/1mnUQtzMFTpPfUwoBQX2yo4g_sWeBrHBG4Z2myRK… The zoom link is in the google doc. Best, Martina

2 1

Next Stylesheets meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Feb '21

08 Feb '21

Dear all, The next Stylesheets meeting is scheduled for February 25, the day of our release. I propose to postpone the meeting to March 4. Please let me know if this works for you. Best, Martina

1 0

Refrigeration
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Feb '21

08 Feb '21

Dear all, We are close to refrigeration, starting on Friday, February 12. After this date we should not commit major changes to the schema. Minor changes like improvements in wording, correction of typos etc. are fine. Please have a look at the open milestone 4.2.0 Guidelines issues (https://github.com/TEIC/TEI/issues?q=is%3Aissue+milestone%3A%22Guidelines+4…) and 7.51.0 Stylesheets issues https://github.com/TEIC/Stylesheets/issues?q=is%3Aopen+is%3Aissue+milestone…. Please remove issues that you will not tackle before the next release. Best, Martina

1 0

positioning of examples vis-a-vis prose
by Bauman, Syd 08 Feb '21

08 Feb '21

Working on ruby glosses, I think it is quite useful to say in the prose of CO things like “the following example” or “the example above”. I note that the “Examples” subsection of the “Style Notes” section of TCW 20<https://teic.github.io/TCW/tcw20.html> (why don’t these <div>s have IDs?) says in the very first paragraph not to do that. However, it is clear to me that the rest of that paragraph is about examples in tagdocs, not examples in the prose of the Guidelines. Furthermore, I think the logic (someone might come along later and add an example) at best does not really apply here in the prose (where being able to differentiate examples is useful), and at worst is basically silly. (I very vaguely remember the argument in favor of this restriction, and begrudgingly agreeing to it; but I cannot find the reasoning that led me to that agreement now, nor can I recall if it was intended for only tagdocs or for examples in the prose, too :-) That said, why don’t we have a mechanism for referring to specific examples?

4 3

Re: [Tei-council] More NVDL issues: Spec files not validating
by Bauman, Syd 05 Feb '21

05 Feb '21

Trying to validate which schema file against which schema? ________________________________ Just trying to validate the schema itself in oXygen.

3 10

Thanks for Ruby feedback
by Martin Holmes 04 Feb '21

04 Feb '21

Hi all, Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this: Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4. Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.) Create subsections: 3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this. 3.4.2 "Ruby Annotations" containing the new prose already proposed. 3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms. I'm doing this work in a separate branch: <https://github.com/TEIC/TEI/tree/issue-2054-ruby> which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done. The time is relatively short, but I think we can get there before the freeze. I'll post the meat of this on the ticket too, for the record. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

3 10

More NVDL issues: Spec files not validating
by Martin Holmes 03 Feb '21

03 Feb '21

Hi all, Our Spec files (P5/Source/Specs/*.xml) all link to the NVDL schema here: <http://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rele…> That generates an error in itself, because the Jenkins server gives a 308 Permanent Redirect to https. But if you do retrieve the schema and try to validate with it in Oxygen, you get (or at least, I get) the error: IllegalStateException - getSchemaProperties requires a schema I'm not sure why that is -- anybody know? It makes it a bit difficult to work on Spec files. What are people doing to validate their Spec files at the moment? Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

4 3