-
Notifications
You must be signed in to change notification settings - Fork 275
-
Notifications
You must be signed in to change notification settings - Fork 275
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
Short distances and elevation with statute units #626
Comments
I think there should be 3 options: metric, imperial (aka statute) or both, because different people have different needs. Not sure why you want to make this not-configurable: it must be. Also, it is not clear why short distances should be treated differently than longer distances. In my opinion everything should be treated the same. Perhaps elevation might be treated differently (I prefer not, but I can see the point), but why short distances? |
I want to keep the current option: Km (should be named metric) and Miles (should be named Imperial or Statue). Short distances are used to configure workouts and get better audio cues (re there cues for how much remains?) I changed the special case for '0' to display as km/mi to make it more natural when creting manual activities. |
The proper spelling is statute not statue, see e.g. https://en.wikipedia.org/wiki/Mile#Statute_mile My third option is both, i.e. being able to get some/all the distance/speed in both units. Still, I am not sure why short distances should be configured different than long distances, let alone hard coded to (say) metric and confuse people who only know imperial (or viceversa). |
A temporary (?) solution could be to only present Imperial (avoiding to misspell statute!), in miles decimal only, then it is like @daviddelvento suggests? |
I'm actually suggesting this being (manually) localized like everything else. Let's aside my "third option" for the the time being because I think it's too advanced and for a smaller user base (even if that user base includes myself, so I'm very interested into it). If we do what you're suggesting I think it'd be confusing for metric people who select metric system everywhere in their phones to see these numbers in miles. Now if localize short distances and elevation is too complicated to do (why????), feel free to do what you said. |
But if this is to be customized, how to present it? Unit (new subpage): |
I'm suggesting:
and to be applied for both long or short distance with the proper adjustments made automatically. For example, if one sets metric: If one sets imperial: Optionally, if not too much of a hassle, when one sets both imperial and metric: both the metric and imperial numbers will be shown in live numbers, tables etc. Unless you plan to considerably increase the font, this will not be a problem since most of the screen of my phone (the smallest screen with the lowest resolution I could buy) is mostly empty. |
Then feet it is "Double" printouts are difficult to handle, it would require a very special setup. |
RU is currently presenting km/m also with miles settings in some situations.
I have suggested changing that in PR #624
However, Short distances (less than a mile) are presented as 'm' still.
Changing that will require translation changes, so there are some steps required.
At this point, I would prefer to not make the setting configurable.
Also, I would not like to present in combined units, like miles and yards.
How to present short distances, in yard or feet or even keep meters?
There is no presentation of elevation right now, if that is added (for instance in graphs), is it OK to use the short distance setting?
The text was updated successfully, but these errors were encountered: