Localized dates in tasklist (US vs EU notation)

[Adam Porter]

Right now the task list due-date formats are verbose and confusing. I'm in the USA, so I have to invert all the m/d to d/m, which is a bit confusing.

The GNU coreutils can handle dates in a variety of formats, somewhat free-form, so it seems like there should be a good Python module available to handle a wider variety of date formats. What I'd really like is to be able to use a format like "23 jan", which is unambiguous and easy to type.

BTW, could we also do away with the "d:" and just use, e.g. "[23 jan]" for the due date? When I'm inputting a lot of tasks with due dates, as I have over the past few days of entering my class schedules, all the extra "d:" adds up after a while.

[Jaap Karssenberg (jaap.karssenberg)]

Problem now is that e.g. difference between m/d and d/m may differ
throughout a notebook and zim can not automatically detect it for
dates like "1/2". So we need a precise representation.

Development is ongoing to make due dates more user friendly, but
depends on the "inline objects" feature. Basically this means that the
date will be an object (or "special field" in the jargon of word
processors) such that it's internal representation and it's user
representation can be seperated. In this way we store internally the
full "YYYY-MM-DD" but we can show the user e.g. "23 jan" based on
preferences. In addition clicking the date would bring up a calendar
widget, so it can be changed in an intuitive way.

-- Jaap

[Adam Porter (alphapapa)]

Another comment that apparently went to /dev/null.
----
from Adam Porter <email address hidden> via gmail.com
to Bug 920806 <email address hidden>
date Tue, Jan 24, 2012 at 16:07
subject Re: [Bug 920806] [NEW] Task list: better date formats
mailed-by gmail.com

You've read my mind, as usual, Jaap: I was hoping for a separation of
the internal format from the display format. Is there anything I can
do to help with this feature? My Python knowledge is rather
rudimentary.