[tei-council] Things needing translation
Lou Burnard
lou.burnard at retired.ox.ac.uk
Thu Jan 2 09:10:15 EST 2014
On 02/01/14 11:13, Sebastian Rahtz wrote:
> On 30 Dec 2013, at 23:46, Syd Bauman <s.bauman at NEU.EDU> wrote:
>
>> 4 out of 5 isn't bad. But as I look at the Guidelines today, there
>> are 425 elements that have both a child <exemplum> with versionDate=
>> and a child <exemplum> without versionDate=. Since <exemplum>s aren't
>> necessarily grouped by the example contained, some of these might be
>> OK. But I really doubt all 425 are -- I bet most are instances where
>> we should be putting @versionDate on the <exemplum>s that don't have
>> it.
> <exemplum>s are a bit harder to deal with than gloss/desc/remarks, for
> two reasons:
>
> a) the exempla in different languages are not translations; so because
> en English example has changed, it does not follow that the Chinese
> one should.
>
> b) the example are not identified/unique. So we cannot simply run the script
> which looks to see when an example has has changed at some point in time.
>
> I agree that <exemplum> having @versionDate is a good thing,
> but I don’t think its part of the same I18N issue.
> --
>
I disagree. Putting @versionDate on <exemplum> is a bad idea, for the
reasons you give above. I would vote for removing @versionDate from all
<exemplum>s
More information about the tei-council
mailing list