"Nm" or "nm" is an extremely common abbreviation for the unit of torque called the Newton-metre. I often search things like "105nm to ft lb" because it's faster than finding my bookmark for a calculator website.
With the given example of "105nm to ft lb", Kagi returns:
= 1.4 times 10 to the negative 18 foot pounds‐force
Which is many magnitudes from the correct answer (77 ft lb) because Kagi reads that as nanometres pound-force, we will come to that.
Image 2: Notably capitalising the "N" in "105Nm" does not give any "Kagi Calculator" result at all, just web results. I figured it would be case-insensitive.
If I write ""105newton metres to ft lb", Kagi returns the correct result:
= 77.44 ft lbf (foot pounds-force)
Me and most people who regularly use torque units don't want to write "Newton metre" every time we search, if we don't have to write out "foot pounds-force" or "pound feet" [N.b. below]. Above we saw the unit part of the phrase "105Nm" is case sensitive. Can that be enabled to mean Newton-metres?
Apparently the "nm" unit is getting interpreted as nanometres [implied-pounds]-force.
Indeed the opposite calculation - "105ft lb to nm" gives an answer in nanometre pounds-force. See below image 2.
With the context of "to ft lb" meaning a torque-to-torque conversion is most likely, can Kagi read this "nm" unit as Newton metres? Then if the calculation is "400nm to mm", Kagi can assume the user probably wants to convert distance-to-distance and give the right result in millimetres.
N.b. yes, we often speak lb-ft and ft-lb interchangeably but are technically different units, but never mind that for casual use.
