From: Mike FABIAN <mfabian@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: David Paleino <dapal@debian.org>,
Florian Weimer <fweimer@redhat.com>,
libc-alpha@sourceware.org, tech@cademiasiciliana.org
Subject: Re: [PATCH] localedata: add new locales scn_IT and scn_US
Date: Thu, 16 May 2024 17:03:58 +0200 [thread overview]
Message-ID: <s9dcyplztlt.fsf@hathi.site> (raw)
In-Reply-To: <mvmjzjuyqae.fsf@suse.de> (Andreas Schwab's message of "Thu, 16 May 2024 13:00:57 +0200")
Andreas Schwab <schwab@suse.de> さんはかきました:
> On Mai 16 2024, Andreas Schwab wrote:
>
>> On Mai 16 2024, Mike FABIAN wrote:
>>
>>> David Paleino <dapal@debian.org> さんはかきました:
>>>
>>>> +LC_CTYPE
>>>> +copy "it_IT"
>>>> +
>>>> +translit_start
>>>> +ḌḌ "DDH"
>>>> +ḍḍ "ddh"
>>>> +Ḍḍ "Ddh"
>>>> +translit_end
>>>> +END LC_CTYPE
>>>
>>> I am sorry for not testing that earlier, but that translit part does not
>>> seem to work:
>>>
>>> bash-5.2# export LC_ALL=scn_IT.UTF-8
>>> bash-5.2# echo 'ḌḌ' | iconv -f UTF-8 -t ASCII//translit
>>> ??
>>
>> There is already a transliteration for Ḍ which takes precedence.
>
> Actually, the entries above replace the ones from translit_combining,
> but they are interpreted as "Ḍ" -> "DDH" and "ḍ" -> "ḍddh" (the third
> entry is ignored). The proper syntax would be
>
> translit_start
> "ḌḌ" "DDH"
> "ḍḍ" "ddh"
> "Ḍḍ" "Ddh"
> translit_end
Thank you! I have tried with that syntax now but could not make it work.
> but depending on the how the binary search goes on, either these or the
> shorter matches will win.
Does it depend on the exact input how the binary search goes on?
I tried several inputs and for me the shorter matches did always win.
Then I uncommented the shorter matches in translit_combining like this:
diff --git a/localedata/locales/translit_combining b/localedata/locales/translit_combining
index ce2f19eee1..6f879d9caf 100644
--- a/localedata/locales/translit_combining
+++ b/localedata/locales/translit_combining
@@ -2486,9 +2486,9 @@ translit_start
% LATIN SMALL LETTER D WITH DOT ABOVE
<U1E0B> <U0064>
% LATIN CAPITAL LETTER D WITH DOT BELOW
-<U1E0C> <U0044>
+%<U1E0C> <U0044>
% LATIN SMALL LETTER D WITH DOT BELOW
-<U1E0D> <U0064>
+%<U1E0D> <U0064>
% LATIN CAPITAL LETTER D WITH LINE BELOW
<U1E0E> <U0044>
% LATIN SMALL LETTER D WITH LINE BELOW
and after doing that,
bash-5.2# echo 'ḌḌ'|iconv -f UTF-8 -t ASCII//translit
^C
bash-5.2#
uses 100% CPU and never stops until I stop it with Control-C.
--
Mike FABIAN <mfabian@redhat.com>
睡眠不足はいい仕事の敵だ。
next prev parent reply other threads:[~2024-05-16 15:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 21:37 David Paleino
2024-04-29 13:17 ` Florian Weimer
2024-05-01 0:09 ` David Paleino
2024-05-13 13:23 ` Florian Weimer
2024-05-14 20:58 ` David Paleino
2024-05-14 21:08 ` David Paleino
2024-05-15 4:37 ` Florian Weimer
2024-05-15 15:17 ` Mike FABIAN
2024-05-15 18:39 ` David Paleino
2024-05-16 7:38 ` Mike FABIAN
2024-05-16 8:08 ` Mike FABIAN
2024-05-16 8:44 ` Andreas Schwab
2024-05-16 9:47 ` Florian Weimer
2024-05-16 10:22 ` Andreas Schwab
2024-05-16 10:20 ` Andreas Schwab
2024-05-16 11:00 ` Andreas Schwab
2024-05-16 15:03 ` Mike FABIAN [this message]
2024-05-16 15:20 ` Andreas Schwab
2024-06-09 7:20 ` Mike FABIAN
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=s9dcyplztlt.fsf@hathi.site \
--to=mfabian@redhat.com \
--cc=dapal@debian.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
--cc=tech@cademiasiciliana.org \
/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).