Fixing inverseLocate so it hopefully works now. I was advancing on the wrong thing in directInverseLocate, and my upper bound on permissible inputs in inverseLocate was super-wrong (because there's lots of space between texts in string coordinate space)