Re: Fallback behavior for "UNKNOWN" types -- proposed change

> I would suggest a slightly different rule, but maybe it comes out at the
> same place in the end: if we can't find a unique match treating UNKNOWN
> the way we do now, try again assuming it is TEXT (or at least string
> category). As you say, this is reasonable given that the original
> literal looked like a string.

Yeah, it is the same thing in the end, since the *only* place I've
changed in the code is the block which used to bail out when seeing a
"category conflict".

I assumed you would have an opinion ;) If anyone else has concerns
before seeing the effects of the change in the development tree, speak
up! Of course, if we see troubles after commit, things can change or
revert...

Oh, and UNKNOWNNUMERIC sounds like a plausible concept too.

- Thomas