| Both sides previous revision Previous revision Next revision | Previous revision |
| transcriptions:rules [2019-12-26 10:41:02] – reworked the examples Ken Norman | transcriptions:rules [2024-04-01 14:56:41] (current) – minor edits to Thorn bullet Ken Norman |
|---|
| * If a word is illegible, I'll typically use a sequence of underline characters in place of the unknown word (e.g., ''[%%____%%]''). | * 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?]''). | * 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..."). | * 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., "...Quragoby''[?]'' 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/ ''[4 shillings]''; or, 4/ ''[4s]''). | * **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/ ''[4 shillings]''; or, 4/ ''[4s]''). |
| * **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). |
| * **"Long" //s//**: The [[wp>Long_s|long s]] (i.e., the <typo fc:blue; fw:bold; ff:serif>//ſ//</typo> character) is an archaic form of the lower case letter //s//, which was used both in some early printing typesets as well as in handwriting. I simply replace it with a lowercase //s//. Some transcribers use the lowercase //f//, but that is grammatically and syntactically incorrect. | * **"Long" //s//**: The [[wp>Long_s|long s]] (i.e., the <typo fc:blue; fw:bold; ff:serif>//ſ//</typo> character) is an archaic form of the lower case letter //s//, which was used both in some early printing typesets as well as in handwriting. I simply replace it with a lowercase //s//. Some transcribers use the lowercase //f//, which is both grammatically and syntactically incorrect, so that practice is rejected on this site. |
| | * **Thorn (Þ, þ)**: The letter [[wp>Thorn_(letter)|thorn]] was used in Old English, and had a 'th' sound. As the letter became non-standard in the English alphabet, it was often replaced by 'y' which looked similar. Hence, we find words like 'ye' in writing and print. Wherever the context is clear, I transcribe the letter 'y' as the 'th' it phonetically represents. Thus, 'ye' (the definite article, not the [[wp>Ye_(pronoun)|pronoun]]) will be transcribed as 'the'. I will do similarly anywhere 'y' is used in place of 'þ' (e.g., 'yt' ⇒ 'that'). |
| * **Existing line breaks**: As a general rule, I do //not// preserve line breaks from the original text when they are due solely to the text encountering the edge of the paper. This rule is driven primarily by two factors: | * **Existing line breaks**: As a general rule, I do //not// preserve line breaks from the original text when they are due solely to the text encountering the edge of the paper. This rule is driven primarily by two factors: |
| * Such line breaks are not necessary for preserving the semantics of the transcription. | * Such line breaks are not necessary for preserving the semantics of the transcription. |
| * My transcriptions are posted online and, as such, the text needs to "flow" based on screen size. Even so, some line breaks make perfect sense, such as when it's obvious that a new line is appropriate (lists, tabular data, etc.). | * My transcriptions are posted online and, as such, the text needs to "flow" based on screen size. Even so, some line breaks make perfect sense, such as when it's obvious that a new line is appropriate (lists, tabular data, etc.). |
| * **Inserted line breaks**: I may insert a line break when it makes the transcription more readable or more comprehensible. An example would be to begin a new line for each "Item" in a will. Another example is when the original text is written in one long, continuous paragraph; in such a case I may break it into sections as content dictates. | * **Inserted line breaks**: I may insert a line break when it makes the transcription more readable or more comprehensible. An example would be to begin a new line for each "Item" in a will. Another example is when the original text is written in one long, continuous paragraph; in such a case I may break it into sections as content dictates. |
| * **Punctuation**: No punctuation is added or removed, even if doing so would improve readability. Old documents (and images thereof) often have smudges or marks that are mistaken for punctuation. I'll ignore these when/if the context reasonably indicates they are not punctuation marks. | * **Punctuation**: No punctuation is added or removed, even if doing so would improve readability. Old documents (and images thereof) often have smudges or marks that are mistaken for punctuation. I'll ignore these when/if the context reasonably indicates they are not punctuation marks. |
| | * **Person Names**: I highlight all occurrences of people's names with bold text (e.g., **John Q. Public**) in order to make it easy for the reader to quickly scan a page to find them. I do //not// highlight names of deities (e.g., God, Jesus), rulers (e.g., King George), politicians, or anyone unaffiliated with the author or subject(s) of a given document. |
| |