[Bug localedata/17426] en_IN: set date format

["digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>]

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

Rafal Luzynski <digitalfreak at lingonborough dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |digitalfreak@lingonborough.
                   |                            |com

--- Comment #6 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
I've just checked few locales in CLDR and they seem to copy the content of
d_fmt in glibc locale data (which is later used by `date +%x') from  Date &
Time -> Gregorian -> Formats - Standard - Date Formats -> short.  For en_IN is
says "dd/MM/yy" which translates to "%d/%m/%y" in glibc terms.  Also I saw that
some locales do not follow strictly the rule when it says "only 2 digits for a
year" and they use four digits instead.  (That means: they use "%Y" instead of
"%y".)  So for me it is fine to set d_fmt for en_IN to "%d/%m/%y" if nobody
opposes or "%d/%m/%Y" if you prefer this.

(In reply to Arjun Shankar from comment #5)
> [...]
> I must add that the format string guideline [4] is not clear upon the
> difference between 'y' and 'yy', but it appears to me from the examples that
> 'y' represents the full year '2014' and 'yy' represents the year with the
> century truncated '14'.
> 
> [...]
> 
> [4] http://cldr.unicode.org/translation/date-time

The link says that 'y' is as many digits as necessary while 'yy' is always
exactly 2 digits (truncated) and 'yyyy' is always exactly 4 digits (zero padded
IIUC).

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