public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arjun.is at lostca dot se" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/17426] New: date format not set for en_IN
Date: Tue, 23 Sep 2014 14:48:00 -0000	[thread overview]
Message-ID: <bug-17426-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17426
           Summary: date format not set for en_IN
           Product: glibc
           Version: 2.20
            Status: NEW
          Severity: normal
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: arjun.is at lostca dot se
                CC: libc-locales at sourceware dot org

executing:
$ LC_TIME=en_IN.UTF-8 date +%x

prints:
Tuesday 23 September 2014

This isn't the format used in India.

I have typically seen DD-MM-YY(YY) or DD/MM/YY(YY) in use in most places
including official tax forms, etc.

Here is the link to a copy of the Constitution of India:
http://india.gov.in/my-government/constitution-india/constitution-india-full-text

It appears to consistently use "DD-MM-YYYY" (when I looked at the main "Parts I
to XXII" document).

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


             reply	other threads:[~2014-09-23 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 14:48 arjun.is at lostca dot se [this message]
2014-09-23 16:26 ` [Bug localedata/17426] " pranav913 at gmail dot com
2014-09-23 18:23 ` arjun.is at lostca dot se
2014-09-24 10:25 ` arjun.is at lostca dot se
2014-09-24 11:24 ` arjun.is at lostca dot se
2014-09-24 12:16 ` pravin.d.s at gmail dot com
2014-09-24 13:59 ` arjun.is at lostca dot se

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-17426-131@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).