Whitespace - Revision history

Kshawkin: redirect to XML Whitespace per request from John McCaskey

2012-08-05T16:42:00Z

redirect to XML Whitespace per request from John McCaskey

John P. McCaskey: /* Recommendations */

2012-07-30T13:28:37Z

Recommendations

← Older revision		Revision as of 13:28, 30 July 2012
Line 304:		Line 304:

	* Programmers should, unless instructed otherwise by <span style="background-color:#DBF0FD">@xml:space='preserve'</span>, implement code that normalizes space.		* Programmers should, unless instructed otherwise by <span style="background-color:#DBF0FD">@xml:space='preserve'</span>, implement code that normalizes space.
	* Encoders ~~can assume~~ such normalization will be done.		* Encoders should presume such normalization will be done but should include a note in the <tt><span style="background-color:#DBF0FD"><encodingStmt></span></tt> announcing the presumption.
	* Encoders should use <span style="background-color:#DBF0FD">@xml:space='preserve'</span> only with the utmost care. Whatever could be accomplished by using it is usually accomplished with less risk by using native TEI elements.		* Encoders should use <span style="background-color:#DBF0FD">xml:space='preserve'</span> only with the utmost care. Whatever could be accomplished by using it is usually accomplished with less risk by using native TEI elements.
	* Project teams should not intentionally or inadvertently use structured elements as if they were mixed-content elements. If this must be done, the schema should be customized to record the change.		* Project teams should not intentionally or inadvertently use structured elements as if they were mixed-content elements. If this must be done, the schema should be customized to record the change.

John P. McCaskey: /* Recommendations */

2012-07-30T04:47:48Z

Recommendations

← Older revision		Revision as of 04:47, 30 July 2012
Line 306:		Line 306:
	* Encoders can assume such normalization will be done.		* Encoders can assume such normalization will be done.
	* Encoders should use <span style="background-color:#DBF0FD">@xml:space='preserve'</span> only with the utmost care. Whatever could be accomplished by using it is usually accomplished with less risk by using native TEI elements.		* Encoders should use <span style="background-color:#DBF0FD">@xml:space='preserve'</span> only with the utmost care. Whatever could be accomplished by using it is usually accomplished with less risk by using native TEI elements.
	* Project teams should not intentionally or inadvertently use structured elements as if they were mixed-content elements. If it must be done, the schema should be customized to record the change.		* Project teams should not intentionally or inadvertently use structured elements as if they were mixed-content elements. If this must be done, the schema should be customized to record the change.

	== XSL Normalization Code ==		== XSL Normalization Code ==

John P. McCaskey: /* Mixed-Content Elements */

2012-07-30T04:44:47Z

Mixed-Content Elements

← Older revision		Revision as of 04:44, 30 July 2012
Line 218:		Line 218:
	The<u>cat</u>ate the ''grande croissant''. I didn't!		The<u>cat</u>ate the ''grande croissant''. I didn't!

	An encoder must assume that an element that includes nothing but text ''will'' get trimmed.		'''An encoder must assume that an element that includes nothing but text ''will'' get trimmed.'''

	== Structured Elements and xsl:strip-space ==		== Structured Elements and xsl:strip-space ==

John P. McCaskey: /* Mixed-Content Elements */

2012-07-30T04:44:02Z

Mixed-Content Elements

← Older revision		Revision as of 04:44, 30 July 2012
Line 199:		Line 199:
	\|-		\|-
	\| <tt>                                        <span style="background-color:#DBF0FD"><foreign>grande croissant</foreign></span></tt><br>		\| <tt>                                        <span style="background-color:#DBF0FD"><foreign>grande croissant</foreign></span></tt><br>
	<tt>                                        <span style="background-color:#DBF0FD">~~<foreign>~~grande croissant~~</foreign>~~</span></tt>		<tt>                                                 <span style="background-color:#DBF0FD">grande croissant</span></tt>

	\|\| Space in this text-only node is collapsed and trimmed, but no change results.		\|\| Space in this text-only node is collapsed and trimmed, but no change results.
Line 205:		Line 205:
	\| <tt>                                                                         <span style="background-color:#DBF0FD">. I didn't!</span></tt><br><tt>   <span style="background-color:#DBF0FD">  </span></tt><br>		\| <tt>                                                                         <span style="background-color:#DBF0FD">. I didn't!</span></tt><br><tt>   <span style="background-color:#DBF0FD">  </span></tt><br>
	<tt>                                                                         <span style="background-color:#DBF0FD">. I didn't!</span></tt>		<tt>                                                                         <span style="background-color:#DBF0FD">. I didn't!</span></tt>
	\|\| Because this is the last node in the <span style="background-color:#DBF0FD"><p></span>element, trailing space is trimmed and leading space is collapsed but not trimmed.		\|\| Because this is the last node in the <span style="background-color:#DBF0FD"><p></span> element, trailing space is trimmed and leading space is collapsed but not trimmed.
	\|-		\|-
	\|}		\|}

John P. McCaskey: /* Mixed-Content Elements */

2012-07-30T04:41:40Z

Mixed-Content Elements

← Older revision		Revision as of 04:41, 30 July 2012
Line 178:		Line 178:
	The algorithm to normalize space in mixed content is:		The algorithm to normalize space in mixed content is:
	* Collapse all white space, then		* Collapse all white space, then
	* trim		* trim:
	** leading space on the first text node in an element and		** trim leading space on the first text node in an element and
	** trailing space on the last text node in an element,		** trim trailing space on the last text node in an element,
	** both if a text node is both first and last, i.e., is the only text node in the element.		** trim both if a text node is both first and last, i.e., is the only text node in the element.

	Applying that algorithm to the above passage:		Applying that algorithm to the above passage:

John P. McCaskey: /* Trimming */

2012-07-30T04:39:10Z

Trimming

← Older revision		Revision as of 04:39, 30 July 2012
Line 105:		Line 105:
	=== Trimming ===		=== Trimming ===

	Whether text in an element should or will be trimmed depends ~~(1)~~ whether the ~~element contains other elements (1) on TEI's specification of the element's ''parent'', (2) on whether~~ the element has siblings~~, and if so, whether the element is first of those siblings, is the last one, or is in the middle, and (3) on practices of the encoders, practices unspecified in TEI~~.		Whether text in an element should or will be trimmed depends on whether it is the only text in the element or it has siblings that are themselves elements.

	==== Text-Only Elements ====		==== Text-Only Elements ====

John P. McCaskey at 02:54, 30 July 2012

2012-07-30T02:54:39Z

← Older revision		Revision as of 02:54, 30 July 2012
Line 1:		Line 1:
	~~THIS PAGE IS UNDER ITS INITIAL CONSTRUCTION AND CHANGING FREQUENTLY -- John, July 29, 2012~~


	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.		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.

John P. McCaskey: /* XSL Normalization Code */

2012-07-30T02:54:26Z

XSL Normalization Code

← Older revision		Revision as of 02:54, 30 July 2012
Line 313:		Line 313:
	== XSL Normalization Code ==		== XSL Normalization Code ==

	XSL's normalize-space() function cannot simply be used on all text nodes. The program must consider where a text node is among its siblings.		XSL's <span style="background-color:#DBF0FD">normalize-space()</span> function cannot simply be used on all text nodes. The program must consider where a text node is among its siblings.

	The following code implements the trimming algorithm described above. It works for both text-only and mixed-content elements. The code overrides the built-in template for the appropriate text() nodes so may simply be added to XSLT stylesheets. XSLT processors will normally take care of collapsing.		The following code implements the trimming algorithm described above. It works for both text-only and mixed-content elements. The code overrides the built-in template for the appropriate text nodes so may simply be added to XSLT stylesheets. XSLT processors will normally take care of collapsing.

	<xsl:template priority=".7" match="text()[position()=1 and not((ancestor::node()/@xml:space)[position()=last()]='preserve')]">		<xsl:template priority=".7" match="text()[position()=1 and not((ancestor::node()/@xml:space)[position()=last()]='preserve')]">

John P. McCaskey: /* XSL Normalization Code */

2012-07-30T02:53:54Z

XSL Normalization Code

← Older revision		Revision as of 02:53, 30 July 2012
Line 313:		Line 313:
	== XSL Normalization Code ==		== XSL Normalization Code ==

	The following code implements the trimming algorithm described above. The code overrides the built-in template for the appropriate text() nodes. XSLT processors will normally take care of collapsing.		XSL's normalize-space() function cannot simply be used on all text nodes. The program must consider where a text node is among its siblings.

			The following code implements the trimming algorithm described above. It works for both text-only and mixed-content elements. The code overrides the built-in template for the appropriate text() nodes so may simply be added to XSLT stylesheets. XSLT processors will normally take care of collapsing.

	<xsl:template priority=".7" match="text()[position()=1 and not((ancestor::node()/@xml:space)[position()=last()]='preserve')]">		<xsl:template priority=".7" match="text()[position()=1 and not((ancestor::node()/@xml:space)[position()=last()]='preserve')]">