Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revisionBoth sides next revision
transcriptions:rules [2019-12-14 16:18:02] – fixed text for "Long s" Ken Normantranscriptions:rules [2019-12-14 16:30:36] – clarified some text Ken Norman
Line 14: Line 14:
   * **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//** (i.e., the ''<typo fc:blue; fw:bold>ſ</typo>'' character): The [[wp>Long_s|long s]] 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//** (i.e., the ''<typo fc:blue; fw:bold>ſ</typo>'' character): The [[wp>Long_s|long s]] 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.
-  * **Existing line breaks**: As a general rule, I do not preserve line breaks in the original text when it is 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: 
-    * Intentionally preserving such a line break does not enhance the transcription.  +    * Such line breaks are not necessary for preserving the semantics of the transcription.  
-    * My transcriptions will be 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 is obvious 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'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. +  * **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
  
  • Last modified: 2024-04-01 14:56:41
  • by Ken Norman