Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add handling for choice/sic/corr #274

Open
joewiz opened this issue Apr 28, 2020 · 2 comments
Open

Add handling for choice/sic/corr #274

joewiz opened this issue Apr 28, 2020 · 2 comments

Comments

@joewiz
Copy link
Member

joewiz commented Apr 28, 2020

In order to capture known typos in the published/printed editions of our publications, we should explore the use the TEI <choice> element and related elements (see TEI Guidelines on Simple Editorial Changes), which lets us indicate the original, printed words/phrases and corrected words/phrases.

Aspects of this to be developed include:

  • enabling these elements in the FRUS ODD and generated schema files
  • developing clear practices and documenting how we will use these elements in the FRUS ODD and generated documentation files
  • updating the FRUS TEI PM ODD to properly display the new elements
  • adding clear explanations for readers so they know how to interpret this information

Initial work on this will be performed in branches of frus and hsg-shell, and will be discussed with Mandy and Kathy before adopting it.

@vak2ve
Copy link
Contributor

vak2ve commented May 5, 2020

Typos on the printed page fall into several categories:

  1. Searchable terms--proper names of various kinds including names, groups, and ships, as well as place names. Typos will keep users from finding documents that match these search terms.

Britian

Canfederate
Duucan,

Oreta

United Staes
Nicaragua,
Mexiro.

Philadelpaia.

  1. High-certainty typos—repeated fragments before and after a line break

de-degree
govern-ernment
beeen
gov-government

  1. Medium-certainty typos—one letter missing, transposed letters, incorrect usage of similar letters (especially vowels, echoing common OCR error patterns)

ot
whieh
accouut
accopt
lordshid
liad

  1. Low-certainty typos--possible legitimate spelling variation at the time

batallion
embassador
exequator

exequatur
Schulz.
siezed

siezure

@joewiz
Copy link
Member Author

joewiz commented Mar 9, 2021

Another example via the mailbox today: In https://history.state.gov/historicaldocuments/frus1901/d448, the dateline of the attachment contains a typo: "Kinkiang" should be "Kiukiang." As shown in shown on https://history.state.gov/historicaldocuments/frus1901/pg_509, this typo was in the original:

Screen Shot 2021-03-09 at 1 59 38 PM

Mr. Kupfer worked in Kiukiang, Kiangsi province (using today's spelling, Jiujiang, Jiangxi province).

It would be nice to inform readers that we are aware of the typo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants