Hi Vasily,
I've given it a thorough look over as a possibility to lookup region
codes via region name, but this won't work for our vast traffic for the
following reasons:
- we handle not far from 1/10th of google's global traffic, therefore
*every* lookup we do needs to really well optimised. Something taking
1ms more than before when you're handling 4k requests a second creates a
4 second backlog in processing requests coming after (ok, those 4k
aren't
location.gp traffic, but you get the idea)
- we would need to create fuzzy lookups on a varchar(255) mysql field,
rather than an int(2) in mysql, which is 1. mysql intensive, 2. 3ms
longer on non-cached mysql lookups (live tests on MM csv imported into
mysql)
- the region name lookup actually results in a 2% no return because of
the mismatch in region names (accents, no accents, different spellings
etc like you pointed out)
For us handling this amount of lookups, these slowdowns to return an
abbreviation for countries we don't hold abbreviations for in the actual
live data is too much of a trade-off to be fully 100% global.
So unfortunately, for these countries (like RU), we will push the onus
onto the end user to map these. It sounds like you were able to.
Hopefully others in your situation can do the same!
Sorry I couldn't find a simple solution for this - I did honestly try!
Best
Andy