Fixed the XML syntax of a few test files.

tests/data/test1026

@@ -25,7 +25,7 @@ curl --manual
 # Search for these two sentinel lines in the manual output; if they are found,
 # then chances are good the entire manual is there.
 <postcheck>
-perl -e 'open(IN,$ARGV[0]); my $lines=grep(/(a\s*tool\s*to\s*transfer\s*data)|(mailing\s*lists\s*to\s*discuss\s*curl)/, <IN>); exit ($lines != 2);' log/stdout1026
+perl -e 'open(IN,$ARGV[0]); my $lines=grep(/(a\s*tool\s*to\s*transfer\s*data)|(mailing\s*lists\s*to\s*discuss\s*curl)/, <IN>); exit ($lines != 2); # Let this file pass an XML syntax check: </IN>' log/stdout1026
 </postcheck>
 </client>
 

tests/data/test1027

@@ -25,7 +25,7 @@ curl --help
 # Search for these two sentinel lines in the help output; if they are found,
 # then chances are good the entire help is there.
 <postcheck>
-perl -e 'open(IN,$ARGV[0]); my $lines=grep(/(Usage: curl )|(--version\s*Show version)/, <IN>); exit ($lines != 2);' log/stdout1027
+perl -e 'open(IN,$ARGV[0]); my $lines=grep(/(Usage: curl )|(--version\s*Show version)/, <IN>); exit ($lines != 2); # Let this file pass an XML syntax check: </IN>' log/stdout1027
 </postcheck>
 </client>
 

tests/data/test1033

@@ -1,7 +1,7 @@
+<testcase>
 #
 # This case with an unexpected 1xx response used to cause a "hang" before the fix
 # got 7.19.0
-<testcase>
 <info>
 <keywords>
 HTTP

tests/data/test12

@@ -6,6 +6,7 @@ HTTP GET
 Content-Range
 </keywords>
 </info>
+
 # Server-side
 <reply>
 <data>
@@ -20,9 +21,9 @@ Content-Range: bytes 100-200/3527
 Connection: close
 Content-Type: text/html
 
-ink="#ffffff" vlink="#cccccc">
-<table width=100% cellspacing=0 cellpadding=0 border=0>
- <tr> 0123456
+..partial data returned from the
+server as a result of setting an explicit byte range
+in the request
 </data>
 </reply>