Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.suse    |    Suse is actually not that bad    |    138,051 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 137,812 of 138,051    |
|    Carlos E.R. to bad sector    |
|    =?UTF-8?B?UmU6IE5haWxlZCAuLi5SZTogwqEgw5    |
|    19 Jul 23 13:40:26    |
      From: robin_listas@es.invalid              On 2023-07-19 13:14, bad sector wrote:       > On Wed, 19 Jul 2023 12:17:17 +0200, Carlos E.R. wrote:       >       >> On 2023-07-18 23:34, bad sector wrote:       >>> On 7/18/23 14:19, Carlos E.R. wrote:       >>>> On 2023-07-18 18:47, bad sector wrote:       >>>>> On 7/18/23 05:45, Carlos E.R. wrote:       >>>>>> On 2023-07-18 01:15, bad sector wrote:       >>>>>>> On 7/17/23 09:01, Carlos E.R. wrote:       >>>>>>>       >>>>>>>> Mine tries first the file "/usr/lib/locale/en_US.UTF-8/LC_TIME"       >>>>>>>> which does not exist. Then it tries       >>>>>>>> "/usr/lib/locale/en_US.utf8/LC_TIME", which in mine does exist.       >>>>>>>>       >>>>>>>> But yours is trying instead       >>>>>>>>       >>>>>>>> /usr/lib/locale/Default.UTF-8/LC_TIME       >>>>>>>> /usr/lib/locale/Default.utf8/LC_TIME       >>>>>>>> /usr/lib/locale/Default/LC_TIME       >>>>>>>>       >>>>>>>> which do not exist. Why is it trying those?       >>>>>>>>       >>>>>>>>       >>>>>>>> When I asked you for your locale, you pasted this:       >>>>>>>>       >>>>>>>> Leap-15.5 ~ 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="en_US.UTF-8"       >>>>>>>> LC_TIME=Default.UTF-8 <=========       >>>>>>>> LC_COLLATE="en_US.UTF-8"       >>>>>>>> LC_MONETARY="en_US.UTF-8"       >>>>>>>> LC_MESSAGES="en_US.UTF-8"       >>>>>>>> LC_PAPER="en_US.UTF-8"       >>>>>>>> LC_NAME="en_US.UTF-8"       >>>>>>>> LC_ADDRESS="en_US.UTF-8"       >>>>>>>> LC_TELEPHONE="en_US.UTF-8"       >>>>>>>> LC_MEASUREMENT="en_US.UTF-8"       >>>>>>>> LC_IDENTIFICATION="en_US.UTF-8"       >>>>>>>> LC_ALL=       >>>>>>>>       >>>>>>>>       >>>>>>>> That's the origin of your problem. Why do you have that?       >>>>>>>> Find that out, and change it to a proper one, and you should be       >>>>>>>> Ok.       >>>>>>>       >>>>>>> Also tried setting it in Yast to "en_US.UTF-8"       >>>>>>>       >>>>>>> On login I still get that Default.UTF-8       >>>>>>>       >>>>>>> did a content search on "Default.UTF-8"       >>>>>>>       >>>>>>> Bingo...       >>>>>>>       >>>>>>> ~/.config/plasma-localerc       >>>>>>       >>>>>> Aha. I thought so.       >>>>>       >>>>> In Artix, also with KDE :-) the file is only       >>>>>       >>>>> ==================       >>>>> [Formats]       >>>>> LANG=en_CA.UTF-8 ==================       >>>>>       >>>>>       >>>>> The above must have come from clicking Pangnirtung as a place just to       >>>>> throw too long noses off a bit       >>>>       >>>> Ar you using the same home folder in openSUSE? Because openSUSE       >>>> doesn't have "en_CA.UTF-8".       >>       >> I see "/usr/share/locale/en_CA", and en_GB and en_US and others, just no       >> utf8 variants. Seems to be about the messages only.       >>       >> I also see       >>       >> /usr/lib/locale/en_CA /usr/lib/locale/en_CA.utf8       >       > today is slackware day but I mounted my Leap partition and it's the same       > here       >       >       >       >> just not "en_CA.UTF-8", which could thus just fail.       >       >       > I'm just a passenger on this ship but it seems to me that the entire       > locale deal is gettin' a bit too 'lossy', it may be time to clean up the       > whorehouse, set some syntax rules and enforce them! When one is TS-ing       > and finds an output list of a dozen "en_US.UTF-8" in quotes but one that       > says en_US.utf8 and without quotes then one tends to think that that's       > where the problem is. Not so, it seems, for 'starters' :-(                     It get worse. Plasma has its own locale system, different than the rest       of the system. You can choose a locale in settings that has no       corresponding "locale" tree in the system. Maybe it works in native KDE       tools, but not in others.              And Gnome uses a different method. I believe that the file .i18n works.              --       Cheers, Carlos.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca