Hi Ralf:

> One wish: In roundup we always had the international date format YYYY-MM-DD and
> it now (at least in my test instance) has mm / dd / yyyy  ... [traditional format
> ... is dd.mm.yyyy) so can we have the international format back as the default?
> I guess this *is* configurable?

Hmm, maybe not or at least not mixable (e.g. English locale with dd.mm.yyyy date
format).

The browser is supposed to handle the date format automatically. The date
(or datetime-local) input takes a YYYY-mm-ddTH:MM[:ss] format value and
displays it according to the browser's locale (or system date setting (Edge)).

If I change my chrome browser to use German (chrome://setting/language) and make
it the default display language for chrome and restart the browser, I see
31.12.2024 00:00 for a 2024-12-31T00:00 date value. I didn't need to refresh
the page, but if you don't see that maybe a page refresh would help.

What browser are you using and what language is its interface in?

AFAIK, there is no way to configure this outside of setting the locale.
It has to be handled at the tracker level by reverting to the text input
setting type="text" explicitly on a date/datetime display as shown at:

  https://sourceforge.net/p/roundup/code/ci/default/tree/doc/upgrading.txt#l292

> Concerning re-implementing date using python's datetime: [emulating edge cases in
> current date and lack of test coverage]

That's my concern too. I asked the question to see if anybody knew of any
blockers I don't know about.

-- rouilj