X-Git-Url: http://gitweb.michael.orlitzky.com/?a=blobdiff_plain;f=doc%2Fman1%2Fhtsn-import.1;h=f36327c032532e08aee29c8869b2d74df5838aec;hb=ac72ee5fa40ec449efba2a0ae00d2944886a2f92;hp=47ca0d10d33a022d98d2bd78ad5d988dd8eeb209;hpb=f60eab7bde994afb9b2f727e56b0a635413bdd3b;p=dead%2Fhtsn-import.git diff --git a/doc/man1/htsn-import.1 b/doc/man1/htsn-import.1 index 47ca0d1..f36327c 100644 --- a/doc/man1/htsn-import.1 +++ b/doc/man1/htsn-import.1 @@ -280,7 +280,9 @@ an empty followed a non-empty one: .nf -We don't parse this case at the moment. +We don't parse this case at the moment, but we do recognize it and report +it as unsupported so that offending documents can be removed. An example +is provided as test/xml/newsxml-multiple-sms.xml. .IP \[bu] \fIOdds_XML.dtd\fR @@ -292,6 +294,18 @@ this leads to ambiguity in parsing. We therefore ignore the notes entirely (although a hack is employed to facilitate parsing). The same thing goes for the newer element. +We've also seen XML on the feed where the home/away starter elements +exist and have ID attributes but no content. For example, + +.nf + + +.fi + +We don't handle this at the moment, but since the starter id/name are +already optional (we just expect them to be present or missing as a +pair), it wouldn't be too hard to support. + .IP \[bu] \fIweatherxml.dtd\fR @@ -308,6 +322,12 @@ printed. If the \fI\-\-remove\fR flag is used, the file will be deleted. This prevents documents that we know we can't import from building up. +Another problem that comes up occasionally is that the home and away +team elements appear in the reverse order. As in the other case, we +report these as unsupported and then \(dqsucceed\(dq so that the +offending document can be removed if desired. An example is provided +as test/xml/weatherxml-backwards-teams.xml. + .SH DEPLOYMENT .P When deploying for the first time, the target database will most