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

Release timeline
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Jan '19

03 Jan '19

Dear Council, I hope you had some relaxing holidays and I wish you a happy new year! Thankfully, Elli and Hugh agreed to postpone the release date to January 29. This will give us a bit more time to finish some open issues. This is our suggested timeline: Refridge: Jan 17 (Thursday) - no major changes to the schema should be done after that; minor changes (wording, typos, examples, etc.) are fine. Freeze: Jan 23 (Wednesday) - no more changes can be done in the dev branch Create release branch: Jan 24 (Thursday) - after that, only minor changes (typos) can be done in the release branch Release: Jan 29 (Tuesday) I added the dates to the Google calendar. Our next Council call is between refridge and freeze, on January 18. Best wishes, Martina

1 0

starting rub-a-dub-dub
by Syd Bauman 03 Jan '19

03 Jan '19

Exactly 1 year to the day after abandoning the project, I am restarting it. Yay! New branch for this work will be called sydb-radd. First question: is there any difference between the 'master' and 'release-3.4.0' branches of TEI? Any significant difference? And, perhaps more importantly, how would I go about asking `git` that question? (Why, you ask? Because in order to test the Stylesheets they need to be building against some version of TEI P5. I'd like to use a local version so I don't have to wait the extra second or so it takes to download it every time I test the Stylesheets. Besides, it would be nice to know definitively which version I am testing against.)

1 0

Re: [Tei-council] rub-a-dub revisited
by James Cummings 30 Dec '18

30 Dec '18

With apologies to Syd, I've only got around to reading this now. It seems a good description to me. I'd add that before he stopped working on the Stylesheets Sebastian did recognise that although he'd moved it to be XSLT2 technically much of the way it worked was still with XSLT1 constructs. The one I discussed most with him was the interminable call-templates constructions that could be simplified significantly with functions. (And even where the same depths of constructs, it would be clearer.) Many thanks for all your hard work, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu> Sent: 24 December 2018 17:17:42 To: TEI Council Cc: Lou Burnard; Martin Holmes Subject: [Tei-council] rub-a-dub revisited Vanessa, and everyone -- I was tasked with writing up an explanation of the rub-a-dub revisited project, primarily for Vanessa, but for all, really. So here goes. background ---------- [Note -- this is intended to be a "get your head around this issue" sort of history, not a detailed highly accurate accounting. Lou and James probably know a lot more about the early history than I.] The TEI Consortium, through the TEI Council, maintains a set of stylesheets called (unimaginatively) "the stylesheets" or (not much better) "the TEI stylesheets". They were originally started (back in early 2000s?), I think, as two separate projects. The first was to have a workflow with which the TEI Guidelines, written in TEI/ODD, could be converted to HTML and print (PDF), and later ePUB, etc. The second was to provide a stylesheet for producing some semblance of readable output (HTML or PDF) from TEI Lite. It quickly became clear that these two projects had a *lot* in common, and so they were merged. And, in fact, the code base for TEI P4 and TEI P5 also had a lot in common, and they were merged, too. (We no longer support P4, though.) The main, almost sole, programmer behind this effort was the amazing Sebastian Rahtz. Sebastian was a brilliant, talented, and frighteningly fast XSLT programmer. An archaeologist by training, and an expert in the TeX and LaTeX typesetting systems, Sebastian never had any formal training in CS, at least none he would confess to me. Sebastian did not believe in internal documentation (e.g., comments) and did not care about indentation or consistency of namespace prefixes (the latter two, I suspect, because he was so brilliant he parsed XML on the fly in his head :-). He wrote these stylesheets over many years, adding features (often only a few hours after a request was made) in a somewhat willy-nilly fashion. Oh, and he started this project in XSLT1, converting to XSLT2 years later. situation --------- Due to brain cancer Sebastian stopped contributing to the stylesheets in late 2015 and died in early 2016. So now we (the Council) are left with a wonderfully powerful, modularized, parameterized, flexible set of stylesheets that are ridiculously difficult to maintain. Roughly 6 months after the gut-wrenching loss of our dear friend and colleague, the TEI Council established a group of interested parties to co-operatively educate ourselves as to how these stylesheets worked. All of TEI Council plus anyone who had ever contributed to the Stylesheets repo was invited. This group (chaired by me) has evolved from a self-education group to a Stylesheets-fixing group over time. The only people still on it are Martin Holmes, Lou Burnard, and various members of Council. One of the first things this group did was map out how the Stylesheets actually work. Some of that knowledge is represented in https://wiki.tei-c.org/index.php/Mapping_ODD_processing. desires ------- Martin and I have a (somewhat aspirational, but somewhat realistic) plan to re-write the ODD portion of the Stylesheets from scratch. That is, we would like to write a completely new code base (in XSLT 3.0) for processing the source of P5 into the P5 outputs (in PDF via XSLFO, as opposed to via LaTeX; HTML5; ePUB; etc.), and for processing customization ODDs into schemas and documentation. We do not want to rewrite the rest of the Stylesheets, i.e. those parts that transform generic TEI Lite into useful output, and do various other conversions. (These same stylesheets are the backbone of OxGarage.) However, that would take a long time, and in the meantime we still have a nearly unmaintainable mess. cleaning up -------- -- I have often been frustrated reading Sebastian's code. I am not nearly as brilliant as he was, so I like having helpful comments along the way, proper indentation, some consistent method of variable and function names, etc. I also find long-winded XSLT 1.0 constructs where a short bit of XSLT 2.0 can do the same thing quite frustrating. So every time I dive into the stylesheets, I think "this really has to be cleaned up". But usually I don't want to do any actual cleaning, in order to keep the delta between the code base before and after whatever fix I am applying as small as possible, to make it easier to double-check that it hasn't introduced new errors. There are some people a lot smarter than I who say that it is always better to clean up a code base than re-write it from scratch. One of them wrote a lovely blog post about it. See https://www.joelonsoftware.com/2002/01/23/rub-a-dub-dub/ While I am sure there are computer scientists who disagree, it is a quite compelling article. rub-a-dub 1 --------- - So I convinced Martin that we should take a crack at cleaning the Stylesheets first (it wasn't hard). I then convinced Council of the same thing (not much harder). In late 2017 Council explicitly charged me with performing a clean up operation (called "rub a dub" or "rub a dub dub" based on what Joel called it in his blog) on a single, large, part of the Stylesheets: the odd2odd program. I spent my winter break exactly a year ago working my tail off for hours on end cleaning up code in ways that should not change the output. Pretty much every time I saved the file, I kicked off a test process to make sure the output came out the same. And it did! Every time. It wasn't until I was well over halfway through rubbing and dubbing that I discovered that, due to a misunderstanding between me & Martin (no blame on Martin, I just mistook what he said), the test procedure I was using was not actually testing odd2odd! I had been comparing the wrong output files, so of course they were the same every time. Sigh. In fact, while I blissfully thought I was doing such a great job, I had in fact mucked up the output almost beyond recognition. Sigh. rub-a-dub 2 --------- - So Martin and I redoubled our efforts on getting ODD testing in the Test2 system to work properly, and are almost finished with that. (Martin presented the Test2 system at our last Stylesheets group meeting.) Once that is done (my current goal is before I leave for a conference in Texas on Wed 09 Jan), I will attack rub-a-dub of odd2odd again, probably shortly after I get back from Texas. The over-arching goal will be to end up with a version of odd2odd that does the same thing, but is *much* easier to maintain. Some of the ancillary files (like common_functions) will likely need to be changed somewhat, too. By "the same thing" I mean "have essentially the same XML tree as output". I don't care about the incidentals of serialization, and may well sprinkle the output with comments if it seems to help. The point is I intend to try to explicitly avoid "improving" the processor as I go along. The detailed tasks I expect to work on to make it more maintainable are somewhat flexible, likely to change as I go along. But the following are the kinds of things I mean: * Reasonable indentation * Adding internal documentation * Re-factoring XSLT 1.0 constructs into XSLT 2.0 * Collapsing equivalent functions, modes, and templates where appropriate. (There are several cases where the Stylesheets have 2 or even 3 versions of what appear to be almost the same function, mode, or template.) * Changing names of functions, modes, templates, and variables in order to approach consistency * Re-factor logic to avoid double negatives where reasonable This, of course, will all be carried out in a separate branch, so as not to interfere with normal bug-fixing and the late Jan release. _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

rub-a-dub revisited
by Syd Bauman 24 Dec '18

24 Dec '18

Vanessa, and everyone -- I was tasked with writing up an explanation of the rub-a-dub revisited project, primarily for Vanessa, but for all, really. So here goes. background ---------- [Note -- this is intended to be a "get your head around this issue" sort of history, not a detailed highly accurate accounting. Lou and James probably know a lot more about the early history than I.] The TEI Consortium, through the TEI Council, maintains a set of stylesheets called (unimaginatively) "the stylesheets" or (not much better) "the TEI stylesheets". They were originally started (back in early 2000s?), I think, as two separate projects. The first was to have a workflow with which the TEI Guidelines, written in TEI/ODD, could be converted to HTML and print (PDF), and later ePUB, etc. The second was to provide a stylesheet for producing some semblance of readable output (HTML or PDF) from TEI Lite. It quickly became clear that these two projects had a *lot* in common, and so they were merged. And, in fact, the code base for TEI P4 and TEI P5 also had a lot in common, and they were merged, too. (We no longer support P4, though.) The main, almost sole, programmer behind this effort was the amazing Sebastian Rahtz. Sebastian was a brilliant, talented, and frighteningly fast XSLT programmer. An archaeologist by training, and an expert in the TeX and LaTeX typesetting systems, Sebastian never had any formal training in CS, at least none he would confess to me. Sebastian did not believe in internal documentation (e.g., comments) and did not care about indentation or consistency of namespace prefixes (the latter two, I suspect, because he was so brilliant he parsed XML on the fly in his head :-). He wrote these stylesheets over many years, adding features (often only a few hours after a request was made) in a somewhat willy-nilly fashion. Oh, and he started this project in XSLT1, converting to XSLT2 years later. situation --------- Due to brain cancer Sebastian stopped contributing to the stylesheets in late 2015 and died in early 2016. So now we (the Council) are left with a wonderfully powerful, modularized, parameterized, flexible set of stylesheets that are ridiculously difficult to maintain. Roughly 6 months after the gut-wrenching loss of our dear friend and colleague, the TEI Council established a group of interested parties to co-operatively educate ourselves as to how these stylesheets worked. All of TEI Council plus anyone who had ever contributed to the Stylesheets repo was invited. This group (chaired by me) has evolved from a self-education group to a Stylesheets-fixing group over time. The only people still on it are Martin Holmes, Lou Burnard, and various members of Council. One of the first things this group did was map out how the Stylesheets actually work. Some of that knowledge is represented in https://wiki.tei-c.org/index.php/Mapping_ODD_processing. desires ------- Martin and I have a (somewhat aspirational, but somewhat realistic) plan to re-write the ODD portion of the Stylesheets from scratch. That is, we would like to write a completely new code base (in XSLT 3.0) for processing the source of P5 into the P5 outputs (in PDF via XSLFO, as opposed to via LaTeX; HTML5; ePUB; etc.), and for processing customization ODDs into schemas and documentation. We do not want to rewrite the rest of the Stylesheets, i.e. those parts that transform generic TEI Lite into useful output, and do various other conversions. (These same stylesheets are the backbone of OxGarage.) However, that would take a long time, and in the meantime we still have a nearly unmaintainable mess. cleaning up -------- -- I have often been frustrated reading Sebastian's code. I am not nearly as brilliant as he was, so I like having helpful comments along the way, proper indentation, some consistent method of variable and function names, etc. I also find long-winded XSLT 1.0 constructs where a short bit of XSLT 2.0 can do the same thing quite frustrating. So every time I dive into the stylesheets, I think "this really has to be cleaned up". But usually I don't want to do any actual cleaning, in order to keep the delta between the code base before and after whatever fix I am applying as small as possible, to make it easier to double-check that it hasn't introduced new errors. There are some people a lot smarter than I who say that it is always better to clean up a code base than re-write it from scratch. One of them wrote a lovely blog post about it. See https://www.joelonsoftware.com/2002/01/23/rub-a-dub-dub/ While I am sure there are computer scientists who disagree, it is a quite compelling article. rub-a-dub 1 --------- - So I convinced Martin that we should take a crack at cleaning the Stylesheets first (it wasn't hard). I then convinced Council of the same thing (not much harder). In late 2017 Council explicitly charged me with performing a clean up operation (called "rub a dub" or "rub a dub dub" based on what Joel called it in his blog) on a single, large, part of the Stylesheets: the odd2odd program. I spent my winter break exactly a year ago working my tail off for hours on end cleaning up code in ways that should not change the output. Pretty much every time I saved the file, I kicked off a test process to make sure the output came out the same. And it did! Every time. It wasn't until I was well over halfway through rubbing and dubbing that I discovered that, due to a misunderstanding between me & Martin (no blame on Martin, I just mistook what he said), the test procedure I was using was not actually testing odd2odd! I had been comparing the wrong output files, so of course they were the same every time. Sigh. In fact, while I blissfully thought I was doing such a great job, I had in fact mucked up the output almost beyond recognition. Sigh. rub-a-dub 2 --------- - So Martin and I redoubled our efforts on getting ODD testing in the Test2 system to work properly, and are almost finished with that. (Martin presented the Test2 system at our last Stylesheets group meeting.) Once that is done (my current goal is before I leave for a conference in Texas on Wed 09 Jan), I will attack rub-a-dub of odd2odd again, probably shortly after I get back from Texas. The over-arching goal will be to end up with a version of odd2odd that does the same thing, but is *much* easier to maintain. Some of the ancillary files (like common_functions) will likely need to be changed somewhat, too. By "the same thing" I mean "have essentially the same XML tree as output". I don't care about the incidentals of serialization, and may well sprinkle the output with comments if it seems to help. The point is I intend to try to explicitly avoid "improving" the processor as I go along. The detailed tasks I expect to work on to make it more maintainable are somewhat flexible, likely to change as I go along. But the following are the kinds of things I mean: * Reasonable indentation * Adding internal documentation * Re-factoring XSLT 1.0 constructs into XSLT 2.0 * Collapsing equivalent functions, modes, and templates where appropriate. (There are several cases where the Stylesheets have 2 or even 3 versions of what appear to be almost the same function, mode, or template.) * Changing names of functions, modes, templates, and variables in order to approach consistency * Re-factor logic to avoid double negatives where reasonable This, of course, will all be carried out in a separate branch, so as not to interfere with normal bug-fixing and the late Jan release.

1 0

Stylesheets group meeting
by Syd Bauman 21 Dec '18

21 Dec '18

We have a Stylesheets group meeting scheduled for today, Fri 21 Dec 18 at 21:00Z. (That's 13:00 PST, 16:00 EST, 21:00 GMT, and 22:00 CET.) Our agenda includes: * MH & SB presenting the progress so far on Test2/ (Mostly MH both because he's done more of the work, and because SB's voice is shot.) See https://github.com/TEIC/Stylesheets/blob/dev/Test2/README_build_odd.md for some (brand new!) documentation. * Ticket 325: https://github.com/TEIC/Stylesheets/issues/325 Talk to you soon! (Or, at least, whisper at you.)-:

3 2

Re: [Tei-council] Japanese translations incoming
by James Cummings 19 Dec '18

19 Dec '18

a) I agree marking up these phrases might be useful. (This doesn't just include simple modal verbs but also constructions involving 'require*', 'recommend*', 'optional*', since we already indicate these are equivalent to must, should, may.) I note that this will take more work than you might think, the way many of these are phrased mean automatic replacement would be error-prone. I would suggest that this be an addendum to the current ticket to be done once I've finished going through and checking them. (Doing it in two phases also means I double-check, though also someone else could do that to double-check my work? Happy either way.) b) We note that we are basing our use of modal verbs on BCP14 not only in the Guidelines Style Guide http://teic.github.io/TCW/tcw24.html but also in the Guidelines themselves at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/AB.html#AB-modal. To wit, I believe we already do what you are recommending. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Peter Stadler <stadler(a)edirom.de> Sent: 19 December 2018 08:21:42 To: Martin Holmes Cc: TEI Council Subject: Re: [Tei-council] Japanese translations incoming I wonder if we shouldn’t be marking up these verbs (and constructions?) ant to render these visually distinct? To me, that’d be a huge benefit for our meta language ODD in addressing technical documentation. Best Peter > Am 18.12.2018 um 17:33 schrieb Martin Holmes <mholmes(a)uvic.ca>: > > I do like the clarity of RFC 2119 and/or BCP 14, which seem to be pretty much identical. I wonder if we should state explicitly that our usage of modal verbs is intended to conform with one of them? > > Cheers, > Martin > > On 2018-12-18 7:29 a.m., James Cummings wrote: >> Hi Peter, Martin, etc. >> This ticket (https://github.com/TEIC/TEI/issues/1175#issuecomment-406592469) was something I was doing slowly when I got around to it. The actual work when you do it isn't difficult... Just double-checking that must/may/should etc. are all what we expect. Overall very few changes but mostly softening language (where we have said 'should' in past zealousness but even our own examples suggest 'may' is better). I'm happy to try to finish up the work sooner rather than later if desired. >> Many thanks, >> James >> -- >> Dr James Cummings, James.Cummings(a)newcastle.ac.uk >> Senior Lecturer in Late-Medieval Literature and Digital Humanities >> School of English, Newcastle University >> ------------------------------------------------------------------------ >> *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:* 18 December 2018 15:17:29 >> *To:* Peter Stadler; Martin Holmes >> *Cc:* TEI Council >> *Subject:* Re: [Tei-council] Japanese translations incoming >> Hi, >> there is also a ticket https://github.com/TEIC/TEI/issues/1175 for that. James already started to work on that, but there are 4-5K hits to check. I think we should split the work, or James? I have put it on the agenda for our next call in January. >> Thanks Martin for merging the translations! >> Best wishes, >> Martina >> -----Ursprüngliche Nachricht----- >> Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von Peter Stadler >> Gesendet: Dienstag, 18. Dezember 2018 07:39 >> An: Martin Holmes <mholmes(a)uvic.ca> >> Cc: TEI Council <tei-council(a)lists.tei-c.org> >> Betreff: Re: [Tei-council] Japanese translations incoming >> I couldn’t agree more! We currently mark technical terms (elements, classes) but not modal verbs which leads to confusion not only when translating. >> That’s quite an effort to go through the Guidelines and adjust (rephrase?) all those verbs but it would be a significant improvement. >> I’d like to put that on the agenda for our next f2f and see whether we can develop a plan for achieving this. What do you think? >> Best >> Peter >>> Am 17.12.2018 um 22:21 schrieb Martin Holmes <mholmes(a)uvic.ca>: >>> They're using the spreadsheets, and I'm transferring things back manually, one row at a time. There has been some discussion over the use of (for example) "may" in the Guidelines -- does it mean "be allowed to" or "can-if-you-wish" -- which makes me wonder whether it's time to look again at the modal verbs in TCW 24: >>> <http://teic.github.io/TCW/tcw24.html> >>> perhaps with an eye on RFC 2119: >>> <https://www.ietf.org/rfc/rfc2119.txt> >>> Cheers, >>> Martin >>>> On 2018-12-17 12:30 p.m., James Cummings wrote: >>>> That sounds excellent Martin! Thanks! >>>> Out of interest what process are they using to update the glosses, descs, etc. Those spreadsheets or something else? >>>> Many thanks, >>>> James >>>> -- >>>> Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University >>>> --------------------------------------------------------------------- >>>> --- >>>> *From:* Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Martin Holmes <mholmes(a)uvic.ca> >>>> *Sent:* 17 December 2018 17:07:14 >>>> *To:* TEI Council >>>> *Subject:* [Tei-council] Japanese translations incoming Hi all, Just a note to let everyone know that over the next little while I'll be slowly merging some new Japanese translations of glosses, descs and remarks into the dev branch. These are coming from some excellent work that Kiyonori and his team have been doing; they're about one-third of the way through the process of translating the spec files. >>>> I'm going to do this slowly and look at each item before I include it, mostly for my own learning purposes, but also in case I might catch the odd misunderstanding. >>>> Cheers, >>>> Martin >>>> _______________________________________________ >>>> Tei-council mailing list >>>> Tei-council(a)lists.tei-c.org >>>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council >>> _______________________________________________ >>> Tei-council mailing list >>> Tei-council(a)lists.tei-c.org >>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council >> _______________________________________________ >> Tei-council mailing list >> Tei-council(a)lists.tei-c.org >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council >> _______________________________________________ >> Tei-council mailing list >> Tei-council(a)lists.tei-c.org >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

Re: [Tei-council] Japanese translations incoming
by James Cummings 19 Dec '18

19 Dec '18

Hi Peter, Martin, etc. This ticket (https://github.com/TEIC/TEI/issues/1175#issuecomment-406592469) was something I was doing slowly when I got around to it. The actual work when you do it isn't difficult... Just double-checking that must/may/should etc. are all what we expect. Overall very few changes but mostly softening language (where we have said 'should' in past zealousness but even our own examples suggest 'may' is better). I'm happy to try to finish up the work sooner rather than later if desired. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ 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: 18 December 2018 15:17:29 To: Peter Stadler; Martin Holmes Cc: TEI Council Subject: Re: [Tei-council] Japanese translations incoming Hi, there is also a ticket https://github.com/TEIC/TEI/issues/1175 for that. James already started to work on that, but there are 4-5K hits to check. I think we should split the work, or James? I have put it on the agenda for our next call in January. Thanks Martin for merging the translations! Best wishes, Martina -----Ursprüngliche Nachricht----- Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von Peter Stadler Gesendet: Dienstag, 18. Dezember 2018 07:39 An: Martin Holmes <mholmes(a)uvic.ca> Cc: TEI Council <tei-council(a)lists.tei-c.org> Betreff: Re: [Tei-council] Japanese translations incoming I couldn’t agree more! We currently mark technical terms (elements, classes) but not modal verbs which leads to confusion not only when translating. That’s quite an effort to go through the Guidelines and adjust (rephrase?) all those verbs but it would be a significant improvement. I’d like to put that on the agenda for our next f2f and see whether we can develop a plan for achieving this. What do you think? Best Peter > Am 17.12.2018 um 22:21 schrieb Martin Holmes <mholmes(a)uvic.ca>: > > They're using the spreadsheets, and I'm transferring things back manually, one row at a time. There has been some discussion over the use of (for example) "may" in the Guidelines -- does it mean "be allowed to" or "can-if-you-wish" -- which makes me wonder whether it's time to look again at the modal verbs in TCW 24: > > <http://teic.github.io/TCW/tcw24.html> > > perhaps with an eye on RFC 2119: > > <https://www.ietf.org/rfc/rfc2119.txt> > > Cheers, > Martin > >> On 2018-12-17 12:30 p.m., James Cummings wrote: >> That sounds excellent Martin! Thanks! >> Out of interest what process are they using to update the glosses, descs, etc. Those spreadsheets or something else? >> Many thanks, >> James >> -- >> Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in >> Late-Medieval Literature and Digital Humanities School of English, >> Newcastle University >> --------------------------------------------------------------------- >> --- >> *From:* Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf >> of Martin Holmes <mholmes(a)uvic.ca> >> *Sent:* 17 December 2018 17:07:14 >> *To:* TEI Council >> *Subject:* [Tei-council] Japanese translations incoming Hi all, Just >> a note to let everyone know that over the next little while I'll be >> slowly merging some new Japanese translations of glosses, descs and >> remarks into the dev branch. These are coming from some excellent >> work that Kiyonori and his team have been doing; they're about >> one-third of the way through the process of translating the spec files. >> I'm going to do this slowly and look at each item before I include >> it, mostly for my own learning purposes, but also in case I might >> catch the odd misunderstanding. >> Cheers, >> Martin >> _______________________________________________ >> Tei-council mailing list >> Tei-council(a)lists.tei-c.org >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

3 2

Re: [Tei-council] Japanese translations incoming
by James Cummings 18 Dec '18

18 Dec '18

That sounds excellent Martin! Thanks! Out of interest what process are they using to update the glosses, descs, etc. Those spreadsheets or something else? Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Martin Holmes <mholmes(a)uvic.ca> Sent: 17 December 2018 17:07:14 To: TEI Council Subject: [Tei-council] Japanese translations incoming Hi all, Just a note to let everyone know that over the next little while I'll be slowly merging some new Japanese translations of glosses, descs and remarks into the dev branch. These are coming from some excellent work that Kiyonori and his team have been doing; they're about one-third of the way through the process of translating the spec files. I'm going to do this slowly and look at each item before I include it, mostly for my own learning purposes, but also in case I might catch the odd misunderstanding. Cheers, Martin _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

4 4

Re: [Tei-council] TEI Council chair elections
by James Cummings 18 Dec '18

18 Dec '18

Hi Elisa (etc.), My apologies. AOL stands for America Online. See http://catb.org/jargon/html/A/AOL-.html for an explanation of this reference. Apologies for being unintentionally cryptic. Best wishes, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Elisa Beshero-Bondar <ebb8(a)pitt.edu> Sent: 17 December 2018 13:28:54 To: James Cummings Cc: Scholger, Martina (martina.scholger(a)uni-graz.at) Vanessa Bigot-Juloux; TEI Council Subject: Re: [Tei-council] TEI Council chair elections James's last message is mysterious because I don't know what <aol> means...Google tells me: AOL Acronym Definition AoL Army of Light (Starwars Galaxies guild) AOL Age of Legends (Wheel of Time Series) AOL Airborne Oceanographic LIDAR AOL Absent Over Leave (See AWOL) which doesn't help much. Anyway, I, too, am glad Martina is willing to continue as chair. Elisa On Mon, Dec 17, 2018 at 1:23 PM James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> wrote: <aol>Me as well </aol> Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> School of English Literature, Language, and Linguistics, Newcastle University From: Vanessa Bigot-Juloux Sent: Monday, 17 December, 12:22 Subject: Re: [Tei-council] TEI Council chair elections To: Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) Cc: TEI Council Dear all, I totally agree: May I encourage you (Martina) to stand for election once more?! Best, Vanessa Le 13 déc. 2018 à 18:58, Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)UNI-GRAZ.AT<mailto:martina.scholger@UNI-GRAZ.AT>> a écrit : Dear all, I realized that I haven’t said anything about running for Chair again yet, but I wanted to keep the announcement and my candidature separate. I'd be happy to serve as Chair of the TEI Technical Council for another year. I learned a lot this year and have no doubt that there is yet more to learn. Best wishes, Martina Von: Peter Stadler <stadler(a)edirom.de<mailto:stadler@edirom.de>> Gesendet: Donnerstag, 13. Dezember 2018 17:49 An: Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>> Cc: TEI Council <tei-council(a)lists.tei-c.org<mailto:tei-council@lists.tei-c.org>> Betreff: Re: [Tei-council] TEI Council chair elections May I encourage you (Martina) to stand for election once more?! My feeling is you’re just about getting warm :) Best Peter Am 13.12.2018 um 14:19 schrieb Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>>: Dear all, this is a reminder for the upcoming election on the Council's chair for the next term. If you are interested in taking this position, please let us know before our next call on Monday (December 17) via the Council's mailing list. Best wishes, Martina _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu<mailto:ebb8@pitt.edu> Development site: http://newtfire.org<http://newtfire.org/>

2 1

Japanese translations incoming
by Martin Holmes 17 Dec '18

17 Dec '18

Hi all, Just a note to let everyone know that over the next little while I'll be slowly merging some new Japanese translations of glosses, descs and remarks into the dev branch. These are coming from some excellent work that Kiyonori and his team have been doing; they're about one-third of the way through the process of translating the spec files. I'm going to do this slowly and look at each item before I include it, mostly for my own learning purposes, but also in case I might catch the odd misunderstanding. Cheers, Martin

1 0