Bug 1228263 - Unable to set locale to Australian english en_AU
Summary: Unable to set locale to Australian english en_AU
Status: RESOLVED WORKSFORME
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Leap 15.6
Hardware: 64bit Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-24 07:33 UTC by Brian Butler
Modified: 2024-07-24 18:44 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Butler 2024-07-24 07:33:39 UTC
There is no option to set my system locale to en_AU even though I can set my time zone to Australian CST.
Comment 1 Stefan Hundhammer 2024-07-24 18:44:33 UTC
This is not a bug, it's a mere statement of fact.

YaST does not support setting a system locale, just the language, and the time zone. Both are separate YaST modules in the YaST control center.

There are two variants of English to choose from, English (US) and English (UK), both with messages for the system and for applications in different spelling. We offer the languages that have a significant amount of messages (usually translations) for YaST and related sysadmin subsystems.


All that does NOT affect any other locale settings such as LC_CTYPE, LC_NUMERIC, LC_TIME, LC_COLLATE, LC_MONETARY, LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT, LC_IDENTIFICATION.

You can use the YaST sysconfig editor or simply edit /etc/sysconfig/language to set the other ones in their RC_LC_xxx variant, but in almost all cases this has little or no effect at all: The desktops tend to override that with their own applets anyway, so you are much better off using the locale settings of your desktop, be it KDE Plasma, GNOME, Xfce or whatever.

If you have a more complex setup, you might want to set them individually in your shell startup files (~/.bashrc etc.).

See also bug #1228104.