`  == Finally a fix for range precisions == Amidst all the turmoil in the Lua Convert sideshow, I have been able to focus on real user requests, such as to fix the default precision in ranges to seem more logical. For years, we have heard people complain about the excessive rounding, such as: ::* {{convert|43|-|45|lb|kg}} → <both results same ::* {{convert|861|-|862|lb|kg}} → 861–862 pounds (391–391 kg) <both same Well after asking people, for months/years, to help think of solutions, it finally dawned on me that a range such as ``800-800.06`` implicitly means the number ``800`` is ``800.00`` but people write ``800`` as a shorter numeral, and the template needs to switch gears and consider the precision of 800 to match 800.06 when inside the range, and then people will get the results they expect. This solution has worked, and the /sandbox version of {Convert/Dual/rnd} will give logical results in the various cases: ::* {{convert|43|-|45|lb|kg }} →  ::* {{convert|860|-|970|lb|kg}} → 860–970 pounds (390–440 kg)  ::* {{convert|861|-|862|lb|kg}} →  ::* {{convert|800|-|800.06|lb|kg}} → 800–800.06 pounds (362.87–362.901 kg) Now, we finally have a comprehensive solution, where multiples of ten (or 100) still round to the nearest ten, but consecutive numbers 860–861 will default to an extra digit of precision to show the difference between numbers, both treated as precision ``1`` when close in value. These issues are explained in: ::* Template:Convert/Dual/rnd/sandbox - auto-adjusts precision of a range So, the next time someone has a list of ranges with close values, then they could use {convert/old} for each range to auto-adjust the precision. We might ask for further help in fixing the Lua Convert by posting to wp:Lua_requests, or experiment with a Module:Convert/sandbox2. Meanwhile, I will run some wider tests, and then install this fix for range precision. Any other concerns? - `