GNOME Bugzilla – Bug 347476
en_IN: day is misformed in appointments
Last modified: 2010-04-02 11:27:21 UTC
in Evolutions Calendar Create an appointment. It reports 12th July as Sunday whereas it should be monday. In fact every date is being reported as Sunday.
huh? what is your LOCALE? which version is this exactly? *where exactly* is this reported?
~$ evolution --version Gnome evolution-2.6 2.6.1 ~$ locale LANG=en_IN.UTF-8 LANGUAGE=en_IN:en LC_CTYPE="en_IN.UTF-8" LC_NUMERIC="en_IN.UTF-8" LC_TIME="en_IN.UTF-8" LC_COLLATE="en_IN.UTF-8" LC_MONETARY="en_IN.UTF-8" LC_MESSAGES="en_IN.UTF-8" LC_PAPER="en_IN.UTF-8" LC_NAME="en_IN.UTF-8" LC_ADDRESS="en_IN.UTF-8" LC_TELEPHONE="en_IN.UTF-8" LC_MEASUREMENT="en_IN.UTF-8" LC_IDENTIFICATION="en_IN.UTF-8" LC_ALL= Where? Evolution --> File --> New --> Appointment In the appointment form, under the text boxes for specifying the date and time. The date field says `Sunday 14 July 2006'. In the field `Sunday' does not change change for any date, although calendar that appears when i click on the drop down button shows the day correctly.
evil. i can confirm this, yes. this happens with every date chooser widget, also due date in tasks. i guess it's a translation issue, because evolution still abuses the translators to "translate" cryptic time format strings instead of using %x - see bug 336253. (and what happens if there is no po file for en_IN in evolution/po/ ? hmm.) anyway, be happy - only sundays, no more working days! ;-)
This bug has been identified on doing Evolution automation using LDTP.
ping any news on this?
Ubuntu bug about that: https://launchpad.net/evolution/+bug/85288
*** Bug 479496 has been marked as a duplicate of this bug. ***
I had a brief look at the relevant code... seems like Evolution does use %x Using Evolution from SVN trunk.. 2.21.5 (In reply to comment #3) > (and what happens if there is no po file for en_IN in evolution/po/ ? hmm.) > absolutely.. there is no en_IN translation
This had been fixed already, see the other bug. *** This bug has been marked as a duplicate of bug 525689 ***