unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v4 4/4] Add generic C.UTF-8 locale (Bug 17318)
Date: Fri, 30 Apr 2021 13:59:49 -0400	[thread overview]
Message-ID: <dbbf0eb9-f2af-5bd5-2bda-4ed5cd586d67@redhat.com> (raw)
In-Reply-To: <93ab3888-25db-4582-ce6a-c7a91ac14417@redhat.com>

On 4/29/21 4:05 PM, Carlos O'Donell wrote:
> - LC_CTYPE, includes "translit_combining" which is wrong for a C locale IMO.
>   - Upstream C.UTF-8 includes no transliteration, all characters pass
>     through because UTF-8 supports all such characters.

It turns out that this is related to bug 26984.

I was wrong too, the C locale has a builtin set of ~1600 transliterations that
it uses internally (I even reviewed a patch for that you committed).
I had completely forgotten about this internal detail.

This transliteration affects converters ability to use //TRANSLIT, and so I
think we should include all the netural transliterations e.g.

translit_start
include "translit_neutral";""
translit_end

This makes things *better* with respect to harmonization with Debian/Ubuntu.

Thoughts?

In summary:
- POSIX says nothing about transliteration.
- C/POSIX already includes a partial set of ~1600 translit entries, and they
  are largely incomplete. It would be nice to harmonize them with the proper
  translit_neutral set.
- C.UTF-8 including translit_neutral would bring in ~25,000 translit rules
  for conversions from UTF-8 to other charmaps. This would be a superset of
  those offered by C/POSIX.
- Fixing C/POSIX is another issue.

-- 
Cheers,
Carlos.


  reply	other threads:[~2021-04-30 17:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 13:00 [PATCH v4 0/4] Add new C.UTF-8 locale (Bug 17318) Carlos O'Donell via Libc-alpha
2021-04-28 13:00 ` [PATCH v4 1/4] Add support for processing wide ellipsis ranges in UTF-8 Carlos O'Donell via Libc-alpha
2021-04-29 14:11   ` Florian Weimer via Libc-alpha
2021-04-28 13:00 ` [PATCH v4 2/4] Update UTF-8 charmap processing Carlos O'Donell via Libc-alpha
2021-04-29 14:07   ` Florian Weimer via Libc-alpha
2021-04-29 21:02     ` Carlos O'Donell via Libc-alpha
2021-04-30  4:18       ` Florian Weimer via Libc-alpha
2021-05-02 19:18         ` Carlos O'Donell via Libc-alpha
2021-04-28 13:00 ` [PATCH v4 3/4] Regenerate localedata files Carlos O'Donell via Libc-alpha
2021-04-29 21:03   ` Carlos O'Donell via Libc-alpha
2021-04-28 13:00 ` [PATCH v4 4/4] Add generic C.UTF-8 locale (Bug 17318) Carlos O'Donell via Libc-alpha
2021-04-29 14:13   ` Florian Weimer via Libc-alpha
2021-04-29 20:05     ` Carlos O'Donell via Libc-alpha
2021-04-30 17:59       ` Carlos O'Donell via Libc-alpha [this message]
2021-04-30 18:20         ` Florian Weimer via Libc-alpha
2021-05-02 19:18           ` 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=dbbf0eb9-f2af-5bd5-2bda-4ed5cd586d67@redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    --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).