Search comparison of custom fields

Is it just me or does RT 3.0.4 use lexicographical comparison instead
of the sort order when evaluating a query condition relating to a
custom field? I.e., if I have a custom field F with values A (sort
order 3), B (sort order 2), and C (sort order 1), and I search for “F
greater than B” I get all the tickets where F = C, not all the
tickets where F = A.

meeroh | KB1FMP

A: Because it reverses the logical flow of conversation.
Q: Why is top posting frowned upon?