From: Marko Myllynen <myllynen@redhat.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
"Diego (Egor) Kobylkin" <egor@kobylkin.com>,
Carlos O'Donell <codonell@redhat.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"libc-locales@sourceware.org" <libc-locales@sourceware.org>,
Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Mike Fabian <mfabian@redhat.com>
Subject: Re: [PING^8][PATCH v12] Locales: Cyrillic -> ASCII transliteration [BZ #2872]
Date: Thu, 06 Jun 2019 09:42:00 -0000 [thread overview]
Message-ID: <f392d6b1-39e7-c883-ae5e-2a8636231181@redhat.com> (raw)
In-Reply-To: <2030695416.914859.1559778544120@poczta.nazwa.pl>
Hi,
On 06/06/2019 02.49, Rafal Luzynski wrote:
> 5.06.2019 08:47 "Diego (Egor) Kobylkin" <egor@kobylkin.com> wrote:
>>
>> ping
>
> I second these pings. Marko, Carlos, Siddhesh, Mike, is there anything
> else I can do here?
My understanding of the overall situation here is that for 2.30 we try
to have Cyrillic->ASCII transliteration added into the built-in C locale
and after that we would discuss more about translit rules used by other
locales, and that this C locale patch is pending on Carlos to complete
his verification efforts.
Does the above sound correct to you?
> Since the questions may sound overwhelming, I'd like to focus on
> a single issue:
Yes, the subject becomes overwhelming if considering everything related
at the same time so this sounds like a good approach, however are there
other notable open questions left around the C locale rules in addition
to this? (Ignoring the more generic tranlit rules or other locales for
the time being.)
> How should we handle the upper/lower case when a single Cyrillic letter
> is transliterated to a Latin digraph (trigraph, etc.)?
>
> Possible answers (Cyrillic -> Latin Extended -> ASCII):
>
> 1. "Ш" -> "Š" -> "SH"
>
> e.g.: "Шема" -> "Šema" -> "SHema"
> "СÑ
ема" ----------> "Shema"
>
> 2. "Ш" -> "Š" -> "Sh"
>
> e.g.: "Шема" -> "Šema" -> "Shema"
> "СÑ
ема" ----------> "Shema"
>
> Personally I don't like the answer 1. because "SHema" looks weird
> to me. Egor in turn does not like the answer 2. because the output
> string becomes ambiguous.
>
> Should we maybe have a smart algorithm which would select the title
> case or the upper case of the output characters depending on the
> context in the word? Note that it would not resolve the problem of
> the output text being ambiguous.
It seems clear that there is no one right/wrong answer but it's a matter
of preference, especially the way this currently works. It might be an
improvement to output (for instance) SH instead of Sh if all the other
letters of a word are upper-case as well but not sure what would help
with the result being unambiguous.
Thanks,
--
Marko Myllynen
next prev parent reply other threads:[~2019-06-06 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 6:47 Diego (Egor) Kobylkin
2019-06-05 23:51 ` Rafal Luzynski
2019-06-06 9:42 ` Marko Myllynen [this message]
2019-06-06 21:31 ` Rafal Luzynski
2019-06-07 0:58 ` Carlos O'Donell
2019-06-07 9:46 ` Diego (Egor) Kobylkin
2019-06-07 11:11 ` Rafal Luzynski
2019-06-07 10:51 ` Rafal Luzynski
2019-06-07 12:36 ` Carlos O'Donell
2019-06-07 13:00 ` Diego (Egor) Kobylkin
2019-06-07 21:17 ` Carlos O'Donell
2019-06-10 22:44 ` Rafal Luzynski
2019-06-17 8:59 ` Diego (Egor) Kobylkin
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=f392d6b1-39e7-c883-ae5e-2a8636231181@redhat.com \
--to=myllynen@redhat.com \
--cc=codonell@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=egor@kobylkin.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-locales@sourceware.org \
--cc=mfabian@redhat.com \
--cc=siddhesh@gotplt.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).