From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Custom locales seem not to work
Date: Mon, 21 Jun 2021 09:48:15 -0600 [thread overview]
Message-ID: <a4b62a2e-da7b-2203-74f4-1168a3bd9df8@SystematicSw.ab.ca> (raw)
In-Reply-To: <PA4PR01MB7599EA3D08DA59B28B72C700A90A9@PA4PR01MB7599.eurprd01.prod.exchangelabs.com>
On 2021-06-21 07:23, Алекса -скрыто- via Cygwin wrote:
> I noticed that Cygwin-linked applications fail to use the proper
> language code from a Windows custom locale, and revert to C instead.
> Is that a bug?
Cygwin automatically tries to pick your locale using Windows system
language, country, and regional settings, if you have set them. Many
Cygwin packages are not localized, do not come with localizations, may
not support certain locales, or may have incomplete translations. For
example, on my system, the following are the only Cygwin programs
installed with Russian localizations (no others are):
$ ls -xw72 /usr/share/locale/ru*/*
/usr/share/locale/ru/LC_MESSAGES:
alacarte.mo alternatives.mo
appstream.mo appstream-glib.mo
aspell.mo atk10.mo
at-spi2-core.mo bash.mo
bfd.mo binutils.mo
bison.mo bison-runtime.mo
clisp.mo clisplow.mo
coreutils.mo cpio.mo
cpplib.mo cygwin32-cpplib.mo
cygwin32-gcc.mo dialog.mo
diffutils.mo dos2unix.mo
epiphany.mo exif.mo
findutils.mo flex.mo
gas.mo gcal.mo
gcc.mo gcr.mo
gdk-pixbuf.mo gettext-runtime.mo
gettext-tools.mo git.mo
glib20.mo glib-networking.mo
gnome-doc-utils.mo gnome-keyring.mo
gnome-menus-3.0.mo gnupg.mo
gnupg2.mo gprof.mo
grep.mo gsettings-desktop-schemas.mo
gstreamer-1.0.mo gtk20.mo
gtk20-properties.mo gtk30.mo
gtk30-properties.mo gvfs.mo
help2man.mo i686-pc-cygwin-bfd.mo
i686-pc-cygwin-binutils.mo i686-pc-cygwin-gas.mo
i686-pc-cygwin-gprof.mo i686-pc-cygwin-ld.mo
iso_15924.mo iso_3166.mo
iso_3166-1.mo iso_3166-3.mo
iso_4217.mo iso_639.mo
iso_639_3.mo iso_639-2.mo
iso_639-3.mo isoquery.mo
json-glib-1.0.mo ld.mo
lftp.mo libexif-12.mo
libfm.mo libgpg-error.mo
libgsf.mo libiconv.mo
libidn2.mo libisocodes.mo
libsecret.mo libsoup.mo
libwnck.mo libwnck-3.0.mo
lxappearance.mo lxappearance-obconf.mo
lxinput.mo lxpanel.mo
lxsession.mo lxtask.mo
lxterminal.mo lynx.mo
mailutils.mo make.mo
man-db.mo man-db-gnulib.mo
midori.mo openbox.mo
osinfo-db-tools.mo pcmanfm.mo
popt.mo psmisc.mo
rpm.mo sed.mo
sharutils.mo tar.mo
tcsh.cat texinfo.mo
util-linux.mo vte-0.0.mo
WebKitGTK-2.0.mo WebKitGTK-3.0.mo
wget.mo wget2.mo
wget-gnulib.mo whois.mo
xarchiver.mo xdg-user-dirs.mo
xdg-user-dirs-gtk.mo xkeyboard-config.mo
/usr/share/locale/ru/LC_TIME:
coreutils.mo
/usr/share/locale/ru_UA/LC_MESSAGES:
tcsh.cat
Which applications do you have problems with, what locale do you wish to
use, and what are your locale settings; try running the command below
and post your input and output (don't worry if some of your output is in
Русский or Кириллица):
$ for o in -s -u -i -n -f ''; do locale $o; done
en_US
en_GB
en_CA
en_CA
en_CA
LANG=en_CA.UTF-8
LC_CTYPE="en_CA.UTF-8"
LC_NUMERIC="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_COLLATE="en_CA.UTF-8"
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_ALL=
so you can see I run Windows system default US English, user default
GB/UK English, input, non-Unicode, and regional formats Canadian English
(and customized some of those settings).
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-06-21 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 13:23 Алекса -скрыто-
2021-06-21 15:48 ` Brian Inglis [this message]
2021-06-21 18:21 ` Thomas Wolff
2021-06-21 20:06 ` Brian Inglis
2021-06-22 8:50 ` Алекса -скрыто-
2021-06-22 18:32 ` Brian Inglis
2021-06-26 14:58 ` Алекса -скрыто-
2021-06-26 19:29 ` Brian Inglis
2021-06-26 20:10 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4b62a2e-da7b-2203-74f4-1168a3bd9df8@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).