Skip to content

Rationale for accurate location is too vague #402

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

Closed
1 task done
rimas-kudelis opened this issue Jan 17, 2025 · 1 comment · Fixed by #489
Closed
1 task done

Rationale for accurate location is too vague #402

rimas-kudelis opened this issue Jan 17, 2025 · 1 comment · Fixed by #489
Labels
enhancement New feature or request

Comments

@rimas-kudelis
Copy link
Contributor

rimas-kudelis commented Jan 17, 2025

Description

The rationale currently says the following:

Getting access to the current location needs permission for accurate location

This basically says "to get location, we need access to location". This is kind of self-referential and somewhat painful to translate.

Suggested implementation

I suggest to rewrite it to something like this:

Permission for accurate location is necessary to produce useful location reports

Additional information

There are a few other permission strings which could perhaps also be rewritten to use "X is needed/necessary for Y" form for consistency, but that's optional.

New request

  • I have checked that a similar feature hasn't been requested yet
@rimas-kudelis rimas-kudelis added the enhancement New feature or request label Jan 17, 2025
@mjaakko
Copy link
Owner

mjaakko commented Jan 17, 2025

Good point. These permission rationales are in need of better wording anyway. Feel free to update it in your translations - the translations don't have to be word-by-word

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants