Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Amadis Conference Preparation
Part 1: First 10 minutes. Stacey begins.
Introduce Amadis: What is this thing?
Textual History: pithy and interesting! NOT necessarily a series of word-for-word translations into other languages or into newer forms of Spanish. Southey and earlier translators all CHANGED this text in producing versions of it in their own languages. But they're also translating.
Typical pejorative terms for this:
Actually it's not so terrible--it might be a GOOD way to translate, to reproduce this romance adapted to a specific culture. IS this a translation or a creative adaptation? It's something of BOTH.
TERMS OF THE DEBATE: "Bad Translation" or "Cultural Adaptation"? Translation theory is limited in its grasp of cultural adaptation!
Issue in translation theory = word-for-word vs. sense-for-sense. Ours is closer to sense for sense WITH interest in omissions and additions.
show page images
Our Editorial Declaration show on screen and discuss our decisions.
Our specific project: Why work on Montalvo and Southey?
--Why is Southey's translation interesting? --compression, omissions, and leveling the narrative. Additions and changes to the speech acts: alterations of direct to indirect discourse, AND vice versa.
feature examples from two or three key, juicy passages: side-by-side views on web
How did we apply TEI markup to study this act of translation and/or adaptation?
<cl> markup of Montalvo: How we applied it, and why we decided to make these sequential sibling elements, and not nested. NOT always literal clauses:
<cl> as "clause-like unit". Complexities of Montalvo chunking plus the need to map LOCATIONS in the text, giving each a distinct xml:id so that we can reference that id in our coding of Southey's translation.
** Presence of pseudo-markup ** in Montalvo: Show images. Discuss how we used these to signal clause-like breaks and what kinds of things they designate.
visual of code: probably side-by-side of Southey and Montalvo, PLUS the TEI code that does it
<s> elements ** in Southey and
<p> elements: Southey's structure is mostly his own. He adds paragraphs and creates English sentences. Speak to Southey's editorial work on punctuation and grammar. [Stacey]
We don't use @ref attributes on the
<s> elements because we don't expect there to be a one-to-one correspondence between sentences and the "clause-like" groupings of Montalvo.