Bug 6544 – USA localization displays distance in kilometers

Bug 6544 - (int-133672) USA localization displays distance in kilometers

(int-133672)
Summary:	USA localization displays distance in kilometers

Status:	RESOLVED FIXED

Product:	Map
Component:	General
Version:	5.0/(1.2009.42-11)
Platform:	All Linux

Importance:	Medium normal (vote)
Target Milestone:	5.0/(2.2009.51-1)
Assigned To:	unassigned
QA Contact:	map-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2009-12-03 16:21 UTC by Ian Monroe
Modified:	2010-01-14 12:27 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Ian Monroe (reporter) 2009-12-03 16:21:13 UTC

SOFTWARE VERSION:
1.2009.42-11.002

EXACT STEPS LEADING TO PROBLEM: 
1. In initial device setup, I selected my regional setting as English (USA).
2. Create a route in Ovi Maps.

EXPECTED OUTCOME:
The route length should be displayed in miles cause this is 'mercia and that's
how we roll. (Seriously all road signs and speed limits are in miles etc etc). 

ACTUAL OUTCOME:
Displays distance in kilometers.

REPRODUCIBILITY:
Always

OTHER COMMENTS:
This is one of the devices from the Maemo conference. I did flash the update.
But I suppose its possible that I don't have 100% of the localizations that
someone buying a N900 in the US will have?

Comment 1 Andre Klapper maemo.org

2009-12-04 13:59:05 UTC

This has been fixed in package
nokia-maps-ui 0.2.0-6+0m5
which is part of the internal build version
2.2009.49-2
(Note that 2009 is the year and the number after is the week.)

Any public update released with or after this build version will include the
fix.
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
For your information, Nokia does not announce release dates of updates in
advance.

Comment 2 Andre Klapper maemo.org

2010-01-14 12:27:19 UTC

The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update
version.