-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: use thousands of kilometres instead of "megameters" by default #1452
Comments
Yes that's true, we don't use megameters in practice. Makes sense to me to make a special rule for this in the function that finds the "best" prefix. I'm thinking about whether there are other units which have a similar case. Maybe time in seconds? (I don't use megaseconds but I do use milliseconds for example?). More ideas? |
Also:
Implementing #1314 would be nice and could address this issue as well :) |
In most contexts (scientific, civil engineering, except perhaps for astronomy and particle physics), I would expect that to be communicated as |
The km versus Mm issue is resolved by UnitMath's Choosing between |
We need a place to house all these unit things until there is a good long-term way to deal with them. In any case, the points raised here are all still valid. |
At present:
I understand why MathJS evaluates the expression this way, given the standard SI prefix system for metric units.
However, scientists & regular people are much more likely to use thousands of kilometers than megameters. It would be nice if MathJS could make a practical exception from jumping to the next largest SI unit in this case.
The text was updated successfully, but these errors were encountered: