From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-developers@cygwin.com
Subject: Re: glib2.0 2.64.6-1 (TEST)
Date: Wed, 26 Jul 2023 16:56:35 +0100 [thread overview]
Message-ID: <fe8107a1-29f1-fafd-45b0-e0761f70af9a@dronecode.org.uk> (raw)
In-Reply-To: <ZMEuw8xJhnRhhSos@calimero.vinschen.de>
On 26/07/2023 15:33, Corinna Vinschen wrote:
> On Jul 3 15:49, Jon Turney wrote:
>> On 02/07/2023 15:30, Jon Turney wrote:
>>>
>>> The following packages have been uploaded to the Cygwin distribution:
>>>
>>> * libglib2.0_0-2.64.6-1
>>> * libglib2.0-devel-2.64.6-1
>>> * libglib2.0-doc-2.64.6-1
>>>
>> [...]
>>>
>>> There are many test-suite failures, however, as far as I can tell, they
>>> are not regressions, so this should work as well as it ever did.
>>
>> At least some of these test failures are due to bugs or shortcomings in the
>> Cygwin DLL. In an ideal world, I'd have the time and motivation to
>> investigate them all, but here's a brief summary of the few I looked into
>> ...
>>
>> gdatetime: The _NL_CTYPE_OUTDIGITx_MB constants for nl_langinfo aren't
>> defined (possibly because we don't have the required information, e.g. to
>> produce Persian (as opposed to Arabic) digit characters in the fa_IR.utf-8
>> locale)
>
> Uhm... we actually have this information. Only, unfortunately I screwed
> up the names:
>
> _NL_CTYPE_OUTDIGITSx_MB
>
> instead of
>
> _NL_CTYPE_OUTDIGITx_MB
>
> D'oh.
>
> Do you think we need the wrong names for backward compat? Theoretically
> they should never have been used...
A brief web search only finds the wrong names in the cygwin source code,
so yeah, I'd say just fix it.
next prev parent reply other threads:[~2023-07-26 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <adaf0c49-3ab2-c883-474e-f9e00f79c5bb@dronecode.org.uk>
2023-07-03 14:49 ` Jon Turney
2023-07-26 14:33 ` Corinna Vinschen
2023-07-26 15:56 ` Jon Turney [this message]
2023-07-28 15:17 ` Jon Turney
2023-08-04 17:04 ` Jon Turney
2023-08-07 9:51 ` Corinna Vinschen
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=fe8107a1-29f1-fafd-45b0-e0761f70af9a@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-developers@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).