On 27/02/2024 20:59, Gary Dale wrote:
The en_GB seems to be coming from Plasma 5's Region & Language settings.
However I see the message that it is "unsupported", which seems
appropriate.
en_GB is missed in the output of "locale -a" you posted. I have no idea
On 2024-02-26 22:47, Greg Wooledge wrote:
On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote:
On 2/26/24 20:28, Gary Dale wrote:
$locale
locale: Cannot set LC_CTYPE to default locale: No such
file or directory
locale: Cannot set LC_MESSAGES to default locale: No
such file or directory
On 2024-02-26 22:47, Greg Wooledge wrote:
On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote:
On 2/26/24 20:28, Gary Dale wrote:
$locale
locale: Cannot set LC_CTYPE to default locale: No such
file or directory
locale: Cannot set LC_MESSAGES to default locale: No
such file or directory
om testing but it fails to start. When I run it from the
command line, I get:
$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec:
1.2"
"Using locale: en_GB"
terminate called after throwing an insta
On 2024-02-26 21:29, Max Nikulin wrote:
env | grep 'LC_\|LANG'
systemctl --user show-environment | grep 'LC_\|LANG'
$ env | grep 'LC_\|LANG'
LANGUAGE=en_GB
LC_MONETARY=en_CA.UTF-8
LANG=iu_CA.UTF-8
LC_MEASUREMENT=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=en_CA.UTF-8
LC_NUMERIC=en_CA.UTF
On Tue, Feb 27, 2024 at 08:48:27AM -0500, Gary Dale wrote:
> > You've got three different locales mentioned here:
> >
> > iu_CA.UTF-8
> > en_GB
> > en_CA.UTF-8
> >
> > Either generate the two that you're missing, or stop using them.
>
> I'm trying to stop using them. That's the point. How do I g
On 2024-02-26 20:43, Greg Wooledge wrote:
On Mon, Feb 26, 2024 at 08:28:01PM -0500, Gary Dale wrote:
$locale
locale: Cannot set LC_CTYPE to default locale: No such file
or directory
locale: Cannot set LC_MESSAGES to default locale: No such
file or directory
locale: Cannot set LC_ALL to default
On 2/26/24 22:47, Greg Wooledge wrote:
On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote:
On 2/26/24 20:28, Gary Dale wrote:
$locale
locale: Cannot set LC_CTYPE to default locale: No such
file or directory
locale: Cannot set LC_MESSAGES to default locale: No
such file or directory
locale
On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote:
> On 2/26/24 20:28, Gary Dale wrote:
> > > > > > $locale
> > > > > > locale: Cannot set LC_CTYPE to default locale: No such
> > > > > > file or directory
> > > > > >
n I run it from the command
line, I get:
$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
what():
On 27/02/2024 08:28, Gary Dale wrote:
$locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
What desktop environment do you use? Have you checked its settings? Did
you choose locale in
On Mon, Feb 26, 2024 at 08:28:01PM -0500, Gary Dale wrote:
> > > > > $locale
> > > > > locale: Cannot set LC_CTYPE to default locale: No such file
> > > > > or directory
> > > > > locale: Cannot set LC_MESSAGES to default locale: No s
ine, I get:
$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_c
ing Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
[1]+ Aborted
;notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
[1]+ Aborted (core dumped) jami
garyd
E, version: 5.27.10, spec: 1.2"
"Using locale: en_GB"
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
[1]+ Aborted (core dumped) jami
garydale@transponder:~/mnt/archives/2024/Lions
I'm running Debian/Trixie on an AMD64 system. I've installed jami from
testing but it fails to start. When I run it from the command line, I get:
$jami &
[1] 7804
$ Using Qt runtime version: 6.
4.2
"notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2&qu
Feb 20, 2022, 05:31 by loca...@tutanota.com:
> Hi,
>
> So I wanted to add the RU locale but for some reason that doesn't seem to
> work.
>
> Any ideas? Thanks
>
>
> # cat /etc/debian_version && uname -a
> 11.2
> Linux srv07 5.10.0-11-amd64 #1 SMP Deb
Hi,
So I wanted to add the RU locale but for some reason that doesn't seem to work.
Any ideas? Thanks
# cat /etc/debian_version && uname -a
11.2
Linux srv07 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64
GNU/Linux
# locale -a
C
C.UTF-8
en_US.utf8
POSIX
# loc
OS: Bullseye, fully updated.
Problem: When logged in Simplified Chinese locale, the date and time are
shown in English. They are correctly shown in Chinese characters in Ubuntu
20.04.
On 6/23/21 12:16 PM, Andrei POPESCU wrote:
Try asking on debian-i18n.
Thanks for your suggestion, I will ask on debian i18n
--
Robbi Nespu
D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu
On Mi, 23 iun 21, 11:53:47, Robbi Nespu wrote:
> Hello Debian!
>
> TLDR; How I can generate my own dictionary and spell checker file?
Try asking on debian-i18n.
> I from Malaysia, we use Malay (Bahasa Melayu) as our primary language but we
> don't mind using English for user-interface of softwa
Hello Debian!
TLDR; How I can generate my own dictionary and spell checker file?
I from Malaysia, we use Malay (Bahasa Melayu) as our primary language
but we don't mind using English for user-interface of software and
communication. I think most of us are comfortable with English because
dire
t; > > >
> > > > LANG=en_SE.UTF-8
>
> There is no such locale in the "dpkg-reconfigure locales" list on
> my buster system.
>
> │ Locales to be generated:
> │ │
On fredag 15 januari 2021 kl. 13:56:17 CET Andrei POPESCU wrote:
> On Jo, 14 ian 21, 19:06:34, Rasmus MK wrote:
> > During the Debian installation (graphical) I configured my locale to be
> > "en_SE.UTF-8".
>
> Can you explain how you managed to do that?
>
>
On Vi, 15 ian 21, 17:45:06, Rasmus MK wrote:
> On fredag 15 januari 2021 kl. 13:56:17 CET Andrei POPESCU wrote:
> > On Jo, 14 ian 21, 19:06:34, Rasmus MK wrote:
> > > During the Debian installation (graphical) I configured my locale to be
> > > "en_SE.UTF-8&qu
ebian installation (graphical) I configured my locale to be
> > "en_SE.UTF-8".
> > Recently a python script crashed with the error message "unsupported
> > locale
> > setting" after trying to set LC_ALL to an empty string and I cannot get it
> > to work
On Fri, Jan 15, 2021 at 09:14:53AM +, Rasmus MK wrote:
> > > I use KDE. If I look in Settings -> Regional Settings -> Format it says
> > > en_SE.UTF-8 (no adjustments).
> > > LANG=en_SE.UTF-8
There is no such locale in the "dpkg-reconfigure locales&quo
On Jo, 14 ian 21, 19:06:34, Rasmus MK wrote:
>
> During the Debian installation (graphical) I configured my locale to be
> "en_SE.UTF-8".
Can you explain how you managed to do that?
Right now im trying the latest daily (for arm64, but it shouldn't
matter) and if I sele
On Thu 14 Jan 2021 at 19:06:34 (+), Rasmus MK wrote:
>
> I'm looking for help in understanding how locales work and how to configure
> my
> system running Debian Testing.
>
> During the Debian installation (graphical) I configured my locale to be
> "en
n see now that I have one locale in the console environment and one in the
desktop environment. this clears out some confusion. Thank you.
>
> If your actual issue is "when I'm working inside my python virtual
> environment, shit breaks" then I'm afraid I can't
Hi list,
I'm looking for help in understanding how locales work and how to configure my
system running Debian Testing.
During the Debian installation (graphical) I configured my locale to be
"en_SE.UTF-8".
Recently a python script crashed with the error message "unsuppo
On Thu, Jan 14, 2021 at 07:06:34PM +, Rasmus MK wrote:
> Recently a python script crashed with the error message "unsupported locale
> setting" after trying to set LC_ALL to an empty string and I cannot get it to
> work with the en_SE.UTF-8 locale.
Setting any of the L
On 2021-01-14 20:06, Rasmus MK wrote:
Hi list,
I'm looking for help in understanding how locales work and how to configure my
system running Debian Testing.
During the Debian installation (graphical) I configured my locale to be
"en_SE.UTF-8".
Recently a python script crashed
On Wed 14 Oct 2020 at 13:19:15 (-0500), Mike McClain wrote:
> On Tue, Oct 13, 2020 at 04:46:56PM -0400, Cindy Sue Causey wrote:
> > On 10/13/20, L Godioleskky wrote:
> > > App localepurge eliminates some, but far from all of these un-needed files
> >
> > What's it leaving behind that you would lik
On Tue, Oct 13, 2020 at 04:46:56PM -0400, Cindy Sue Causey wrote:
> On 10/13/20, L Godioleskky wrote:
> > App localepurge eliminates some, but far from all of these un-needed files
>
> What's it leaving behind that you would like to see additionally
> purged? If there's not a known tweak, flag, or
On 10/13/20, L Godioleskky wrote:
> There are hundreds of MBytes of wasted disk space due to un-needed locale
> files.
> Most users only use one or two languages, so why should they devote huge
> amounts of disk space to locale files they dont need/use ?
>
> App localepurge el
There are hundreds of MBytes of wasted disk space due to un-needed locale
files.
Most users only use one or two languages, so why should they devote huge
amounts of disk space to locale files they dont need/use ?
App localepurge eliminates some, but far from all of these un-needed files
On Sb, 15 feb 20, 06:11:30, Barney G wrote:
> In plasma KDE in system configuration->Personalization->Regional
> Settings->Formats->Detailed Settings you cannot chose mk_MK. This is a bug
> or it is feature?
Try running 'dpkg-reconfigure locales' and enabling mk_MK.UTF-8.
Kind regards,
Andrei
--
In plasma KDE in system configuration->Personalization->Regional
Settings->Formats->Detailed Settings you cannot chose mk_MK. This is a
bug or it is feature?
Barney G.
On Fri, Dec 27, 2019 at 06:00:44PM +0100, Alessandro Barbieri wrote:
> With htop, I noticed that the processes in my Buster installation load the
> aa_DJ locale while I have configured only the Italian locales. Is it known?
> Should I file a bug?
Run "dpkg-reconfigure locales&qu
With htop, I noticed that the processes in my Buster installation load the
aa_DJ locale while I have configured only the Italian locales. Is it known?
Should I file a bug?
https://www.mycause.com.au/page/183259/a-smile-will-change-a-day-love-that-changed-my-world
From: davidson
Sent: Saturday, 11 August 2018 8:02 PM
To: debian-user@lists.debian.org
Subject: how to change default locale [was Re: How to Fix ACPI Error :
Namespace
https://www.mycause.com.au/page/183259/a-smile-will-change-a-day-love-that-changed-my-world
From: davidson
Sent: Saturday, 11 August 2018 8:02 PM
To: debian-user@lists.debian.org
Subject: how to change default locale [was Re: How to Fix ACPI Error :
Namespace
quot;) and
the question that you ask here, I am afraid I am not enough of a
wizard to figure it out.
Anyway, if I were you, this is how I would try to change the default
locale on my system:
As root I would do
# dpkg-reconfigure locales
I would expect this to
1. allow me to interactively select
On 2018-07-11 17:38:18 +0100, John wrote:
> >> What is the output of "locale" and "locale -a" on this machine?
> snout:~> locale
> LANG=en_GB.UTF-8
> LANGUAGE=en_GB:en
> LC_CTYPE="en_GB.UTF-8"
> LC_NUMERIC="en_GB.UTF-8"
> LC_TI
On 7/11/2018 6:38 PM, John wrote:
What is the output of "locale" and "locale -a" on this machine?
snout:~> locale
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB
>> What is the output of "locale" and "locale -a" on this machine?
snout:~> locale
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY=&
On 2018-07-10 19:50:40 +0100, jpff wrote:
> I should have added that I have been running this macine for years
> and this started recently, a month or two I think.
What is the output of "locale" and "locale -a" on this machine?
--
Vincent Lefèvre - Web: <
7;m not sure, but try running locate on your locale e.g.:
> >
> > $ locate en_US.UTF-8
> > /usr/share/X11/locale/en_US.UTF-8
> > /usr/share/X11/locale/en_US.UTF-8/Compose
> > /usr/share/X11/locale/en_US.UTF-8/XI18N_OBJS
> > /usr/share/X11/locale/en_US.UTF-8/XLC_L
ocale: LC_CTYPE: cannot change
> locale (en_US.UTF-8)
> when compiling, and
>
> (firefox-esr:11622): Gtk-WARNING **: Locale not supported by C library.
> Using the fallback 'C' locale.
>
> from firefox. There are other similar. I have not got this problem
advice about messages I am getting
about locales I thought I did what was suggested but I still see
CC libclamav_internal_utils_nothreads_la-strlcat.lo
../libtool: line 1748: warning: setlocale: LC_CTYPE: cannot change
locale (en_US.UTF-8)
when compiling, and
(firefox-esr:11622): Gtk
e 1748: warning: setlocale: LC_CTYPE: cannot change
> locale (en_US.UTF-8)
> when compiling, and
>
> (firefox-esr:11622): Gtk-WARNING **: Locale not supported by C library.
> Using the fallback 'C' locale.
>
> from firefox. There are other similar. I have not got t
A short time ago I sought your advice about messages I am getting
about locales I thought I did what was suggested but I still see
CC libclamav_internal_utils_nothreads_la-strlcat.lo
../libtool: line 1748: warning: setlocale: LC_CTYPE: cannot change
locale (en_US.UTF-8)
when compiling
On Tue, 05 Jun 2018 18:30:02 +0200, John wrote:
> Whenever I run emacs on my 64bit Debian (Jessie) machine via ssh I see
>
> (process:20589): Gtk-WARNING **: Locale not supported by C library.
> Using the fallback 'C' locale.
>
> root@snout:~# printenv (e
On Tue, Jun 05, 2018 at 05:25:52PM +0100, John wrote:
> Whenever I run emacs on my 64bit Debian (Jessie) machine via ssh I see
>
> (process:20589): Gtk-WARNING **: Locale not supported by C library.
> Using the fallback 'C' locale.
>
> root@snout:~# printenv
Whenever I run emacs on my 64bit Debian (Jessie) machine via ssh I see
(process:20589): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
root@snout:~# printenv (edited)
LANG=en_GB.UTF-8
XTERM_LOCALE=C
XTERM_VERSION=XTerm(312)
LANGUAGE=en_GB:e
Hi,
Morten W. Petersen :
> need to hack a bit on terminal code
This is not only about terminals but also about any other
program or module which shall process your UTF-32 text.
You would have to set up a complete UTF-32 capable system
while everything around it expects UTF-8.
For example, in C l
Le decadi 20 frimaire, an CCXXIV, Morten W. Petersen a écrit :
> Hm. But how would I go about setting up a locale that is in fact UTF-32?
You do not.
Locales are a bad API, do not use it except for the most basic tasks, and
this is not a basic case.
Regards,
--
Nicolas Geo
On Sun, Nov 29, 2015 at 4:04 PM, Nicolas George wrote:
> Le nonidi 9 frimaire, an CCXXIV, Morten W. Petersen a écrit :
> > I was looking for a locale that would enable me to putwchar a 32-bit
> > Unicode character to stdout and have things handled correctly,
> > automatic
Le tridi 13 frimaire, an CCXXIV, to...@tuxteam.de a écrit :
> Yeah, agreed, that's quote-worthy. Nicolas: can I put that into my
> quotations book? With attribution, of course!
No problem. I am flattered.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Dec 03, 2015 at 03:25:38AM -0500, Neal P. Murphy wrote:
> On Thu, 3 Dec 2015 09:01:40 +0100
> Nicolas George wrote:
>
> > (Sun is also responsible for making java's char type 16-bits and strings
> > UTF-16. This is another case of headdesk, o
On Thu, 3 Dec 2015 09:01:40 +0100
Nicolas George wrote:
> (Sun is also responsible for making java's char type 16-bits and strings
> UTF-16. This is another case of headdesk, or possibly headwall, although
> entirely unrelated to the wchar_t issue. For those who do not know,
> basically UTF-16 ma
n the libc, but of course,
outside the Linux world, the libc and the kernel come from the same origin
and have the same name), the value for non-ASCII characters depends on the
locale.
More precisely, the value of wchar_t with UTF-8 locales is the Unicode code
point (same as GNU and any sane imple
un had other interesting ideas on how to make the coding for
> wchar_t itself depend on the locale.
I understand the reference to (the mess from) MS (although at that
time everyone in America did think 64k would be enough characters for
everyone, didn't they?), but not the one to Sun.
Were the
Le nonidi 9 frimaire, an CCXXIV, Thomas Schmitt a écrit :
> Well, in this case a byte does not necessarily consist of 8 bits,
> which would make data exchange somewhat difficult.
As I said, POSIX mandates that bytes are octets. C without POSIX does not
allow reliable binary I/O.
> But i confess t
Hi,
Nicolas George wrote:
> # [#3] When applied to an operand that has type char, unsigned char, or
> # signed char, (or a qualified version thereof) the result is 1.
Well, in this case a byte does not necessarily consist of 8 bits,
which would make data exchange somewhat difficult.
But i confes
Le nonidi 9 frimaire, an CCXXIV, Thomas Schmitt a écrit :
> Are you sure this function qualifies for copyright at all ? ~:o)
This would be for a judge to decide, if I were to sue.
> The man page of putc(3) looks suspicious:
>fputc() writes the character c, cast to an unsigned char, to str
Hi,
Nicolas George wrote:
> void put_utf32be(FILE *f, unsigned c)
> ...
> Note: I hereby place this code under the terms of the GNU GPL.
Are you sure this function qualifies for copyright at all ? ~:o)
To be nitpicking ...
The man page of putc(3) looks suspicious:
fputc() writes the c
ode point.
The i4s at sun had other interesting ideas on how to make the coding for
wchar_t itself depend on the locale.
If you really need to write UTF-32, writing the corresponding function takes
about half a minute:
void put_utf32be(FILE *f, unsigned c)
{
putc(f, (c >> 24) &
Hi,
Morten W. Petersen wrote:
> This program outputs some information to stdout in the testing process,
> and this is also UTF-32
As long as they are in stdout, the UTF-32 characters are byte
sequences of no special meaning.
The meaning as characters is attributed to them by the display
program (
lly a character is an integer >= 32 bits).
I tried now to use putwchar:
putwchar((wchar_t) buffer[index]);
And the output is the same as if had used
printf("%c", (char) buffer[index]);
That is, non-ASCII characters are garbled.
All the locale settings except LC_ALL are
Le nonidi 9 frimaire, an CCXXIV, Morten W. Petersen a écrit :
> I was looking for a locale that would enable me to putwchar a 32-bit
> Unicode character to stdout and have things handled correctly,
> automatically. Without any re-encoding to UTF-8 and so on.
I do not know what your p
Hi Alex,
thanks for that.
I was looking for a locale that would enable me to putwchar a 32-bit
Unicode character to stdout and have things handled correctly,
automatically. Without any re-encoding to UTF-8 and so on.
-Morten
On Sun, Nov 29, 2015 at 2:21 PM, Alex Vong wrote:
> Hi Mor
are/libiconv/> could help you.
Cheers,
Alex
On 29/11/2015, Morten W. Petersen wrote:
> Hi there.
>
> I have some questions about building/enabling a UTF-32 locale in Debian or
> Linux in general, who could I talk to about that?
>
> Thanks,
>
> Morten
>
> --
> Twit
Pretty much what the subject says.
I'm trying to configure my virtual consoles in Debian Jessie.
When I ask for a listing of the available keymaps, this is what I get
instead:
; localectl list-keymaps
Couldn't find any console keymaps.
Other localectl incantations seem to be working just fi
On 03/16/2015 08:26 PM, Bob Proulx wrote:
Frank wrote:
Bob Proulx wrote:
cat /etc/default/locale
root@frank-debian:/home/frank# cat /etc/default/locale
#LANG=en_US.UTF-8
Unexpected..I thought it would be empty ?
For whatever reason the locales package postinst script simply
comments
Frank wrote:
> Bob Proulx wrote:
> > cat /etc/default/locale
>
> root@frank-debian:/home/frank# cat /etc/default/locale
> #LANG=en_US.UTF-8
>
> Unexpected..I thought it would be empty ?
For whatever reason the locales package postinst script simply
comments out the li
On 03/14/2015 07:21 PM, Frank wrote:
On 03/14/2015 07:02 PM, Bob Proulx wrote:
Frank wrote:
Is this what should be in /etc/default/locale ??
Seems strange.
Not strange. Unfamiliar maybe. This file replaced the same use of it
in the /etc/environment file. And there have been other
On 03/14/2015 06:55 PM, David Wright wrote:
Quoting Frank (debianl...@videotron.ca):
On 03/14/2015 04:03 PM, Bob Proulx wrote:
Frank wrote:
The past few days I've been getting mail from anacron
about errors like this:
/etc/cron.daily/man-db:
/usr/bin/mandb: can't set the locale;
On 03/14/2015 07:02 PM, Bob Proulx wrote:
Frank wrote:
Is this what should be in /etc/default/locale ??
Seems strange.
Not strange. Unfamiliar maybe. This file replaced the same use of it
in the /etc/environment file. And there have been other attempts as
well. I expect it will go
Frank wrote:
> Sorry sent this to Bob instead of the list. Getting old :)
We are all getting old. And at the same rate too! :-)
> Bob Proulx wrote:
> >Somewhere along the way you have set the default system locale to one
> >that doesn't exist. What is the value stored h
Quoting Frank (debianl...@videotron.ca):
> On 03/14/2015 04:03 PM, Bob Proulx wrote:
> >Frank wrote:
> >>The past few days I've been getting mail from anacron
> >>about errors like this:
> >>
> >>/etc/cron.daily/man-db:
> >>/usr/bin
Sorry sent this to Bob instead of the list. Getting old :)
On 03/14/2015 04:03 PM, Bob Proulx wrote:
Frank wrote:
The past few days I've been getting mail from anacron
about errors like this:
/etc/cron.daily/man-db:
/usr/bin/mandb: can't set the locale; make sure $LC_* and $LANG a
Frank wrote:
> The past few days I've been getting mail from anacron
> about errors like this:
>
> /etc/cron.daily/man-db:
> /usr/bin/mandb: can't set the locale; make sure $LC_* and $LANG are correct
Somewhere along the way you have set the default system locale to one
The past few days I've been getting mail from anacron
about errors like this:
/etc/cron.daily/man-db:
/usr/bin/mandb: can't set the locale; make sure $LC_* and $LANG are correct
This is the man-db script:
#!/bin/sh
#
# man-db cron daily
set -e
iosched_idle=
# Don't tr
ML mail wrote:
> Since now already a few weeks I noticed that my locale settings on
> various Debian 6.0 servers got by some mysterious way broken... For
> example any tool/command using PERL will issue the following
> warning:
>
> perl: warning: Setting locale failed.
>
PM
Subject: Re: Locale issue
On Fri, Dec 07, 2012 at 01:17:20AM -0800, ML mail wrote:
> Hello,
>
> Since now already a few weeks I noticed that my locale settings on various
> Debian 6.0 servers got by some mysterious way broken... For example any
> tool/command using PERL wi
On Fri, Dec 07, 2012 at 01:17:20AM -0800, ML mail wrote:
> Hello,
>
> Since now already a few weeks I noticed that my locale settings on various
> Debian 6.0 servers got by some mysterious way broken... For example any
> tool/command using PERL will issue the following war
On Vi, 07 dec 12, 01:17:20, ML mail wrote:
> Hello,
>
> Since now already a few weeks I noticed that my locale settings on
> various Debian 6.0 servers got by some mysterious way broken... For
> example any tool/command using PERL will issue the following warning:
>
> p
Hello,
Since now already a few weeks I noticed that my locale settings on various
Debian 6.0 servers got by some mysterious way broken... For example any
tool/command using PERL will issue the following warning:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale
Zsolt Ero writes:
> My question is that is it safe to remove the all the leftover file
> from /usr/share/locale after removing the locales package?
Where do these files come from? Shouldn't they have been removed when
purging the package? Do they belong to another package?
On Mon 17 Sep 2012 at 17:22:16 +, Camaleón wrote:
> Google points to a tool called "localepurge", available from the usual
> repositories. Before manually removing folders that where not purged
> after the locale packages have been removed, I would look at this, just
On 2012-09-17 19:22 +0200, Camaleón wrote:
> On Mon, 17 Sep 2012 16:47:23 +0200, Zsolt Ero wrote:
>
> (...)
>
>> My question is that is it safe to remove the all the leftover file from
>> /usr/share/locale after removing the locales package?
>>
>> Or are th
On Mon, 17 Sep 2012 16:47:23 +0200, Zsolt Ero wrote:
(...)
> My question is that is it safe to remove the all the leftover file from
> /usr/share/locale after removing the locales package?
>
> Or are those files required for anything else?
(...)
Google points to a tool called
I'm trying to make a minimalistic Debian install for a low-mem VPS
box. I'll be uninstalling the locales package, as there is no need for
any kind of locale support for my purposes (only a few server
programs, English only is perfectly enough).
My question is that is it safe to remove t
On Sun, Sep 2, 2012 at 11:11 PM, Dan B. wrote:
>
> Are you sure about sed?
>
> I tried probing how LANG= vs. LANG=en_US.UTF-8 affected whether
> the regular expression "[a-z]" matched "X". Grep seems to be
> affected as expected, but sed never matched. (That's on Squeeze.)
What commands dud you
slightly different. Because they start up
/before/ you log in, they switch unicode mode on or off depending
on the default system locale (/etc/default/locale). See
unicode_start_stop in /etc/init.d/console-screen.kbd.sh. You can
switch them into unicode mode with unicode_start, which sends an
escape s
get the
encoding to use inside the emulator using nl_langinfo(3)....
What about the virtual consoles?
Whether I choose a default system locale of UTF-8 or None (in the
dialog for "dpkg-reconfigure locales"), and log out and log in (to
make sure the shell has a chance to get fres
On Sat, 01 Sep 2012 19:32:48 -0400, Dan B. wrote:
> In a locale setting such as en_US.UTF-8 (e.g., LANG=en_US.UTF-8), what
> exactly does the charset/character encoding part (UTF-8) affect?
>
> Which common programs (e.g., getty, xterm/etc., sed/grep?) do something
> differe
1 - 100 of 863 matches
Mail list logo
