Trailing whitespace cleanup for XML files

General find and replace clean up

Author: jbampton

lib/NUnit/NUnit.ConsoleRunner.3.5.0/tools/nunit.engine.api.xml

@@ -19,7 +19,7 @@
 	<Query>
 		<MatchAllDocsQuery/>
 	</Query>
-	
+
 	<Filter>
 		<!--
 			This query illustrates how a BooleanFilter can be used to combine
@@ -31,11 +31,11 @@
 				<RangeFilter fieldName="date" lowerTerm="19870409" upperTerm="19870412"/>
 			</Clause>
 			<Clause occurs="mustNot">
-				<TermsFilter fieldName="contents">Emcore</TermsFilter> 
+				<TermsFilter fieldName="contents">Emcore</TermsFilter>
 			</Clause>
 		</BooleanFilter>
-		
+
 	</Filter>
-	
+
 </FilteredQuery>
 

src/Lucene.Net.Tests.QueryParser/Xml/BooleanFilter.xml

@@ -25,7 +25,7 @@
 			<Clause occurs="must">
 				<TermQuery>bank</TermQuery>
 			</Clause>
-		</BooleanQuery>	
+		</BooleanQuery>
 	</Query>
 	<BoostQuery boost="0.01">
 			<UserQuery>"world bank"</UserQuery>

src/Lucene.Net.Tests.QueryParser/Xml/BoostingQuery.xml

@@ -22,36 +22,36 @@
 				<TermQuery>merger</TermQuery>
 			</Clause>
 			<Clause occurs="mustnot">
-				<TermQuery >sumitomo</TermQuery>		
+				<TermQuery >sumitomo</TermQuery>
 			</Clause>
 		</BooleanQuery>
 	</Query>
-	
+
 	<Filter>
 		<!--
-			CachedFilter elements can contain any Query or Filter. 
-			CachedFilters are cached in an LRU Cache keyed on the contained query/filter object. 
-			Using this will speed up overall performance for repeated uses of the same expensive 
-			query/filter. The sorts of queries likely to benefit from caching need not necessarily be 
+			CachedFilter elements can contain any Query or Filter.
+			CachedFilters are cached in an LRU Cache keyed on the contained query/filter object.
+			Using this will speed up overall performance for repeated uses of the same expensive
+			query/filter. The sorts of queries likely to benefit from caching need not necessarily be
 			complex - e.g. simple TermQuerys with a large DF (document frequency) can be expensive
-			on large indexes. A good example of this might be a term query on a field with only 2 possible 
-			values - "true" or "false". In a large index, querying or filtering on this field requires 
-			reading millions of document ids from disk which can more usefully be cached as a 
+			on large indexes. A good example of this might be a term query on a field with only 2 possible
+			values - "true" or "false". In a large index, querying or filtering on this field requires
+			reading millions of document ids from disk which can more usefully be cached as a
 			QueryFilter bitset.
-			
+
 			For Queries/Filters to be cached and reused the object must implement hashcode and
 			equals methods correctly so that duplicate queries/filters can be detected in the cache.
-			
+
 			The CoreParser.maxNumCachedFilters property can be used to control the size
 			of the LRU Cache established during the construction of CoreParser instances.
 			-->
 		<CachedFilter>
 			<!-- Example query to be cached for fast, repeated use -->
-			<TermQuery fieldName="contents">bank</TermQuery> 
+			<TermQuery fieldName="contents">bank</TermQuery>
 			<!-- Alternatively, a filter object can be cached ....
 				<RangeFilter fieldName="date" lowerTerm="19870409" upperTerm="19870412"/>
-			-->				
+			-->
 		</CachedFilter>
 	</Filter>
-	
+
 </FilteredQuery>

src/Lucene.Net.Tests.QueryParser/Xml/CachedFilter.xml

@@ -25,10 +25,10 @@
 				<TermQuery fieldName="date">19870408</TermQuery>
 			</Clause>
 		</BooleanQuery>
-	</Query>	
+	</Query>
 	<Filter>
 		<!-- Filters to last document with this date -->
 		<DuplicateFilter fieldName="date" keepMode="last"/>
 	</Filter>
-	
+
 </FilteredQuery>

src/Lucene.Net.Tests.QueryParser/Xml/DuplicateFilterQuery.xml

@@ -18,6 +18,6 @@
 <FuzzyLikeThisQuery>
 	<!-- Matches on misspelt "Sumitomo" bank -->
 	<Field fieldName="contents">
-		Sumitimo bank 
+		Sumitimo bank
 	</Field>
 </FuzzyLikeThisQuery>

src/Lucene.Net.Tests.QueryParser/Xml/FuzzyLikeThisQuery.xml

@@ -16,18 +16,18 @@
  limitations under the License.
 -->
 <LikeThisQuery percentTermsToMatch="5" stopWords="Reuter" minDocFreq="2">
-IRAQI TROOPS REPORTED PUSHING BACK IRANIANS Iraq said today its troops were pushing Iranian forces out of 
-	positions they had initially occupied when they launched a new offensive near the southern port of 
-	Basra early yesterday.     A High Command communique said Iraqi troops had won a significant victory 
-	and were continuing to advance.     Iraq said it had foiled a three-pronged thrust some 10 km 
-	(six miles) from Basra, but admitted the Iranians had occupied ground held by the Mohammed al-Qassem 
-	unit, one of three divisions attacked.     The communique said Iranian Revolutionary Guards were under 
-	assault from warplanes, helicopter gunships, heavy artillery and tanks.     "Our forces are continuing 
-	their advance until they purge the last foothold" occupied by the Iranians, it said.     
-	(Iran said its troops had killed or wounded more than 4,000 Iraqis and were stabilising their new positions.)     
-	The Baghdad communique said Iraqi planes also destroyed oil installations at Iran's southwestern Ahvaz field 
-	during a raid today. It denied an Iranian report that an Iraqi jet was shot down.     
-	Iraq also reported a naval battle at the northern tip of the Gulf. Iraqi naval units and forces defending an 
-	offshore terminal sank six Iranian out of 28 Iranian boats attempting to attack an offshore terminal, 
+IRAQI TROOPS REPORTED PUSHING BACK IRANIANS Iraq said today its troops were pushing Iranian forces out of
+	positions they had initially occupied when they launched a new offensive near the southern port of
+	Basra early yesterday.     A High Command communique said Iraqi troops had won a significant victory
+	and were continuing to advance.     Iraq said it had foiled a three-pronged thrust some 10 km
+	(six miles) from Basra, but admitted the Iranians had occupied ground held by the Mohammed al-Qassem
+	unit, one of three divisions attacked.     The communique said Iranian Revolutionary Guards were under
+	assault from warplanes, helicopter gunships, heavy artillery and tanks.     "Our forces are continuing
+	their advance until they purge the last foothold" occupied by the Iranians, it said.
+	(Iran said its troops had killed or wounded more than 4,000 Iraqis and were stabilising their new positions.)
+	The Baghdad communique said Iraqi planes also destroyed oil installations at Iran's southwestern Ahvaz field
+	during a raid today. It denied an Iranian report that an Iraqi jet was shot down.
+	Iraq also reported a naval battle at the northern tip of the Gulf. Iraqi naval units and forces defending an
+	offshore terminal sank six Iranian out of 28 Iranian boats attempting to attack an offshore terminal,
 	the communique said.      Reuter 3;
-</LikeThisQuery>
+</LikeThisQuery>

src/Lucene.Net.Tests.QueryParser/Xml/LikeThisQuery.xml

@@ -19,9 +19,9 @@
 	<Query>
 		<MatchAllDocsQuery/>
 	</Query>
-	
+
 	<Filter>
 		<RangeFilter fieldName="date" lowerTerm="19870409" upperTerm="19870412"/>
 	</Filter>
-	
+
 </FilteredQuery>

src/Lucene.Net.Tests.QueryParser/Xml/MatchAllDocsQuery.xml

@@ -17,12 +17,12 @@
 -->
 <!--
 	This query was added to demonstrate nested boolean queries - there
-	was a bug in the XML parser which added ALL child <Clause> tags to 
+	was a bug in the XML parser which added ALL child <Clause> tags to
 	the top level tags ie. took child and grandchild elements instead
-	of just child elements. This was due to the use of the 
+	of just child elements. This was due to the use of the
 	Element.getElementsByTagName() call in BooleanQueryBuilder
--->	
-<BooleanQuery fieldName="contents">	
+-->
+<BooleanQuery fieldName="contents">
 	<Clause occurs="should">
 		<BooleanQuery fieldName="contents">
 			<Clause occurs="must">

src/Lucene.Net.Tests.QueryParser/Xml/NestedBooleanQuery.xml

@@ -22,16 +22,16 @@
 				<TermQuery>merger</TermQuery>
 			</Clause>
 			<Clause occurs="mustnot">
-				<TermQuery >sumitomo</TermQuery>		
+				<TermQuery >sumitomo</TermQuery>
 			</Clause>
 			<Clause occurs="must">
 				<TermQuery>bank</TermQuery>
 			</Clause>
 		</BooleanQuery>
 	</Query>
-	
+
 	<Filter>
 		<NumericRangeFilter fieldName="date2" lowerTerm="19870409" upperTerm="19870412"/>
 	</Filter>
-	
+
 </FilteredQuery>