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

[Feature Request] In-App Localization / UI Language Selection #192

Closed
historical-theology opened this issue Aug 30, 2019 · 2 comments
Closed

Comments

@historical-theology
Copy link

historical-theology commented Aug 30, 2019

It would be a boon to people studying the Bible worldwide to have the option to select the localization / UI language inside the BibleTime application rather than relying on the system's localization settings.

Since the localization settings are already stored locally for BibleTime's use (e.g. "/usr/share/bibletime/locale/" in Linux), I would not imagine this to be a difficult feature to implement.

Here is where I imagine this option fitting:
Settings --> Configure BibleTime --> Localization (UI)
(perhaps directly above or directly under the "Language for names of biblical books" option)

If you would be willing to add this as an option, then BibleTime would be worth translating into any language that lacks proper operating system-wide support.

For one example, if the feature should be added, then I would be happy to start a Latin translation project for BibleTime on transifex.

Thank you for your consideration.

God bless.

@ngaretou
Copy link

ngaretou commented Jul 3, 2020

I second this one! Users aren't always able to get the OS that matches their preferred computing language - used computers in the country we live in often come from the US in English and then can't be changed (unless running Windows Pro), so in-app localization choice is a necessity for our target audience. Thanks for considering this!

@jaakristioja
Copy link
Member

I agree. However, since this is actually a duplicate of #1, which was once marked WONTFIX, it makes sense to reopen the original issue instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants