Up to now, there are only a few rare situations to input a value with a unit into in QMS (e.g. elevation or proximity of waypoints). Therefore, units where not translated to local spelling. This will change with the upcoming advanced filtering. Here, the user has to formulate search queries in the local language used in QMS. While this is not a problem for languages written in Latin-1, it will be a problem for the Russian/Cyrillic version. To avoid conflicts with wrongly written units in search queries I propose to extend the list of units in IUnit.cpp by the Cyrillic equivalents for length, speed, time, … (I can provide such a list). These extended units can then be recognized in extended search queries and unit conflicts (Russian text with Latin-1 unit required but Russian unit given) won’t happen. There is no need to use Russian units elsewhere in QMS (thus, as currently, no translation of units).
Issue #474 resolved