In sortable tables:

In sortable tables:
* (bug 8063) Use the content language digit transform table.
* Don't recognise C-style hexadecimal notation as a number, that feature never actually worked.
* Be more forgiving about things that look like numbers but turn out not to be. Sort them stringwise.
* Optimised ts_resortTable by having it calculate the sort keys at the start, and then using a single trivial comparison function. There are potentially many more comparisons than rows. Observed factor of 2 speedup.
* Use RegExp.test() instead of String.match() when a true/false value is desired, as recommended by the Mozilla reference