From: "Diego (Egor) Kobylkin" <egor@kobylkin.com>
To: Roumen Petrov <bugtrack@roumenpetrov.info>
Cc: "libc-locales@sourceware.org" <libc-locales@sourceware.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] locale/C-translit.h.in: Greek -> ASCII transliteration table [BZ #12031]
Date: Thu, 05 Sep 2019 20:12:00 -0000 [thread overview]
Message-ID: <A8OBT11NHOdi4MDTlfDyFwcSJVGTyQB1_9O4IMe5xfflXKvggq0bdNZS2MbUg1m_Jxk16hdDaU48kHkXxBAnzeT3zbWhx4VsT-vEdqiDzmw=@kobylkin.com> (raw)
In-Reply-To: <65329708-2089-09d4-abda-66bd1f4c0384@roumenpetrov.info>
[-- Attachment #1.1: Type: text/plain, Size: 1215 bytes --]
Hi,
To be super clear, this patch is for _Greek_ transliteration [BZ #12031] for the C Locale.
https://sourceware.org/bugzilla/show_bug.cgi?id=12031
It has nothing to do with Bulgarian Cyrillic.
Looks like the mention of the other already patched bug led to a confusion. Please just disregard that mention going forward.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, September 5, 2019 11:44 AM, Roumen Petrov <bugtrack@roumenpetrov.info> wrote:
> Hello,
>
> Diego (Egor) Kobylkin wrote:
>
> > Dear locale maintainers,
> > fix the glibc bug 12031 "iconv -t ascii//translit with Greek characters" [1]
> > add Greek transliteration rows to locale/C-translit.h.in.
> > This work is done on the heels of the successfully committed patch for the
> > virtually the same bug [BZ #2872] but concerning Cyrillic characters. [2]
>
> Transliteration is mostly locale dependent.
>
> Proposed cyrilic map does not match current Bulgarian act -
> https://www.mrrb.bg/bg/zakon-za-transliteraciyata/ . I cannot remember
> what is difference to the previous one dated 70 years ago.
>
> [SNIP]
>
> Regards,
> Roumen Petrov
Bests,
Egor Kobylkin
[-- Attachment #1.2: publickey - egor@kobylkin.com - 0x01FEB4E8.asc --]
[-- Type: application/pgp-keys, Size: 657 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 217 bytes --]
next prev parent reply other threads:[~2019-09-05 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 7:31 Diego (Egor) Kobylkin
2019-09-05 9:44 ` Roumen Petrov
2019-09-05 20:12 ` Diego (Egor) Kobylkin [this message]
2019-10-08 19:20 ` Diego (Egor) Kobylkin
2019-11-08 19:43 ` Florian Weimer
2019-11-08 20:53 ` Diego (Egor) Kobylkin
2019-11-08 20:59 ` Florian Weimer
2019-11-14 12:33 ` 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='A8OBT11NHOdi4MDTlfDyFwcSJVGTyQB1_9O4IMe5xfflXKvggq0bdNZS2MbUg1m_Jxk16hdDaU48kHkXxBAnzeT3zbWhx4VsT-vEdqiDzmw=@kobylkin.com' \
--to=egor@kobylkin.com \
--cc=bugtrack@roumenpetrov.info \
--cc=libc-alpha@sourceware.org \
--cc=libc-locales@sourceware.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).