Difference between revisions of "MarineLives Transcription & Editorial Policy: Draft Five"
m |
m |
||
Line 135: | Line 135: | ||
'''"arle"''' is transcribed as '''"ar''ti''cle"''' | '''"arle"''' is transcribed as '''"ar''ti''cle"''' | ||
− | '''"Capt"'''is transcribed as '''" | + | '''"Capt"'''is transcribed as '''"Capt''aine''"''' (unless the clerk elsewhere spells the expanded word without a final '''"e"''') |
'''"comand"''' (with tilda over the "m") is transcribed as '''"com''m''and"''' | '''"comand"''' (with tilda over the "m") is transcribed as '''"com''m''and"''' | ||
Revision as of 10:53, September 20, 2012
MarineLives Transcription & Editorial Policy: Draft Five
Editorial history
26/08/12: CSG, created page
Contents
- 1 Suggested links
- 2 Draft Five: Transcription and Editorial policy
- 2.1 Letter forms
- 2.2 Punctuation
- 2.3 Capitalization
- 2.4 Abbreviations
- 2.5 Contractions and Suspensions
- 2.6 Tildas (horizonal lines over a letter)
- 2.7 Letters supplied by transcriber
- 2.8 Letters lost due to manuscript staining or damage
- 2.9 Letters deleted in manuscript
- 2.10 Text inserted above (or below) lines in main body of text
- 2.11 Text written in margins
- 2.12 Spacing
- 2.13 Line breaks
- 3 Draft Five: Coding buttons for metadata
- 4 Draft Five: Coding buttons for text format and layout
- 5 Draft Five: Coding buttons for Notes, Questions, and Help requests
- 6 Draft Five: Coding buttons for semantic markup
Suggested links
Transcription & Editorial Policy
MarineLives Transcription & Editorial Policy: Draft One
MarineLives Transcription & Editorial Policy: Draft Two
MarineLives Transcription & Editorial Policy: Draft Three
MarineLives Transcription & Editorial Policy: Draft Four
Introduction to the High Court of Admiralty
Draft Five: Transcription and Editorial policy
Draft of MarineLives Editorial Method/Directions for Transcribers
Draft of MarineLives Editorial Method/Directions for Transcribers
Revised September 15th, 2012
Charlene M. Eska and Colin Greenstreet
ceska@vt.edu, colin.greenstreet@gmail.com
This draft is current and should be applied to all transcriptions from September 16th, 2012
The aim of the transcribers is to create a semi-diplomatic edition of the HCA documents. As such, transcribers will, for the most part, transcribe exactly what they see using the following conventions.
Letter forms
Spelling is not standardized, so it is important to transcribe what you see and resist the urge to ‘correct’ the spelling. Any letters that are written superscript should be lowered.
EXAMPLE:
"3:th, 4:th, 5:th" should be transcribed as "3th, 4th, 5th"
U/V, u,v Transcribe each of these letters as they appear in the documents. Do not make the determination of whether the graph represents a vowel or a consonant.
i/j, I Transcribe each of these letters as they appear in the documents.
Y Although it looks like the letter ‘y’, it is really a form of þ ‘thorn’ and should be transcribed as ‘th’. Common sense will tell you whether you are dealing with <y> or <þ>.
EXAMPLES:
"y:e" should be transcribed as "the" "y:t" should be transcribed as "that" "y:m" should be tranScribed as "them"
Punctuation
Punctuation is different from what we are used to. Transcribe the marks as you see them. The only exception to this will be the dash used to fill the ends of lines; ignore these marks. Do not try to impose modern punctuation conventions.
EXAMPLES:
"./."
":/:"
":-"
Transcribe any dots surrounding numerals.
EXAMPLE:
".1.", ".6th."
Preserve the page layout as much as possible when you transcribe, including the placement of signatures and line breaks within paragraphs.
EXAMPLE:
56. William ffowkes ^SIGNATURE ON BOTTOM RH SIDE^
The above text is produced using the NOTE function:
William ffowkes <note>SIGNATURE ON BOTTOM RH SIDE </note>
Where there is a marginal item and a main body text item within the same line in the original manuscript, transcribe the main body text line first, then add a space, transcribe the marginal item, preserving the lineation of the marginal item, and add a further space
EXAMPLE:
The code would be as follows:
31. did together with this deponent and others sayle and depart in and with
32. the sayd shipp from Gravesend about the ˹eleventh˺ eighth day of december 1654
33. XXXXXXXXX day And they entred into whole pay in the sayd shipp # ORIGINAL MANUSCRIPT INSERTION MARK, DIRECTING ATTENTION TO TEXT IN LH MARGIN and the
34.
35. <margin value="Left"># upon the eighth day
36. of the sayd moneth,
37. William dixon</margin>
38.
39. sayd shipp arrived afterwards att ffalmouth and from thence
Follow the foliation of the original documentsm and enter the folio number, together with added recto or verso, in the HEADER information
EXAMPLE:
<folio>f.169r</folio>
Capitalization
Do not capitalize letters that are not written in capitals. Transcribe what you see.
Be particularly careful that you do not capitalise the names of people, places, and ships if they are not capitalised in the original.
Be particularly observant of the differences between lower and upper case "c/C" and "h/H"
An index will be created with standardized forms of names, places, ships, etc., and all spelling variants will be indexed accordingly.
Abbreviations
& The ampersand represents the word ‘and’. Transcribe it as ‘and’ without putting it in italics. If it is part of a Latin phrase, transcribe it as ‘et’.
Some words are commonly abbreviated, e.g. ‘arle’ for ‘article’. Put supplied letters in italics. Below is a list of commonly abbreviated and contracted words.
Contractions and Suspensions
XXX All letters supplied by the transcribers should be in italics. This will be the case wherever contractions and suspensions are expanded.
EXAMPLE:
"ag:t" is transcribed as "against"
"als" is trancribed as "alias"
"allon" is transcribed as "allegation"
"arle" is transcribed as "article"
"Capt"is transcribed as "Captaine" (unless the clerk elsewhere spells the expanded word without a final "e") "comand" (with tilda over the "m") is transcribed as "command"
"depon" is transcribed as "deposition"
"depted" is transcribed as "departed"
"depo:t" is transcribed as "deponent" "D:r" is transcribed as "Doctor"
"interr" is usually transcribed as "interrogatory" or "interrogatorie" depending on expanded form the clerk uses elsewhere on the page. If no expanded example, then use "interrogatory"
BUT in some contexts "interr" is a contraction for "interrate", for example "the Interrate Travers or his Agents" should be transcribed as "the Interrate Travers or his Agents"
"labo:r" is transcribed as "labour" "M^r^ is transcribed as "Master"
"parlls" is transcribed as "parcells"
"pcells" is transcribed as "parcells" "pticular" is transacribed as "particular"
"pties" is transcribed as "parties"
"p mo: is transcribed as "per moneth:
"pdposed" is transcribed as "predeposed"
"pson" is transcribed as "person"
"prsent" is transcribed as "present
"pused" is transcribed as "perused"
"rcd" , "recd" and "recvd" are transcribed as "received", "received" and "received" (unless there is evidence elsewhere on the relevant page that the clerk is using the expanded spelling "receave", in which case the expansion of the contractions should be suitably adjusted
"sd" and "s:d" are transcribed as "said or sayd" depending on expanded form the clerk uses elsewhere on the page. If no expanded example, then use sayd"
"S:t" is transcribed as "Saint"
"sumes" (with a tilda over the "m") is transcribed as "summes" "wch" is transcribed as "which"
"worfull" (with tilda over the word) is transcribed as "worshipfull"
"worll" is transcribed as "worshipfull"
POLICY DECISION REQUIRED
"arlate". How is this related to "Article" and to "Allegation"?
"interrate". How is this related to "Interrogatory" and "Interrogatories"? Is it an abbreviation for "Interrogated"?
"libellate". How is this related to "Libell"?
"Midd". Should we expand this common suspension to "Middlesex"? What does Dr Murphy do in her Irish Manscript Commission edition of the Irish HCA papers?
"rend:t". Should this be transcribed as "rendent" or as "respondent"?
"vizt" is an abbreviation for "videlicet", which means "namely" or "to wit"
"xr" is an abbreviation for the latin "et cetera"
Tildas (horizonal lines over a letter)
Tildas represent single or double ‘m’ or ‘n’. Be mindful of the different ways of representing ‘per’, ‘pro’, ‘par’, ‘pre’, etc. along with ‘-con’.
EXAMPLES:
"comonly" (with a tilda over the m) should be transcribed as "commonly" (with the second m inserted by the transcriber and italicised)
Letters supplied by transcriber
[XXX] Any letters supplied should be enclosed in square brackets. This is sometimes the case when a letter has been omitted by mistake. Use sparingly.
Letters lost due to manuscript staining or damage
{…} Letters lost due to staining, damage, etc. Give an indication, if possible, of how many letters are lost and if any letter forms are even partially visible.
Letters deleted in manuscript
--XSTRIKETHROUGHX-- Use the strikethrough function to indicate text deleted in the documents. Transcribe as much as you can see.
Text inserted above (or below) lines in main body of text
˹XXX˺ Text written between the lines
Text written in margins
Use MARGIN button and add Left, Right, Top left, Top Left, Bottom Left, Bottom Right, in inout box and click enter
Spacing
Only ever leave one space after a full stop, comma, semi-colon, or any form of punctuation, no matter how much space the clerk left.
Line breaks
Line breaks in the original manuscript should be shown using a carriage return
Words which are split over lines and which are marked so by the clerk should be shown with "=" (which is the typical symbol used by clerks to indicate such an event)
EXAMPLE:
3. Thomas Sharpe of the parish of Saint Stephen Coleman= 4. Street London merchant Late Purser of the sayd shipp 5. the Swan now called the Satisfaction aged 26, yeares
Draft Five: Coding buttons for metadata
HEADER
Generates the following code:
<header>
<series></series>
<folio></folio>
<picture></picture>
<summary></summary>
<document-date></document-date>
<status></status>
<first-transcriber></first-transcriber>
</header>
CASE
Generates the following code:
<case>
<charge></charge>
<summary></summary>
<date value=""></date>
<plaintiff></plaintiff>
<defendant></defendant>
</case>
DEP
Generates the following code:
<deposition>
<summary></summary>
<date value=""></date>
<witness></witness>
</deposition>
Draft Five: Coding buttons for text format and layout
Italic
Generates the following code: XXXX
Strike
Generates the following code: XXXX
Underline
Generates the following code: XXXX
Bold
Generates the following code: XXXX
Insert
Generates the following symbols: ˹XXXX˺
Margin
Generates the following code: <margin value="XXXX">Margin</margin>
Special characters (Add)
# (New)
Square bracket - [ (New)
Square bracket - ] (New)
Draft Five: Coding buttons for Notes, Questions, and Help requests
Note (All notes to be added in CAPITALS)
Generates the following code: <note></note>
Help (HELP request answers to be added in CAPITALS after the highlighted item, but still within the code (<help>Help request HELP ANSWER FROM A COLLEAGUE</help>
Question (New) (All questions to be added in CAPITALS)
Generates the following code: <question></question>
Draft Five: Coding buttons for semantic markup
The menu above the input box contains a number of buttons which at a later stage we will use for "semantic markup". These are the buttons labelled
Person
Title
Occupation
Commodity
Currency
Quantity
Ship
Place
Date
This form of markup defines for later analysis the nature of a specific word or block of text. Computers are not clever. Humans are. So computers need to be told if the "Red Hand" is a ship or a hand which is red.
Giovanni Colavizza and Patrizia Rebulla, two of our team facilitators, are co-leading our semantic markup and analysis team. At a later stage of the project your team facilitator, working with Giovanni and Patrizia, will show you how to use these semantic mark up buttons, and we will introduce a specific set of editorial conventions related to this type of markup