Fix registration stride mappings with a non-zero offset.
registrations.js would miscalculate the end of the address range in these cases, causing the mapping to be skipped for addresses that we could have handled. This specifically affected German registrations beginning with D-AP through D-AZ and D-BP through D-BZ
This commit is contained in:
parent
35299c47ba
commit
d0094d5abd
|
@ -92,7 +92,7 @@ registration_from_hexid = (function () {
|
||||||
mapping.end = mapping.start - mapping.offset +
|
mapping.end = mapping.start - mapping.offset +
|
||||||
c1 * mapping.s1 +
|
c1 * mapping.s1 +
|
||||||
c2 * mapping.s2 +
|
c2 * mapping.s2 +
|
||||||
c3 - mapping.offset;
|
c3;
|
||||||
} else {
|
} else {
|
||||||
mapping.end = mapping.start - mapping.offset +
|
mapping.end = mapping.start - mapping.offset +
|
||||||
(mapping.alphabet.length - 1) * mapping.s1 +
|
(mapping.alphabet.length - 1) * mapping.s1 +
|
||||||
|
|
Loading…
Reference in a new issue