|
A couple of instances where fielders are not identified:
[226-11857] this is popped up...
on the infield, left side...
[241-14686] camps under the ball...
[246-12346] and he hauls it in...
one down...
and
[226-11860] it's in the air...
on the infield, left side...
[241-14686] camps under the ball...
[246-12330] he retires Hee Seop Choi with the catch...
three down...
In both cases, Text_Object id="14686" text="[% game fielder of] camps under the ball..." is not getting a return from its token. Perhaps because [% game fielder of] is the fielder nearest to the ball on outfield plays, and both plays above are infield plays?
Several examples of wrong preposition use. Here's one:
Strike three on a [315-8881] exploding 97mph fastball....
Problems such as this occur because prepositions are not restricted, as they should be, to the final Category in a sequential Category call. In the example above, the Category producing the text "Strike three on a" leads via a pitch type token to Category 315. All text_objects in 315 beginning with a vowel will therefore produce the wrong preposition error. A simple cure would be to delete or alter all text-objects in 315 so that none begin with a vowel. A better and less restrictive cure (but needing more work) would be to remove the preposition from the calling Category and add the correct prepositions to the objects in the final Category. So, all Categories producing text such as "Strike three on a" are changed to "Strike three on", and the text objects in 315 become
6406 "a blazing fastball"
6414 "an overpowering heater" etc....
Ian
|