public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pravin.d.s at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/17192] Local file for Chechen language
Date: Tue, 22 Jul 2014 12:11:00 -0000	[thread overview]
Message-ID: <bug-17192-131-agbsAj0kTT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17192-131@http.sourceware.org/bugzilla/>

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

Pravin S <pravin.d.s at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pravin.d.s at gmail dot com

--- Comment #1 from Pravin S <pravin.d.s at gmail dot com> ---
Created attachment 7719
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7719&action=edit
program for show ucs data in locale

1. Get iso code for language.  
2. Find existing locale in glibc near to chachen language or country for which
you trying locale. say xx_YY
3. compile show-ucs-data.c and run it on nearest locale xx_YY
4. fill this information for chachen language and submit here. will be good if
you highlight only the stuff that is different than xx_YY.

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


  parent reply	other threads:[~2014-07-22 12:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 10:35 [Bug localedata/17192] New: Local file for Chehcehn language s-o-f-t at mail dot ru
2014-07-22 10:56 ` [Bug localedata/17192] Local file for Chechen language s-o-f-t at mail dot ru
2014-07-22 12:11 ` pravin.d.s at gmail dot com [this message]
2014-07-22 13:02 ` s-o-f-t at mail dot ru
2014-07-31 12:12 ` yurchor at ukr dot net
2014-07-31 12:15 ` yurchor at ukr dot net
2014-08-01  9:14 ` s-o-f-t at mail dot ru
2014-08-01  9:16 ` s-o-f-t at mail dot ru
2014-08-14  6:01 ` s-o-f-t at mail dot ru
2014-08-19  7:58 ` yurchor at ukr dot net
2014-08-19  8:13 ` s-o-f-t at mail dot ru
2014-08-19  8:14 ` yurchor at ukr dot net
2014-08-19  8:21 ` s-o-f-t at mail dot ru
2014-08-25  6:12 ` s-o-f-t at mail dot ru
2014-08-25  8:54 ` pravin.d.s at gmail dot com
2014-08-25 11:53 ` s-o-f-t at mail dot ru
2014-08-25 12:23 ` s-o-f-t at mail dot ru
2014-08-28  6:48 ` s-o-f-t at mail dot ru
2014-08-28 10:08 ` pravin.d.s at gmail dot com
2014-11-25 10:13 ` yurchor at ukr dot net
2014-12-01 10:01 ` cvs-commit at gcc dot gnu.org
2014-12-01 10:33 ` siddhesh at redhat dot com
2014-12-01 11:46 ` pravin.d.s at gmail 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-17192-131-agbsAj0kTT@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).