[From nobody Sun Jan 13 13:13:07 2008 Envelope-to: lou@herald.ox.ac.uk Delivery-date: Sun, 13 Jan 2008 18:11:14 +0000 Received: from rx1.herald.ox.ac.uk ([163.1.0.245]) by imap211.herald.ox.ac.uk with esmtp (Exim 4.63) (envelope-from <nobody@sourceforge.net>) id 1JE7If-0004Kf-UF for lou@herald.ox.ac.uk; Sun, 13 Jan 2008 18:11:13 +0000 Received: from relay1.mail.ox.ac.uk (relay1.mail.ox.ac.uk [129.67.1.165]) by rx1.herald.ox.ac.uk (Postfix) with ESMTP id E5CEF24047 for <lou@herald.ox.ac.uk>; Sun, 13 Jan 2008 18:11:13 +0000 (GMT) Received: from j3.village.virginia.edu ([128.143.20.247]) by relay1.mail.ox.ac.uk with esmtp (Exim 4.68) (envelope-from <nobody@sourceforge.net>) id 1JE7If-00067T-3u for lou.burnard@oucs.ox.ac.uk; Sun, 13 Jan 2008 18:11:13 +0000 Received: from mail.sourceforge.net (lists.sourceforge.net [66.35.250.206]) by j3.village.Virginia.EDU (Postfix) with ESMTP id 8EE0312977 for <editors@tei-c.org>; Sun, 13 Jan 2008 13:11:10 -0500 (EST) Received: from sc8-sf-web22-b.sourceforge.net ([10.3.1.212] helo=sc8-sf-web22.sourceforge.net) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1JE7IY-0003Ju-5l; Sun, 13 Jan 2008 10:11:06 -0800 Received: from nobody by sc8-sf-web22.sourceforge.net with local (Exim 4.43) id 1JE7IW-0002Cm-VZ; Sun, 13 Jan 2008 10:11:05 -0800 To: noreply@sourceforge.net From: "SourceForge.net" <noreply@sourceforge.net> Subject: [ tei-Feature Requests-1019594 ] Manuscript encoding Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-SourceForge-Tracker-unixname: tei X-SourceForge-Tracker-trackerid: 644065 X-SourceForge-Tracker-itemid: 1019594 X-SourceForge-Tracker-itemstatus: Open X-SourceForge-Tracker-itemassignee: jcummings X-SourceForge-Tracker-itemupdate-reason: Settings changed X-SourceForge-Tracker-itemupdate-username: louburnard Message-Id: <E1JE7IW-0002Cm-VZ@sc8-sf-web22.sourceforge.net> Sender: Nobody <nobody@sc8-sf-web22.sourceforge.net> Date: Sun, 13 Jan 2008 10:11:04 -0800 X-Oxmail-Spam-Status: score=0.0 tests=none X-Oxmail-Spam-Level: Feature Requests item #1019594, was opened at 2004-08-31 11:34 Message generated for change (Settings changed) made by louburnard You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=644065&aid=1019594&group_id=106328 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: new or changed element Group: None Status: Open Priority: 3 Private: No Submitted By: Hilde Bøe (hildeboe) >Assigned to: James Cummings (jcummings) Summary: Manuscript encoding Initial Comment: Henrik Ibsen's Writings has made several changes and additions to the TEI DTDs regarding the encoding of manuscript changes and manuscript phenomena. In the following we wish to present some of the modifications and encourage the inclusion of these themes in the P5 revision discussion. - <clarification> We've created a new element to record the clarification phenomenon in manuscripts. Ibsen and his copyists some times clarify words or letters either writing upon the already written word/letters or by repeating the word/letters offline. We encode these instances of repeating the same for the purpose of clarification, like this: <clarification hand="HI" place="inline">Henrik</clarification> <clarification hand="HI" place="offline">Henrik</clarification> We believe this is a well known phenomenon for manuscript transcribers, and we think it would be a useful addition in a revised chapter on "Transcription of Primary Sources". - TEI elements for manuscript changes We've made it possible to include almost all kinds of elements in <app> (i.e. in <lem>/<rdg> of course), <add>, <del> etc. and to use <app>, <add>, <del>, <gap/> etc. almost globally in our manuscript transcriptions in order to record manuscript changes in a way that reflects our view of the changes. E.g. we allow <div> inside <add> and <del> to make possible the inclusion or deletion of a complete scene, thus reflecting the change in the document structure more clearly. - The hand attribute We have allowed the hand attribute in <app>, <hi> and <emph>. Including hand in <app> makes it unnecessary to use hand both in <add> and <del> when another hand has revised the text of the manuscript. Using the hand attribute in <hi> (and similarly in <emph>) allows us to record e.g. the red pencil underlining throughout a manuscript otherwise written in black ink. - A new element for substitutions/revision of the <app> element The last years there have been discussions on the TEI-L and elsewhere of the need to modify and revise the <app> element to make it more useful for manuscript changes. Several alternatives have been discussed. At Henrik Ibsen's Writings we have also discussed this, and although we have managed to use the excisting <app> element for the manuscript changes in our material (though with some modifications of what <lem> and <rdg> can contain and the inclusion of some attributes), we would like to encourage the expansion of this part of the chapter on "Transcription of Primary Sources", at least an element for encoding substitutions should be included. We dislike the double role of the <app> structure, and would feel better having one structure for manuscript changes and one for the critical apparatus. Our use of the <app> element for manuscript changes has resulted in us constructing a new element, <tcApp>, for our critical apparatus and text critical notes. Please contact Hilde Bøe (hilde.boe@ibsen.uio.no) at Henrik Ibsen's Writings, if you have any questions or remarks. ---------------------------------------------------------------------- Comment By: Lou Burnard (louburnard) Date: 2007-02-18 12:43 Message: Logged In: YES user_id=1021146 Originator: NO I apologise for the delay in responding to this ticket, which raises several distinct issues. 1. new element <clarification> for a specific kind of manuscript addition 2. changes in use of the <app> element 3. make the @hand attribute available on <app>, <hi>, and <emph> (1) seems to me to be an interesting suggestion that should however be looked at in the context of a complete overhaul of the Physical Transcription module. This is unlikely to get done for P5 1.0. (2) some changes have been made in the content model of <app>, following suggestions from others: however your basic proposal to distinguish its use in manuscript transcription from its use in transcription of critical apparatus has not yet been debated; it should be. (3) this seems simple enough. I think the way to it would be to define a new attribute class, almost the same as the existing att.ascribed class. This could easily be done for P5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=644065&aid=1019594&group_id=106328 ]