Print whole book
Making a digital edition with TEI and Anastasia
 1 Why should we use the TEI encodings?
  1.1 An example, and a brief history
 2 About this set of exercises
  2.1 Why should we use Anastasia?
  2.2 What we will do in this exercise
  2.3 What you need
 3 Encoding an electronic version of a single document
  3.1 The Document Type Definition (DTD): some useful tools
  3.2 The <teiHeader>
  3.3 The <text> element
  3.4 Using <msDescription> to encode complex document metadata
 4 Publishing the digital facsimile with Anastasia
  4.1 Parsing the document
  4.2 Publishing with Anastasia
  4.3 Making the book
  4.4 Telling the Anastasia Reader about the book
  4.5 Simple formatting of the book
   4.5.1 Starting to read the book: an Anastasia call
   4.5.2 Formatting text with an .anv file: the begin command
   4.5.3 Formatting elements with an .anv file
  4.6 Advanced formatting of the book
   4.6.1 Introducing Anastasia property value commands
   4.6.2 Debugging .anv files: puts
   4.6.3 More Anastasia property value commands
   4.6.4 Chunking the text
  4.7 Making hypertext links
   4.7.1 We can hide part of a document, and then reveal it with a hypertext link
   4.7.2 We can view a document with a different style sheet
   4.7.3 Adding parameters to an Anastasia call
   4.7.4 Going to a particular page of the document: parameters and httppost
   4.7.5 Searching with Anastasia
   4.7.6 Using HTML forms to let users navigate the document
   4.7.7 Using HTML forms to let users find text in the document
   4.7.8 Showing the hits in context
  4.8 Including images in your document
  4.9 Dealing with special characters
 5 Making one collection from many digital editions
  5.1 Presenting digital collections with Anastasia
  5.2 Managing a digital collection with Anastasia
 6 Useful Anastasia tricks and tips
  6.1 Tcl tricks and hints
   6.1.1 Including a file in an .anv file
   6.1.2 Do maths with expr
   6.1.3 Regular expression matching with regexp
   6.1.4 Regular expression substitutions with regsub
   6.1.5 Test expressions with a standalone Tcl interpreter
  6.2 HTML tricks and hints
   6.2.1 Use a cascading style sheet (css) to control display
   6.2.2 Use Javascript to create a popup menu
Making a digital edition with TEI and Anastasia > 1 Why should we use the TEI encodings? >
Previous   Print this chapter   Next

1 Why should we use the TEI encodings?

The aim of the Text Encoding Initiative encodings is to provide a single XML implementation for all humanities documents. If you use the TEI, in theory at least, you do not need to have one encoding for catalogue style ‘metadata’ materials (which might be in a database), one encoding for the source documents (which might be in .pdf files or some other proprietary form), and yet another encoding for analytic, commentary, or teaching materials (which might be Microsoft files). Instead, you can use one encoding system for it all.

Why does this matter? Libraries, for example, are well used to having different materials in different forms: the different shapes of books alone dictate they be shelved separately. It matters because in the explosion of digital information in the last years we now have so many documents, in so many different forms, and so many different readers with so many different interests, that attempts to construct boundaries within this universe resemble clogdancing on quicksand. The many different readers need many and various routes to find the documents they want -- especially, to find the documents they did not know they wanted. Further, the many readers do not care what format the information is held in: to a reader searching the web, all documents look the same; all that matters is to find it. And, more practically, multiplication of document formats and encoding means multiplication of effort in supporting all these.

Previous   Print this chapter   Next