| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| transcriptions:rules [2019-11-05 23:03:20] – old revision restored (2019-10-25 21:34:45) Ken Norman | transcriptions:rules [2019-12-14 15:39:26] – added text for "illegible/confusing" Ken Norman |
|---|
| |
| * **Semantic preservation**: I always preserve the semantics of what is written/typed. If the text is factually incorrect, I nevertheless remain faithful to the author's words. | * **Semantic preservation**: I always preserve the semantics of what is written/typed. If the text is factually incorrect, I nevertheless remain faithful to the author's words. |
| * **Brackets** (i.e., ''<typo fc:blue; fw:bold>[</typo> ... <typo fc:blue; fw:bold>]</typo>''): I use brackets to denote anything that is //not// in the original text. I have very rarely found brackets in use in older handwritten text. | * **Brackets** (i.e., ''<typo fc:blue; fw:bold>[</typo> ... <typo fc:blue; fw:bold>]</typo>''): I use brackets to denote something that is //not// in the original text. I have very rarely found brackets in use in older handwritten text. |
| * **Errors**: I use ''[sic]'' to denote when an error is the author's, not mine. Sometimes, I will include the correction (e.g., ''pson [sic: person]''). | * **Errors**: I use ''[sic]'' to denote when an error is the author's, not mine. Sometimes, I will include the correction when it isn't entirely obvious (e.g., ''pson [sic: person]''). |
| * **Dates**: Dates are written in a variety of ways, to include numbers written as words. I strive to always type the date in a standardized Gregorian Calendar format of ''dd Mmm yyyy'' immediately after the text date (e.g., ''the Tenth Day of aprill 1684 [10 Apr 1684]''). This makes the date more easily recognized by search engines. | * **Dates**: Dates are written in a variety of ways, to include numbers written as words. I strive to always type the date in a standardized Gregorian Calendar format of ''dd Mmm yyyy'' immediately after the text date (e.g., ''the Tenth Day of aprill 1684 [10 Apr 1684]''). This makes the date more easily recognized by search engines. |
| * **Numbers**: When quantities are written as words, I'll give the numeric equivalent in brackets (e.g., ''one hundred [100]''). | * **Numbers**: When quantities are written as words, I'll give the numeric equivalent in brackets (e.g., ''one hundred [100]''). |
| * **Names**: When a name is abbreviated, or given only as initials, I will provide a complete name if it is known (e.g., ''Wm. [William]''). | * **Names**: When a name is abbreviated, or given only as initials, I will provide a complete name if it is known (e.g., ''Wm. [William]''). This helps improve search engine results. |
| | * **Illegible/Confusing**: |
| | * If a word is illegible, I'll typically use a sequence of underline characters in place of the unknown word (e.g., ''[%%____%%]''). |
| | * Sometimes I'll take a reasonable guess (based on context and/or similarity to other text on the page) and include a question mark (e.g., ''[twenty?]''). |
| | * Occasionally, if the word appears legible, but also seems incorrect in context, I'll just add a commented question mark after the transcription (e.g., "...Quingsby''[?]'' Swamp..."). |
| * **Money**: I will indicate money using modern notation wherever possible (e.g., ''ten pounds [£10]''). If old style notation is used, I will convert to modern notation (e.g., ''4/ [4s]'', which is four shillings). | * **Money**: I will indicate money using modern notation wherever possible (e.g., ''ten pounds [£10]''). If old style notation is used, I will convert to modern notation (e.g., ''4/ [4s]'', which is four shillings). |
| * **No new content**: I never introduce new content into the transcribed text (except when contained within brackets, as described above). | * **No new content**: I never introduce new content into the transcribed text (except when contained within brackets, as described above). |