Skip to content
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

LOCALISATION: For non-English languages, the Audio Beacon pane still shows distances in "ft" or "mi" when using imperial distances #55

Open
StevenAbrams opened this issue Aug 22, 2023 · 1 comment
Assignees
Labels
bug Something isn't working Localisation Issues relating to localising of strings Priority 3 MEDIUM: The issue should be addressed soon, but it's not critical to the immediate goals. Severity 4 LOW: The issue has minimal impact on functionality or user experience.

Comments

@StevenAbrams
Copy link

Build: 1.0.0 (9)

Repro Steps:

  1. Set the language to non-English e.g., Spanish
  2. Make sure in Settings that distances are in Imperial
  3. Set a beacon on a nearby POI that is in the order of feet away
  4. View the Audio Beacon pane and view the distance

Expected Results:
The abbreviation for feet (ft) and miles (mi) are localised

Actual Results:
The abbreviation for feet (ft) and miles (mi) are NOT localised

@StevenAbrams StevenAbrams added bug Something isn't working Priority 3 MEDIUM: The issue should be addressed soon, but it's not critical to the immediate goals. Severity 4 LOW: The issue has minimal impact on functionality or user experience. labels Aug 22, 2023
@StevenAbrams StevenAbrams added the Localisation Issues relating to localising of strings label Aug 22, 2023
@steinbro
Copy link
Member

This appears to be a limitation in the translation text: the translation for distance.format.ft is "ft" for all locales except French and Norwegian. We'll need input from translators for the rest of the languages in order to correct these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Localisation Issues relating to localising of strings Priority 3 MEDIUM: The issue should be addressed soon, but it's not critical to the immediate goals. Severity 4 LOW: The issue has minimal impact on functionality or user experience.
Projects
None yet
Development

No branches or pull requests

2 participants