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

Fix spelling #672

Merged
merged 1 commit into from
Mar 15, 2024
Merged

Fix spelling #672

merged 1 commit into from
Mar 15, 2024

Conversation

jbampton
Copy link
Contributor

@jbampton jbampton commented Mar 8, 2024

No description provided.

@trishaoconnor trishaoconnor self-assigned this Mar 8, 2024
@ebeshero
Copy link
Member

ebeshero commented Mar 8, 2024

@jbampton @trishaoconnor Just a quick comment. Sometimes unusual spellings are part of a specialized discourse. I wondered about this use of "extention" rather than the expected "extension", so I quickly searched and found it in use in the Digital Menota project handbook, on this page down in 7.4.1: https://www.menota.org/HB1-0_ch7_corr.xhtml

We might want to check with some medieval paleographers to be sure it's really a misspelling.

@jamescummings
Copy link
Member

I don't think that 'extention' is a specialised term in this case, just a misspelling. While it is a variation on extension, it is really 16thC.

@sydb
Copy link
Member

sydb commented Mar 15, 2024

Well, the mss being described with the word “extention” is a 14th century mss, so it might be the case that the transcription is from the 16th century. But reading the passage it certainly does not sound like it is 16th century, sounds 20th century to me. More importantly, since both source occurrences are in test files (Test/test27.xml & Test2/testBibliography1.xml), it does not matter at all how the word is spelled. It may as well be spelled “Torremolinos, Torremolinos, and complainin’ about the food, oh it’s so greasy, isn’t it”.

@sydb sydb merged commit 030e0b1 into TEIC:dev Mar 15, 2024
2 checks passed
@jbampton jbampton deleted the fix-spelling branch March 15, 2024 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants