setting locale for utf-8 , but to keep measurements, time, date, etc .like with =“C�
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
End goal: use utf-8, but keep rest default (i.e. monetary, date, numeric, etc formats).
I come up with idea "let's make system utf-8 , but keep measurements, time, date, etc like it was" and this (probably terrible) implementation:
LANG="en_US.utf-8" # or en_GB.utf-8
LANGUAGE="en_US.utf-8" # or en_GB.utf-8
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
It seems intuitively (and in practice), that "C" (which is non utf-8, right?) will not mix well with ".utf-8" locales (and it does not! quiet often some encoding dragon jumps out).
What is recommended ".utf-8" locale (which I should use in "=C" cases) to preserve spirit of original units, measurements (km not miles, Celsius not Fahrenheit etc), date&time format, paper (actually I'd like A4, not "letter"), etc?
( or maybe "C" locale can be mixed with ".utf-8" locale, and I made other mistake ? )
locale unicode
asked Nov 27 '17 at 21:59
Grzegorz Wierzowiecki
4,9681160100
add a comment |Â
up vote
2
down vote
favorite
End goal: use utf-8, but keep rest default (i.e. monetary, date, numeric, etc formats).
I come up with idea "let's make system utf-8 , but keep measurements, time, date, etc like it was" and this (probably terrible) implementation:
LANG="en_US.utf-8" # or en_GB.utf-8
LANGUAGE="en_US.utf-8" # or en_GB.utf-8
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
It seems intuitively (and in practice), that "C" (which is non utf-8, right?) will not mix well with ".utf-8" locales (and it does not! quiet often some encoding dragon jumps out).
What is recommended ".utf-8" locale (which I should use in "=C" cases) to preserve spirit of original units, measurements (km not miles, Celsius not Fahrenheit etc), date&time format, paper (actually I'd like A4, not "letter"), etc?
( or maybe "C" locale can be mixed with ".utf-8" locale, and I made other mistake ? )
locale unicode
asked Nov 27 '17 at 21:59
Grzegorz Wierzowiecki
4,9681160100
2
Some systems have a C.UTF-8 locale for something like that. The C locale has a single-byte charset usually ASCII with bytes 128 to 255 undefined, not UTF-8
– Stéphane Chazelas
Nov 27 '17 at 22:08
1
Just changingLC_CTYPEwould affect the character encoding without changing the regional settings.
– Thomas Dickey
Nov 27 '17 at 22:42
manpages.debian.org/unstable/… explains the what and why of C.UTF-8. In short: prevent programs from failing to start or output warnings on the command line. Target: servers. Saves 125MiB over locales-all and 10MiB over locale.
– Pro Backup
Nov 27 '17 at 22:48
What you are suggesting is perfectly valid.
– fpmurphy1
Nov 28 '17 at 2:00
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
End goal: use utf-8, but keep rest default (i.e. monetary, date, numeric, etc formats).
I come up with idea "let's make system utf-8 , but keep measurements, time, date, etc like it was" and this (probably terrible) implementation:
LANG="en_US.utf-8" # or en_GB.utf-8
LANGUAGE="en_US.utf-8" # or en_GB.utf-8
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
It seems intuitively (and in practice), that "C" (which is non utf-8, right?) will not mix well with ".utf-8" locales (and it does not! quiet often some encoding dragon jumps out).
What is recommended ".utf-8" locale (which I should use in "=C" cases) to preserve spirit of original units, measurements (km not miles, Celsius not Fahrenheit etc), date&time format, paper (actually I'd like A4, not "letter"), etc?
( or maybe "C" locale can be mixed with ".utf-8" locale, and I made other mistake ? )
locale unicode
asked Nov 27 '17 at 21:59
Grzegorz Wierzowiecki
4,9681160100
End goal: use utf-8, but keep rest default (i.e. monetary, date, numeric, etc formats).
I come up with idea "let's make system utf-8 , but keep measurements, time, date, etc like it was" and this (probably terrible) implementation:
LANG="en_US.utf-8" # or en_GB.utf-8
LANGUAGE="en_US.utf-8" # or en_GB.utf-8
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
It seems intuitively (and in practice), that "C" (which is non utf-8, right?) will not mix well with ".utf-8" locales (and it does not! quiet often some encoding dragon jumps out).
What is recommended ".utf-8" locale (which I should use in "=C" cases) to preserve spirit of original units, measurements (km not miles, Celsius not Fahrenheit etc), date&time format, paper (actually I'd like A4, not "letter"), etc?
( or maybe "C" locale can be mixed with ".utf-8" locale, and I made other mistake ? )
locale unicode
asked Nov 27 '17 at 21:59
Grzegorz Wierzowiecki
4,9681160100
edited Nov 27 '17 at 23:22
asked Nov 27 '17 at 21:59
Grzegorz Wierzowiecki
4,9681160100
asked Nov 27 '17 at 21:59
Grzegorz Wierzowiecki
4,9681160100
asked Nov 27 '17 at 21:59
Grzegorz Wierzowiecki
4,9681160100
4,9681160100
2
Some systems have a C.UTF-8 locale for something like that. The C locale has a single-byte charset usually ASCII with bytes 128 to 255 undefined, not UTF-8
– Stéphane Chazelas
Nov 27 '17 at 22:08
1
Just changingLC_CTYPEwould affect the character encoding without changing the regional settings.
– Thomas Dickey
Nov 27 '17 at 22:42
manpages.debian.org/unstable/… explains the what and why of C.UTF-8. In short: prevent programs from failing to start or output warnings on the command line. Target: servers. Saves 125MiB over locales-all and 10MiB over locale.
– Pro Backup
Nov 27 '17 at 22:48
What you are suggesting is perfectly valid.
– fpmurphy1
Nov 28 '17 at 2:00
add a comment |Â
2
Some systems have a C.UTF-8 locale for something like that. The C locale has a single-byte charset usually ASCII with bytes 128 to 255 undefined, not UTF-8
– Stéphane Chazelas
Nov 27 '17 at 22:08
1
Just changingLC_CTYPEwould affect the character encoding without changing the regional settings.
– Thomas Dickey
Nov 27 '17 at 22:42
manpages.debian.org/unstable/… explains the what and why of C.UTF-8. In short: prevent programs from failing to start or output warnings on the command line. Target: servers. Saves 125MiB over locales-all and 10MiB over locale.
– Pro Backup
Nov 27 '17 at 22:48
What you are suggesting is perfectly valid.
– fpmurphy1
Nov 28 '17 at 2:00
2
2
Some systems have a C.UTF-8 locale for something like that. The C locale has a single-byte charset usually ASCII with bytes 128 to 255 undefined, not UTF-8
– Stéphane Chazelas
Nov 27 '17 at 22:08
Some systems have a C.UTF-8 locale for something like that. The C locale has a single-byte charset usually ASCII with bytes 128 to 255 undefined, not UTF-8
– Stéphane Chazelas
Nov 27 '17 at 22:08
1
1
Just changing
LC_CTYPE would affect the character encoding without changing the regional settings.– Thomas Dickey
Nov 27 '17 at 22:42
Just changing
LC_CTYPE would affect the character encoding without changing the regional settings.– Thomas Dickey
Nov 27 '17 at 22:42
manpages.debian.org/unstable/… explains the what and why of C.UTF-8. In short: prevent programs from failing to start or output warnings on the command line. Target: servers. Saves 125MiB over locales-all and 10MiB over locale.
– Pro Backup
Nov 27 '17 at 22:48
manpages.debian.org/unstable/… explains the what and why of C.UTF-8. In short: prevent programs from failing to start or output warnings on the command line. Target: servers. Saves 125MiB over locales-all and 10MiB over locale.
– Pro Backup
Nov 27 '17 at 22:48
What you are suggesting is perfectly valid.
– fpmurphy1
Nov 28 '17 at 2:00
What you are suggesting is perfectly valid.
– fpmurphy1
Nov 28 '17 at 2:00
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f407378%2fsetting-locale-for-utf-8-but-to-keep-measurements-time-date-etc-like-with%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
Some systems have a C.UTF-8 locale for something like that. The C locale has a single-byte charset usually ASCII with bytes 128 to 255 undefined, not UTF-8
– Stéphane Chazelas
Nov 27 '17 at 22:08
1
Just changing
LC_CTYPEwould affect the character encoding without changing the regional settings.– Thomas Dickey
Nov 27 '17 at 22:42
manpages.debian.org/unstable/… explains the what and why of C.UTF-8. In short: prevent programs from failing to start or output warnings on the command line. Target: servers. Saves 125MiB over locales-all and 10MiB over locale.
– Pro Backup
Nov 27 '17 at 22:48
What you are suggesting is perfectly valid.
– fpmurphy1
Nov 28 '17 at 2:00