Hi Andrzej
what is the reason for using "dirty names" for sorting? You have this comment in code:
Because I believed that was the correct way to do it.
// We sort on the dirty name (ie with the Garmin shield codes) although those codes do not // affect the sort order. The string for mdr15 does not include the shield codes.
This is because it shouldn't make much difference: if A sorts before B then A will also sort before <shield>B and <shield>A will sort before B. Different kinds of shields do (or can) sort among themselves <shieldA>A and <shieldB>A can sort in that order, but would be entirely overridden by what comes next so <shieldB>A would be before <shieldA>B.
I have tried to swap "dirty names" with "clean names" and search seems to work in Mapsource. Maybe it depends on label coding?
So that is interesting, it really shouldn't make any/much difference in practice (it may have done when I wrote the comment). So we need to find out what difference it makes to the sort order.
Processing of clean names would be easier.
Maybe, but it not about what is easier ;) If you could work out what the difference is that would be great. ..Steve