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 14:06:59 -0600 [thread overview]
Message-ID: <51ab9bc2-5df0-e7f9-eb20-e56fe2f6b3fd@SystematicSw.ab.ca> (raw)
In-Reply-To: <4ac85d41-94f5-26f6-eb6a-75754d71cdb1@towo.net>
On 2021-06-21 12:21, Thomas Wolff wrote:
> Am 21.06.2021 um 15:23 schrieb Алекса -скрыто- via Cygwin:
>> 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?
> If you define a Windows custom locale, how would you expect it to be
> referred to from cygwin, i.e. which POSIX locale name should be used to
> be mapped to it and how should this mapping be magically deployed into
> cygwin?
> I don't think such a mechanism can easily be designed or implemented.
If the OP is using a Windows supplemental or replacement locale
installation, rather than just customizing the locale information, could
they please export the LDML as UTF8 text and attach it to their post.
If the locale identifiers are sufficiently non-standard, they would
require a custom mapping in Cygwin.
--
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 20:07 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 [this message]
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=51ab9bc2-5df0-e7f9-eb20-e56fe2f6b3fd@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).