| Summary: | Getting wrong language with mscore | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Tony Wolfs <tony.wolfs> |
| Component: | RPM Packages | Assignee: | Thomas Spuhler <thomas> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | nic |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mscore | CVE: | |
| Status comment: | |||
|
Description
Tony Wolfs
2012-12-20 10:08:07 CET
what it the output of 'locale' ? Keywords:
(none) =>
NEEDINFO Output of locale is:
[tony@localhost ~]$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=th_TH.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=th_TH.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=th_TH.UTF-8
LC_NAME=th_TH.UTF-8
LC_ADDRESS=th_TH.UTF-8
LC_TELEPHONE=th_TH.UTF-8
LC_MEASUREMENT=th_TH.UTF-8
LC_IDENTIFICATION=th_TH.UTF-8
LC_ALL=
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US.UTF-8:en_US:en",
LC_ALL = (unset),
LC_PAPER = "th_TH.UTF-8",
LC_ADDRESS = "th_TH.UTF-8",
LC_MONETARY = "th_TH.UTF-8",
LC_SOURCED = "1",
LC_NUMERIC = "th_TH.UTF-8",
LC_TELEPHONE = "th_TH.UTF-8",
LC_MESSAGES = "en_US.UTF-8",
LC_IDENTIFICATION = "th_TH.UTF-8",
LC_COLLATE = "en_US.UTF-8",
LC_MEASUREMENT = "th_TH.UTF-8",
LC_CTYPE = "en_US.UTF-8",
LC_TIME = "en_US.UTF-8",
LC_NAME = "th_TH.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
[tony@localhost ~]$
--decided to change locale in MageiaControlCenter/System/Manage Localizatiion For Your System
and set my locale to<< Singapore >>
--log out--login
--checked <mscore > again...>>> Thai language was gone
--after fiddling around with various settings, I was NOT able to get mscore to display Thai again.
Note: The install media was the 3.7Gb DVD 64bit
Next:
I installed Mageia3 beta1 ( this time 1.1gb DVD ) on an other partition.
Same thing...mscore speas Thai
Next:
I checked on my 32bit hardware, mageia2 (two).
Same thing there.
Need any info, please ask.
thomas if you have any ideas Keywords:
NEEDINFO =>
(none) ideas?...yes ! 1-This afternoon I will install beta1 in virtualbox (if I can ) with Bangkok as my place where I stay. This < should > result in mscore being in Thai Then I will do same, but with US as my country where I stay. And see if there is a difference. 2--Musescore ( =mscore ) version 1.2 is out. Why not compile this version. If no problem, you don't have to worry about fixing v1.1 Unless of course...you want to learn something. your call! OK, problem ( partially ) located ! This works < only > if you can read Thai. On top of the screen it reads like this: File Edit Create Notes Layout.................................. Click Edit ( 2nd one ) scroll down to bottom : Preferences--click At the right < above> the RED text, it says<language>..click choose your language.....apply....OK Exit Mscore and open it again. All is OK now ( for the user ), not for the packager :-) I have as language <system> If you set it to system, what language do you get? The same one as your system? Status:
NEW =>
UNCONFIRMED This morning, after reading your question above, I booted into the same beta as where I had set the language to English . It is now set to < system > Rebooted into the other one...same...also set to < system > Suggestion ! If it was me, I would wait till Beta2 before I started chasing wind, based on: Once is a freak accident, two is a disaster ! Of course, it you decide different, I will assist you where I can No problem at all. Is this report still valid for Mageia 4 and Mageia 5 RC? Keywords:
(none) =>
NEEDINFO We have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
UNCONFIRMED =>
RESOLVED |