public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/17426] en_IN: set date format
Date: Mon, 27 Aug 2018 10:20:00 -0000	[thread overview]
Message-ID: <bug-17426-716-rw1las1lZI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17426-716@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
I posted the patch here:

https://sourceware.org/ml/libc-alpha/2018-08/msg00514.html

but now after a little more research I think it needs further work.  Most of
the locales of India have the same d_fmt value, not just en_IN:

$ grep d_fmt localedata/locales/*_IN
localedata/locales/anp_IN:d_fmt       "%A %d %b %Y"
localedata/locales/ar_IN:d_fmt       "%A %d %B %Y"
localedata/locales/as_IN:d_fmt    "%e-%m-%Y"
localedata/locales/bhb_IN:d_fmt       "%A %d %b %Y"
localedata/locales/bho_IN:d_fmt       "%A %d %b %Y"
localedata/locales/bn_IN:d_fmt       "%A %d %b %Y"
localedata/locales/brx_IN:d_fmt       "%A %d %b %Y"
localedata/locales/doi_IN:d_fmt       "%A %d %b %Y"
localedata/locales/en_IN:d_fmt       "%d//%m//%y"
localedata/locales/gu_IN:d_fmt       "%A %d %b %Y"
localedata/locales/hi_IN:d_fmt       "%A %d %b %Y"
localedata/locales/hne_IN:d_fmt       "%A %d %b %Y"
localedata/locales/kn_IN:d_fmt       "%A %d %b %Y"
localedata/locales/kok_IN:d_fmt       "%A %d %b %Y"
localedata/locales/ks_IN:d_fmt       "%A %d %b %Y"
localedata/locales/mag_IN:d_fmt       "%A %d %b %Y"
localedata/locales/mai_IN:d_fmt   "%A %d %b %Y"
localedata/locales/mjw_IN:d_fmt        "%A %d %B %Y"
localedata/locales/ml_IN:d_fmt     "%A %d %B %Y"
localedata/locales/mni_IN:d_fmt       "%A %d %b %Y"
localedata/locales/mr_IN:d_fmt       "%A %d %b %Y"
localedata/locales/or_IN:d_fmt     "%Od-%Om-%Oy"
localedata/locales/pa_IN:d_fmt       "%A %d %b %Y"
localedata/locales/raj_IN:d_fmt       "%A %d %b %Y"
localedata/locales/sa_IN:d_fmt       "%A %d %b %Y"
localedata/locales/sat_IN:d_fmt       "%A %d %b %Y"
localedata/locales/sd_IN:d_fmt       "%A %d %b %Y"
localedata/locales/ta_IN:d_fmt       "%A %d %B %Y"
localedata/locales/tcy_IN:d_fmt       "%A %d %b %Y"
localedata/locales/te_IN:d_fmt       "%B %d %A %Y"
localedata/locales/ur_IN:d_fmt       "%A %d %b %Y"

while CLDR provides "d/M/yy" for most of them (this should translate to
"%-d/%-m/%y") but "dd/MM/yy" for en_IN (this should translate to "%d/%m/%y"). 
I think I should get this date format from CLDR for the locales supported by
CLDR and copy the same values to the locales which are not supported by CLDR.

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

  parent reply	other threads:[~2018-08-27 10:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 14:49 [Bug localedata/17426] New: date format not set for en_IN arjun.is at lostca dot se
2014-09-23 21:15 ` [Bug localedata/17426] " pranav913 at gmail dot com
2014-09-23 21:16 ` arjun.is at lostca dot se
2014-09-24 10:58 ` arjun.is at lostca dot se
2014-09-24 12:39 ` pravin.d.s at gmail dot com
2014-09-24 12:39 ` arjun.is at lostca dot se
2014-09-24 14:00 ` arjun.is at lostca dot se
2016-02-06  0:38 ` fweimer at redhat dot com
2016-02-06  0:51 ` [Bug localedata/17426] en_IN: set date format vapier at gentoo dot org
2018-08-10 12:57 ` digitalfreak at lingonborough dot com
2018-08-27 10:20 ` digitalfreak at lingonborough dot com [this message]
2018-08-27 22:26 ` cvs-commit at gcc dot gnu.org
2018-08-30 10:55 ` [Bug localedata/17426] Indian locales: set the correct " digitalfreak at lingonborough dot com
2018-09-04 21:56 ` digitalfreak at lingonborough dot com
2018-09-05 21:59 ` cvs-commit at gcc dot gnu.org
2018-09-05 22:06 ` digitalfreak at lingonborough dot com
2019-01-31 17:19 ` cvs-commit at gcc dot gnu.org

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-716-rw1las1lZI@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@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).