I believe the problematic code could only be reached when reading buggy versions (i.e., with duplicate ids) of the legacy FlightGear XML non-master l10n files, which is why we haven't tripped on it so far.
I believe the problematic code could only be reached when reading buggy versions (i.e., with duplicate ids) of the legacy FlightGear XML non-master l10n files, which is why we haven't tripped on it so far.