Some binary and hexadecimal values are still printed with the wrong number of characters. The implementation from issue #17834 only takes the lowest size range value into consideration, so ranges like SIZE (0 | 2 | 4) or similar only require a minimum printing length of 0. Hence, in the current implementation '05'H would print to '5'H instead.

The solution to this issue is probably to only consider the size range values larger or equal to the initial value specification. In such a solution, no padding zeros would ever be removed, but padding might still be added in some cases.

Thanks to M.S.Thiraviyakumar for reporting this and providing a patch.