[SUGGESTION] Seperate app language and CV language

[FuturisticGoo]

Currently, changing the language in settings affects both the app's language and common voice language. I would like to use English as the application language while using another language in CV

[Sav22999]

Thanks for the feedback. As I said many times, the implementation would be complicated and confusing.

Maybe, in the future, I'll add this

[riveravaldez]

Just an opinion: probably better not to do. Considering the intention of Common Voice community effort, if someone is not comfortable using the app in X language, probably shouldn't record/validate audio phrases in such language, don't you think?

[Sav22999]

@riveravaldez good observation 🤔

[FuturisticGoo]

I would like to disagree on that. Many people (including me) use apps in English instead of our native language even though we are fluent in it.
This maybe because

1. Most apps don't support X language
2. Many terms used in apps are not (easily) translatable
3. Personally its easier for me to use these apps in English than in my language, not because I'm not comfortable with my language, but I prefer English here.

[MinekPo1]

+1

An additional argument is UX:

In my opinion changing the UI language can alter the UX quite significantly, decreasing familiarity.

Seperating off the CV language also allows to move the option to chose which language to use to the main menu and to remove the gray screen, caused by the app reseting. Bi/Polylingual contributors, such as my self and I assume @FuturisticGoo, would benefit from this change.

[riveravaldez]

Hi, @FuturisticGoo , about those:

• Most apps don't support X language

Here that's irrelevant, being the point precisely that X language is supported and therefore the UI changes to it.

• Many terms used in apps are not (easily) translatable

That would be an issue for UI translators, who, AFAIK, are not mentioning it. (Personally, I've been translating UIs from/to various languages for decades..., and for people who only know one language is always better a translation that the regular English formulation.)

• Personally its easier for me to use these apps in English than in my language, not because I'm not comfortable with my language, but I prefer English here.

I understand that and it's my case too, but again, I think that if one (myself) aren't comfortable enough with a language to navigate the UI shouldn't also being validating/recording content in CV's database...

Hi, @MinekPo1 , also:

In my opinion changing the UI language can alter the UX quite significantly, decreasing familiarity.

That's true. But the lack of visual familiarity (in terms of UI visual design) should be plentifully compensated for the words in a language the user domains.

Seperating off the CV language also allows to move the option to chose which language to use to the main menu and to remove the gray screen, caused by the app reseting.

In this case the issue would be the gray screen, which maybe could be avoided without the need to modify the app to separate UI/CV language.

Bi/Polylingual contributors, such as my self and I assume @FuturisticGoo, would benefit from this change.

Indeed.

Kind regards to both of you, sorry if I bothers... ^_^