SV: [tei-council] damage - what is it good for?

[Matthew James Driscoll]

Well, for what it's worth, I've never used <damage>, nor really understood
why anyone would. If you can read what it says, no problem; if you can read
enough of it to make a reasonable guess at the missing bits use <supplied
type="illegible">; and if you can't read anything at all use <gap>. 

Come to think of it, I've never really understood what <unclear> was for
either.

Matthew

-----Oprindelig meddelelse-----
Fra: Lou Burnard [mailto:lou.burnard at oucs.ox.ac.uk] 
Sendt: 03 September 2007 16:36
Til: TEI Council; Gabriel Bodard
Emne: [tei-council] damage - what is it good for?

As I proceed through PH wreaking havoc, I have come upon the <damage> 
element. This is allegedly used to mark a part of a manuscript within 
which there has been some damage to the carrier, e.g. by rubbing or 
singeing or spilling marmalade, but not so much as to make the 
transcriber unsure of what the writing actually says (if that were the 
case, the <unclear> element should be used), nor so extensive as to make 
the writing (or the carrier) actually disintegrate or disappear (for 
which the <gap> element is available).

As defined, <damage> respects textual structures even less than the 
other elements. If it is to be kept, it should probably be given a 
sister <damageSpan> (analogous to <delSpan>) so that it can point across 
div boundaries for example.  Though even then there isn't any really 
satisfactory way of dealing with things like circular spots of damage in 
the middle of the page, which have to be split up into numerous <damage> 
elements.

But since it is really about the state of the carrier, not the text, why 
would you want to record it anyway? I am sorely tempted to just remove 
it and see who protests....


_______________________________________________
tei-council mailing list
tei-council at lists.village.Virginia.EDU
http://lists.village.Virginia.EDU/mailman/listinfo/tei-council