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

Spaces are missing in languages list (UnitedStates UnitiedKingdom) #712

Closed
scootergrisen opened this issue Apr 9, 2017 · 13 comments
Closed
Milestone

Comments

@scootergrisen
Copy link

When Calamares starts the language list says "English (UnitedStates)" and "English (UnitiedKingdom)" so its seems spaces are missing.

@scootergrisen
Copy link
Author

About "NorweiganBokmal (Norway)":
There is a problem with the "a" in "Bokmal".
"a" should properly be "å".
Properly other problems with none a-z charaters i would guess.

@adriaandegroot
Copy link
Contributor

This is actually a Qt bug (or Calamares shouldn't be using the Qt locale information). The list of country names used to build QLocale data has no spaces in the country names (except for "European Union" and "Outlying Oceania"). It doesn't include accents either, like "Reunion". The list of languages is similarly inconsistent ("NorwegianNynorsk" vs "Western Frisian") and missing accents ("Hawaiian").

So it's something to take up upstream, I think.

@adriaandegroot
Copy link
Contributor

QTBUG 32487 (since 2013)

@gladhorn
Copy link

QTBUG-32487 is about pulse audio. https://bugreports.qt.io/browse/QTBUG-34287 is the right one.

hsitter added a commit to hsitter/calamares that referenced this issue Apr 5, 2018
This basically means we talk about localization in the respective
localized variant. e.g. "German (Germany)" ➡ "Deutsch (Deutschland)".

If geoip lookup failed or isn't configured for whatever reason it's a
stretch to expect the user to know english enough to find their own
language. Preferring the localized strings resolves this issue.

Additionally this happens to bypass calamares#712 respectively
https://bugreports.qt.io/browse/QTBUG-34287
as the native names are properly spelled. So, as long as Qt has localized
names the names will also be properly spelled.
@adriaandegroot
Copy link
Contributor

National names seem to be less derpy (at least in Qt 5.9) than the English names, so this has gone away as a side-effect of using the native language and country names.

@wxl
Copy link
Contributor

wxl commented Nov 3, 2018

I'm still seeing this in Lubuntu 18.10 and we have Qt 5.11. Given the date of your comment @adriaandegroot I would presume that Calamares 3.2.2 would be sufficient, but that does not play out that way. What am I missing?

@tsimonq2
Copy link
Contributor

tsimonq2 commented Nov 3, 2018

@wxl We have 3.2.1 in Disco as of right now; does this make a difference?

@wxl
Copy link
Contributor

wxl commented Nov 21, 2018

@tsimonq2 I'm confused by your message, as we had 3.2.2 in Cosmic and still do in Disco, though we have some more patches. Problem is still there with 0ubuntu4, which is the latest.

@tsimonq2
Copy link
Contributor

Ah, right.

@wxl
Copy link
Contributor

wxl commented Dec 12, 2018

@adriaandegroot Since I still see this as a problem, can we please reopen this? Or let me know what I'm lacking to see the correct behavior?

@adriaandegroot
Copy link
Contributor

It looks like the commit from @apachelogger wasn't actually merged :(

@adriaandegroot
Copy link
Contributor

@wxl the country name was fixed in the welcome page, but not in the locale page. @apachelogger 's patch did the latter as well, and I didn't take that over.

adriaandegroot pushed a commit that referenced this issue Dec 13, 2018
This basically means we talk about localization in the respective
localized variant. e.g. "German (Germany)" ➡ "Deutsch (Deutschland)".

If geoip lookup failed or isn't configured for whatever reason it's a
stretch to expect the user to know english enough to find their own
language. Preferring the localized strings resolves this issue.

Additionally this happens to bypass #712 respectively
https://bugreports.qt.io/browse/QTBUG-34287
as the native names are properly spelled. So, as long as Qt has localized
names the names will also be properly spelled.
@adriaandegroot adriaandegroot added this to the v3.2.3 milestone Dec 14, 2018
@adriaandegroot adriaandegroot modified the milestones: v3.2.3, v3.2.4 Jan 9, 2019
@wxl
Copy link
Contributor

wxl commented Apr 13, 2019

Just wanted to officially confirm this is doing what it's supposed to be doing in 3.2.4.

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

No branches or pull requests

6 participants