[tei-council] Things needing translation

[Sebastian Rahtz]

On 30 Oct 2013, at 20:15, Syd Bauman <s.bauman at neu.edu> wrote:

>   Currently, versionDate= is put on the non-English <desc>, <gloss>,
>   <exemplum>, <valDesc>, or <remarks> only. I.e., it is not put on
>   the canonical <desc>, just the translation <desc>s. (There are 6
>   exceptions.) This, it seems to me, is a mistake. If we required
>   versionDate= to be on every att.translatable element that was, in
>   fact, translated (including the canonical), then the comparisons
>   would be *much* easier, no? Or am I missing something, here?
no, I agree. thats what will be in place by Friday
> SR> column 9: reap statement (optional)
> 
> 2a) What's a "reap statement"? 
> 
<respStmt>

> 2b) I'm a bit nervous about using a spreadsheet for data that could,
>    often should, and occasionally will, contain markup.

whats the alternative? I was trying to think of ways of doing it on the cheap.


> 
> 2c) Most importantly, no matter how people are entering this, it
>    seems to me we need to give them an opportunity for entering
>    notes or discussion. We want to encourage (I think) the
>    back-and-forth of "why did you translate X as Y? wouldn't Z be a
>    better term?", etc.
sure. have as many comment columns as needed.
> 
> 2d) Don't we need to include the date for versionDate=, too? (Or are
>    you planning to extract that from the GoogleDoc history, in which
>    case you are a braver man than I -- although we all knew that
>    already. :-)
yes, that is an issue.


--
Sebastian Rahtz      
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431