December 2014 - Tei-council

How about a translate-a-thon at the Members Meeting?
by Martin Holmes 30 Dec '14

30 Dec '14

Hi all, I have a vague memory of this idea being raised at some point, but I can't find any evidence of it, so maybe it was all in my head. After three attempts to get translation projects going have failed almost at the starting gate, it seems to me that we need an alternative strategy. Since the Members Meeting will be in France next year, how about organizing a one-day "translate-a-thon" to update the French translation? We could provide food, organization and guidance, and try to get a large enough group of interested French speakers to storm through as much of the French translation job as can be done in a day. We might get it all done. Even if we don't, I bet we could get far enough with it that the job would get finished over the following weeks. What do you think? Cheers, Martin

4 12

Stylesheets 7.28.0
by Sebastian Rahtz 29 Dec '14

29 Dec '14

In order to complete my term on Council in typically chaotic way, I have taken the opportunity to make a final release of the TEI Stylesheets for the year. Inter alia, this fixes a serious bug in PDF generation of the Guidelines which Lou spotted (looked at the content model for an element in the reference material in the last release); but mostly it represents a lot of fooling around with TCP conversion and rendering, of which more on Jan 1st. I have _not_ updated the oXygen TEI P5+XSL package, as I don’t want to interfere with work to automate that. So a happy holiday to you all, assuming you all do have some of winter solstice break around now, and farewell from me to the TEI Council -- Sebastian Rahtz Director (Research) of Academic IT University of Oxford IT Services 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 Não sou nada. Nunca serei nada. Não posso querer ser nada. À parte isso, tenho em mim todos os sonhos do mundo.

3 12

Enrich: (was Re: they come to bite us: biblScope/@type fallout
by Lou Burnard 21 Dec '14

21 Dec '14

I'm not sure I agree with that. There is quite a lot of data out there in the real world using Enrich and we wont win any friends by breaking it all for no good reason. I think it would be better to add @type as an explicit locally-defined attribute in the enrich ODD. There is also, I suspect, software which we really don't want to force people to modify., especially since we are no longer in touch with its developers. On 19/12/14 12:55, Sebastian Rahtz wrote: >> On 19 Dec 2014, at 12:50, Martin Holmes <mholmes(a)uvic.ca> wrote: >> >> Hi all, >> >> Following the removal of biblScope/@type, P5-Test and P5-Documentation >> built OK, but the main build failed because of the ENRICH schema, which >> I know nothing about. I guess we have two options: customize the ENRICH >> schema to add back @type on <biblScope>, or modify ENRICH so that it >> uses @unit instead. >> >> Since ENRICH seems to be an interchange format, the former seems the >> better option, so I'll proceed on that basis; if you know differently, >> please shout. It looks like Lou was heavily involved in ENRICH: >> >> <http://projects.oucs.ox.ac.uk/ENRICH/Deliverables/referenceManual_en.html> >> >> If the project is still very active, and has some method of discussing >> and propagating change, we could suggest that they incorporate this >> change into their schema through whatever mechanisms they usually use. > Lou, James and I all worked on ENRICH. No, it doesn’t have an active group > any more. > > I’d be inclined to the "modify ENRICH so that it uses @unit instead” method, > as I don’t want ENRICH to be something other than a subset of TEI. > but I’d like to hear what James and Lou think before you do anything. > -- > Sebastian Rahtz > Director (Research) of Academic IT > University of Oxford IT Services > 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 > > Não sou nada. > Nunca serei nada. > Não posso querer ser nada. > À parte isso, tenho em mim todos os sonhos do mundo. >

5 10

building P5 pdf locally
by Lou Burnard 20 Dec '14

20 Dec '14

On 18/12/14 14:39, Hugh Cayless wrote: > Sorting out the details of the build system would be nice. I can't myself > do a full buildâ€”it fails somewhere around PDF generation, possibly because > I don't have all the right fonts. But it's not at all clear to me what > those are or how to get them. I've never dug into it because I can generate > the HTML GLs just fine. Is there documentation about the details anywhere? If you run "make dependencies" it should list the packages that need to be installed under debian. These include msttcorefonts, and a bunch of other more exotic (but freely available) font packages, some of which have changed their names since the Makefile was last updated There is also a "make fonttest", but sfaics all this does is check to see whether you have Minion or Myriad fonts installed, and warn you that it will fall back to using yucky Computer modern roman if you don't. By default the Makefile doesn't try to build PDF, or Epub, or Mobi formats for the Guidelines, unless I am missing something. Is this something anyone would want to do when just testing their local mods? It's quite a big deal.

1 0

First message
by James Cummings 12 Dec '14

12 Dec '14

Just sending a first message to the tei-council(a)lists.tei-c.org mailing list. Partly so there can be something in the archives to test their availability. ;-) First post! -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0