From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v5 1/2] Add 'strcmp_collation' support for LC_COLLATE.
Date: Fri, 30 Jul 2021 08:11:10 +0200 [thread overview]
Message-ID: <87y29oz5z5.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210730043218.3701358-2-carlos@redhat.com> (Carlos O'Donell via Libc-alpha's message of "Fri, 30 Jul 2021 00:32:17 -0400")
* Carlos O'Donell via Libc-alpha:
> @@ -2123,6 +2135,20 @@ collate_output (struct localedef_t *locale, const struct charmap_t *charmap,
> /* The words have to be handled specially. */
> if (idx == _NL_ITEM_INDEX (_NL_COLLATE_SYMB_HASH_SIZEMB))
> add_locale_uint32 (&file, 0);
> + else if (idx == _NL_ITEM_INDEX (_NL_COLLATE_CODESET)
> + && collate != NULL)
> + /* A valid LC_COLLATE must have a code set name. */
> + add_locale_string (&file, charmap->code_set_name);
> + else if (idx == _NL_ITEM_INDEX (_NL_COLLATE_COLLSEQMB)
> + && collate != NULL)
> + {
> + add_locale_raw_data (&file, collseqmb, 256);
> + }
> + else if (idx == _NL_ITEM_INDEX (_NL_COLLATE_COLLSEQWC)
> + && collate != NULL)
> + {
> + add_locale_raw_data (&file, collseqwc, sizeof (collseqwc));
> + }
> else
> add_locale_empty (&file);
The braces are inconsistent. And I think collseqwc needs to be written
using add_locale_uint32_array, to support --big-endian/--little-endian.
Thanks,
Florian
next prev parent reply other threads:[~2021-07-30 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 4:32 [PATCH v5 0/2] C.UTF-8 Carlos O'Donell via Libc-alpha
2021-07-30 4:32 ` [PATCH v5 1/2] Add 'strcmp_collation' support for LC_COLLATE Carlos O'Donell via Libc-alpha
2021-07-30 6:11 ` Florian Weimer via Libc-alpha [this message]
2021-07-30 4:32 ` [PATCH v5 2/2] Add generic C.UTF-8 locale (Bug 17318) Carlos O'Donell via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y29oz5z5.fsf@oldenburg.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.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).