We spent our time last week thinking about how editors make decisions about what should or shouldn’t be represented through the TEI when creating digital editions of texts. Today we’re going to get our hands (or at least our fingertips) dirty encoding actual texts. Here’s what I want to do:
- First, download the materials we will use for today’s lab.
- You should all have the free trial the oXygen XML editor running on your computers. We will begin by reviewing briefly how oXygen works and why you might want to use it for editing TEI.
- Next we will divide into groups. Each group is responsible for encoding one of the documents in the “transcriptions” folder of today’s lab packet. The images of these documents can be found in the “images” folder.
- Use the sample encoded documents in the base folder to figure out how to encode these new documents. Pay attention to the document images as well—are there textual features that should be accounted for?
- TEI by Example provides a nice walkthrough to encoding different kinds of texts in TEI. You can also browse and search the current TEI guidelines to find the right tags for particular tasks.
…for groups with a TEI-experienced member:
- If you are familiar with CSS stylesheets you can use TEI Boilerplate to style your TEI documents and publish them on your personal website. There are more complex ways to publish large collections of TEI, but Boilerplate is a quick and easy way to get TEI-encoded documents out.
To complete this lab, your group should submit your encoded TEI document by class next week. In addition, you should write a brief reflection about encoding (as a theoretical act, as an editorial practice, &c. &c.) and post it to your blog. Send me the link when it’s ready.