Talk:XML Whitespace - Revision history

Gerrit bruening at 08:03, 30 August 2012

2012-08-30T08:03:21Z

John P. McCaskey at 14:39, 9 August 2012

2012-08-09T14:39:11Z

John P. McCaskey at 14:31, 9 August 2012

2012-08-09T14:31:16Z

Gerrit bruening: Created page with "There is not only the problem of unwanted leading and trailing white space: Significant white space may also inadvertently be removed by database applications. Explicitly protect..."

2012-08-08T10:08:37Z

Created page with "There is not only the problem of unwanted leading and trailing white space: Significant white space may also inadvertently be removed by database applications. Explicitly protect..."

New page

There is not only the problem of unwanted leading and trailing white space: Significant white space may also inadvertently be removed by database applications. Explicitly protecting significant whitespace is ugly. Which of all spaces are involved? And what is the best way to go? This problem may be discussed in the article. Or is it already discussed implicitly --gerrit.bruening 06:08, 8 August 2012 (EDT)

← Older revision		Revision as of 08:03, 30 August 2012
Line 2:		Line 2:

	As indicated in the article, mixed-content elements are unfamiliar to many people who write XML database applications. They must be made aware of the issues here, or significant whitespace will get removed. The algorithm described in the section Mixed-Content Elements should be used. It would be nice to add a section at the end of this article giving an example not just in XSLT but in some database connection tool. If anyone has experience processing XML whitespace in mixed-content elements using a tool other than XSLT, please contribute sample code. [[User:John P. McCaskey\|John P. McCaskey]] 10:31, 9 August 2012 (EDT)		As indicated in the article, mixed-content elements are unfamiliar to many people who write XML database applications. They must be made aware of the issues here, or significant whitespace will get removed. The algorithm described in the section Mixed-Content Elements should be used. It would be nice to add a section at the end of this article giving an example not just in XSLT but in some database connection tool. If anyone has experience processing XML whitespace in mixed-content elements using a tool other than XSLT, please contribute sample code. [[User:John P. McCaskey\|John P. McCaskey]] 10:31, 9 August 2012 (EDT)
		+
		+	:In the given example the inner element don't directly follow each other. What about
		+	<span style="background-color:#DBF0FD"> <p>  This was  <emph>my</emph> <foreign>grande croissant</foreign>!</span>
		+	<span style="background-color:#DBF0FD"> </p></span>
		+	:? Is it obvious that the algorithm described will ''not'' create
		+	<span style="background-color:#DBF0FD"><emph>my</emph><foreign>grande croissant</foreign></span>
		+	:? --gerrit.bruening 04:03, 30 August 2012 (EDT)

← Older revision		Revision as of 14:39, 9 August 2012
Line 1:		Line 1:
	There is not only the problem of unwanted leading and trailing white space: Significant white space may also inadvertently be removed by database applications. Explicitly protecting significant whitespace is ugly. Which of all spaces are involved? And what is the best way to go? This problem may be discussed in the article. Or is it already discussed implicitly --gerrit.bruening 06:08, 8 August 2012 (EDT)		There is not only the problem of unwanted leading and trailing white space: Significant white space may also inadvertently be removed by database applications. Explicitly protecting significant whitespace is ugly. Which of all spaces are involved? And what is the best way to go? This problem may be discussed in the article. Or is it already discussed implicitly --gerrit.bruening 06:08, 8 August 2012 (EDT)

−	The algorithm described in the section Mixed-Content Elements should ~~apply to database applications~~. ~~But it~~ would be nice to add a section at the end giving an example not just in XSLT but in some database connection tool. If anyone has experience processing XML whitespace in mixed-content elements using a tool other than XSLT, please contribute sample code. [[User:John P. McCaskey\|John P. McCaskey]] 10:31, 9 August 2012 (EDT)	+	As indicated in the article, mixed-content elements are unfamiliar to many people who write XML database applications. They must be made aware of the issues here, or significant whitespace will get removed. The algorithm described in the section Mixed-Content Elements should be used. It would be nice to add a section at the end of this article giving an example not just in XSLT but in some database connection tool. If anyone has experience processing XML whitespace in mixed-content elements using a tool other than XSLT, please contribute sample code. [[User:John P. McCaskey\|John P. McCaskey]] 10:31, 9 August 2012 (EDT)

← Older revision		Revision as of 14:31, 9 August 2012
Line 1:		Line 1:
	There is not only the problem of unwanted leading and trailing white space: Significant white space may also inadvertently be removed by database applications. Explicitly protecting significant whitespace is ugly. Which of all spaces are involved? And what is the best way to go? This problem may be discussed in the article. Or is it already discussed implicitly --gerrit.bruening 06:08, 8 August 2012 (EDT)		There is not only the problem of unwanted leading and trailing white space: Significant white space may also inadvertently be removed by database applications. Explicitly protecting significant whitespace is ugly. Which of all spaces are involved? And what is the best way to go? This problem may be discussed in the article. Or is it already discussed implicitly --gerrit.bruening 06:08, 8 August 2012 (EDT)
		+
		+	The algorithm described in the section Mixed-Content Elements should apply to database applications. But it would be nice to add a section at the end giving an example not just in XSLT but in some database connection tool. If anyone has experience processing XML whitespace in mixed-content elements using a tool other than XSLT, please contribute sample code. [[User:John P. McCaskey\|John P. McCaskey]] 10:31, 9 August 2012 (EDT)