public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Custom locales seem not to work
Date: Sat, 26 Jun 2021 14:10:13 -0600	[thread overview]
Message-ID: <1c273679-ed8b-205d-98fb-0e2095ecb743@SystematicSw.ab.ca> (raw)
In-Reply-To: <a8b59f40-4b95-b1b8-eccd-a297df25e8d3@SystematicSw.ab.ca>

On 2021-06-26 13:29, Brian Inglis wrote:
> On 2021-06-26 08:58, Алекса -скрыто- via Cygwin wrote:
>>> I have never seen ie used as a language code under Linux systems, and it
>>> is interlingual, associated with unspecified territory code XX, so you
>>> would have to set each locale category separately to achieve the desired
>>> effects: fr_CH or en_US.
> 
>> ... the locale should be set to "ie_XX.UTF-8", which the locale data 
>> provides, not "C" like Cygwin does now.

If you setup non-interoperable custom locales, it is likely that Cygwin 
may not be seeing anything it can map, so will default to the hardwired 
built-in C/POSIX locale.

You need to help us diagnose what, if anything, Cygwin may be seeing 
from your custom Windows locale.

What does Cygwin show when you run the locale dump command from a shell:

     $ for o in -s -u -i -n -f ''; do locale $o; done

> Which are non-interoperable Windows-only totally meaningless language 
> and territory values to Cygwin startup or any Cygwin, Linux, or Unix 
> program based on Unix libraries or code, so everything might map to the 
> system default locale at best, or hardwired built-in C/POSIX locale at 
> worst.
> 
> That custom locale would be better if developed as a fr_CH replacement 
> or supplementary Windows locale.

It might also help if you followed the Cygwin problem reporting guidelines:

	https://cygwin.com/problems.html

and attached the required output as plain text to your next response.

-- 
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.]

      reply	other threads:[~2021-06-26 20:10 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
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 [this message]

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=1c273679-ed8b-205d-98fb-0e2095ecb743@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).