Text only | Skip links
Skip links||IT Services, University of Oxford

Contents

1. Editing Options for TEI Users

This section provides a brief overview of technology for editing in TEI, and issues related to that in the area of data capture and editing.

2. Summary

How does a TEI user do the following?
  • Data capture
  • Editing

3. What tools do we need?

  • Appropriately expressive vocabularies (eg TEI XML)
  • Syntax-checking document creation tools (ie editors)
  • Document transformation tools
  • Document delivery tools
  • Document storage and management tools
  • Programming interfaces
  • Specialized applications

4. Two stages to get a TEI text

  • capture the text
  • create the markup
Often they occur simultaneously; but often not.

Note that the markup does not necessarily all have to be in the same file.

5. Categories of creation tools

  • scanning/OCR
  • data-entry vendors
  • software to add tagging automatically
  • editors
followed by
  • validators, well-formedness checkers
  • proofing aids, data integrity checkers

6. OCR/Data Entry

  • Scanning and OCR software generally produce only minimal HTML or Word (e.g., recognizing paragraph breaks, font changes etc).
  • Data-entry vendors in theory would insert whatever markup you wanted, but at a price. They generally prefer HTML or TEI Lite or some such well-known DTD.
  • TEI is creating a standard slimed-down vocabulary for initial encoding that may be useful in mass-digitisation projects called 'TEI tite'.

7. Editor types

Editing tools cover a wide spectrum:
  • Basic text editors
  • General programmers' editors
  • XML-aware programmers' editors
  • XML-specific editors
  • Word-processors which can export XML
  • Data-entry forms
  • Image-specific editors
it is likely that people in different roles need different tools.

8. Things to look for in specialist XML editors

  • schema-aware
  • constraining element entry
  • IDE features
  • customizable
  • validation, preferably continual
  • Multiple display views (as tree, with tags, formatted etc)
  • folding structures
  • context-sensitive help
For XML editing, Emacs, oXygen, jEdit, XMetaL, XMLSpy, Stylus Studio, Arbortext Adept are all worth a look.

For image editing, try University of Victoria Image Markup Tool or Edition Production and Presentation Technology (EPPT).

9. oXygen screenshot 1

10. oXygen screenshot 2

11. oXygen screenshot 3

12. Tagless editing in oXygen

13. EPPT

14. UVic IMT screenshot 1

15. UVic IMT screenshot 2

16. What is missing, or hard, in the TEI editing world

  • Editors like XMetaL which combine visual feedback with code editing
  • Visual, or WYSIWYG, editors in web applications (eg in a CMS); most web editors are for XHTML (cf Writely)
  • Reliable conversion to and from Word and OpenOffice styles. Note:
    • the general inability of word-processors to nest inline inside inline, or block inside block
    • the difficulty of extrapolating a hierarchical structure from a sequence of free-standing headings at assorted levels
    • the tedious programming required to trace the ancestry of styles in Word and OO
    • the lack of a facility in OO to stop the user formatting by hand

17. Next...?

Next, Dot will lead us in an exercise editing some XML in oXygen version 9.



Dot Porter. Date: 2007-10-31
Copyright University of Oxford