public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ekobylkin at paypal dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/2872] Transliteration Cyrillic -> ASCII fails
Date: Tue, 08 Sep 2015 10:06:00 -0000	[thread overview]
Message-ID: <bug-2872-131-oXe33D1yxz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-2872-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=2872

Egor Kobylkin <ekobylkin at paypal dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #8589|0                           |1
        is obsolete|                            |

--- Comment #17 from Egor Kobylkin <ekobylkin at paypal dot com> ---
Created attachment 8591
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8591&action=edit
multi-character transliteration table cyrillic->ascii with fallback to
single-character

correction: updated the comment in the file to reflect new spreadsheet and
mutli-character feature

I have not tested the fallback to the sigle-character but have included it in
case somebody needs it. I am not sure on how to test it.
The file should ideally be included in all Latin based locales via include in
this section as follows (example)
LC_CTYPE
copy "i18n"

translit_start
include "translit_combining";"translit_cyrillic";""
translit_end
END LC_CTYPE

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-09-08 10:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-2872-131@http.sourceware.org/bugzilla/>
2015-09-07 11:18 ` ekobylkin at paypal dot com
2015-09-07 12:17 ` ekobylkin at paypal dot com
2015-09-07 23:07 ` ekobylkin at paypal dot com
2015-09-07 23:07 ` ekobylkin at paypal dot com
2015-09-07 23:10 ` ekobylkin at paypal dot com
2015-09-07 23:34 ` ekobylkin at paypal dot com
2015-09-08  6:35 ` myllynen at redhat dot com
2015-09-08  7:40 ` ekobylkin at paypal dot com
2015-09-08  9:11 ` ekobylkin at paypal dot com
2015-09-08  9:59 ` ekobylkin at paypal dot com
2015-09-08 10:06 ` ekobylkin at paypal dot com [this message]
2015-09-08 10:20 ` ekobylkin at paypal dot com
2015-09-18  9:29 ` ekobylkin at paypal dot com
2015-09-18  9:48 ` ekobylkin at paypal dot com
2015-09-18 12:55 ` ekobylkin at paypal dot com
2015-09-18 13:20 ` myllynen at redhat dot com
2015-09-18 14:06 ` ekobylkin at paypal dot com
2015-09-18 16:14 ` ekobylkin at paypal dot com
2015-09-18 16:37 ` ekobylkin at paypal dot com
2015-09-21  5:30 ` myllynen at redhat dot com
2006-07-02  8:31 [Bug localedata/2872] New: " edi at gmx dot de
2006-07-20 10:18 ` [Bug localedata/2872] " dsegan at gmx dot net
2007-02-17 19:24 ` drepper at redhat dot com
2007-02-17 22:17 ` edi at gmx dot de
2007-02-19  0:52 ` drepper at redhat dot com

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=bug-2872-131-oXe33D1yxz@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).