So, after looking into this, I didn't have to get into too many
languages before realizing there isn't a one-size-fits-all solution that
can be addressed in the source code.

For example, I the code /could/ check nl_langinfo(D_FMT) to see whether
the month or day goes first, and that would solve the MM DD YYYY <--> DD
MM YYYY complaints that are part of this ticket.

However there are all kinds of other issues and combinations, for
example en zh_CN the weekday should go after the date, rather than
before, and always prefers year-month-day rather than day-month-year or
month-day-year. And there are several other issues.

In the end, I think this has got to be fixed on a locale-by-locale basis
by the translators. However, indicator-datetime's code /can/ make this a
lot less painful / more likely to actually happen. I've added copious
translator comments to lp:~charlesk/indicator-datetime/lp-1001595 to
help make this happen.

** Changed in: indicator-datetime
       Status: Triaged => In Progress

** Changed in: indicator-datetime (Ubuntu)
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1001595

Title:
  Clock does not respect regional settings

Status in The Date and Time Indicator:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  In Progress

Bug description:
  The clock unity applet (or indicator) have an option to show a date.
  Regional settings are set to show the date as "19 may", but the clock
  shows "may 19" instead. After clicking on a clock, in a calendar, it
  shows properly — 19 may 2012.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1001595/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to     : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to