Whitespace

TEI has robust features for specifying space, gaps, line breaks, and related aspects of the space between text. But TEI is an XML vocabulary, and XML itself, and programs that read and process XML files, have their own ways to deal with what they call whitespace, that is, space, tab, carriage return and linefeed characters. Sometimes the standards, constraints, and conventions imposed by XML cause problems for TEI encodings and for programs that process TEI files.

Where XML Considers Whitespace to be Significant

In XML documents, some whitespace is significant, some is not. For example, inside the brackets that mark XML elements extra whitespace is not significant. For any program processing these as pieces of XML,

<title type="main">

and

<title     type = "main" >

are the same. There is no significance to the extra space. By XML rules, no application that processes the data in this XML file (processing it as XML and not just as text) is allowed to treat these two representations differently. A person or computer editing this file is free to use either one, based merely on readability and aesthetics. The fact that there is whitespace between title and type is significant, but how much or of what kind (space characters, tabs, carriage returns, new lines) is not significant. The space between type and = is not significant.

Whitespace can be significant, however, in the content of an element. For example,

<name>JoAnn</name>

and

<name>Jo Ann</name>

are different because of that space between Jo and Ann, and any program reading this element in an XML file is obliged to maintain the distinction.

But things can get complicated. Consider this:

<persName>    
    <forename>Jo</forename>
    <forename>Ann</forename>
    <surname>Henry</forename>
</persName>

Should the carriage returns and new lines matter? Should it matter if that open area before <surname> is a tab or is instead four space characters? Should it matter that there is extra space after <persName>?

“Collapse,” “Trim,” “Normalize”

Many applications, including web browsers and many programs that read XML files will, unless instructed otherwise, “collapse” XML whitespace, that is, they will replace any contiguous string of space characters (0x20), tabs (0x09), carriage returns (0x0D) and line feeds (0x0A) with just one space character. So

  <name>Jo Ann</name>

  <name>Jo    Ann</name>

  <name>Jo 
      Ann</name>

are all treated as if there were just one space character between Jo and Ann. Moreover many applications also remove (“trim”) leading and trailing XML whitespace. So these, too,

  <name> Jo Ann</name >

  <name>
      Jo Ann</name>

  <name>
      Jo   
      Ann
  </name>

are treated as if the XML had been simply <name>Jo Ann</name>.

Sometimes, as in the XSLT function “normalize-space()”, the term “normalize” refers to the combination of collapsing XML whitespace and then trimming. Other times, as in XML Schema, “collapse” is the name of the combined operation.

Normalizing XML whitespace is very common. It is so pervasive that it is easy to overlook that it is happening and even difficult to know which program processing an XML file is doing the normalizing—is it the XSLT processor, the XSL program, the web browser, the print routine, or some combination?

@xml:space

XML defines an attribute, xml:space, that when set to preserve indicates that applications should suspend default trimming, collapsing, and normalizing and instead keep all the spaces, tabs, carriage returns and line feeds just as they appear. If @xml:space is set to default or is simply left off, no such request is made; the application is free to do whatever its developer thinks best.

The attribute xml:space is inherited by child elements. One could, for example, put xml:space="preserve" into a TEI <text> element but not in <teiHeader> to indicate that the request applies to all of the text but to none of the header.

TEI allows xml:space to be used on any element. But since TEI has so much rich functionality for encoding spaces, gaps, line breaks, and so on, the xml:space attribute is rarely used. Whatever could be accomplished by setting its value to preserve would be better accomplished by using native TEI elements. So the value is normally left as default by simply not including the attribute. Downstream processors are then left free to treat XML whitespace however the application developers want.

Default Whitespace Processing

When xml:space is left as default, nothing in XML or TEI specifies how consumers of a TEI XML file should treat whitespace.

There are, however, unspecified conventions. TEI encoders generally assume that some downstream processor will collapse spaces, tabs, carriage returns, and line feeds and will remove (“trim”) the space at the beginnings and ends of encodings such as this:

  <p>   
      We hold these truths to be self-evident,  that all men are   
      are created equal,  that they are endowed by their creator 
      with certain inalienable Rights,  that among these are Life,   
      Liberty and the pursuit of Happiness.
  </p>

If the TEI file will be displayed in a web browser, the assumption is probably safe. Authors of web browsers have accepted responsibility for normalizing such text. The authors of other applications that read TEI XML files may need to be instructed to do the same.

Ideally there would be a formal mechanism for such communication, but XML has no such mechanism, and TEI 5 does not either. Because the assumption manifestly made above is so common, the author of a program that reads a TEI XML file should—unless instructed otherwise by the encoders—assume the burden of collapsing, but not necessarily trimming, space in text nodes such as this one above. Whether the text should also be trimmed depends on what other elements are around the one being processed.

Default Whitespace Processing in Elements That Contain Elements

Elements with only text, such as the one immediately above, generally cause little trouble. Without thinking much about it, encoders assume space will get normalized, and programmers have tools that do so. Elements that contain other elements, either alone or with text, are much more troublesome. Different encoders will make different assumptions. Programmers will make yet others. How elements will be processed may depend on how they were specified and consumers, producers or both may be unaware of the details.

Consider first elements that contain both other elements and text, so-called mixed-content elements.