[kleopatra] [Bug 358666] Short dates are used everywhere in the UI

[Andre Heinecke via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358666

--- Comment #3 from Andre Heinecke <aheinecke at intevation.de> ---
Hi,

> (In reply to Andre Heinecke from comment #1)
> > Kleopatra uses QLocale::ShortFormat for dates.
> 
> Correct. Says so in the title of this bug report.

As far as I understood you the original report was about: "(e.g., Thu 28 Jan)" 
So not including the Year and this is what you meant by ambiguous. Which I took
down as "Bad configuration"

> > I think this is the correct behavior respecting the users settings.
> 
> Which is why this bug report says the expected format should be either "a
> full date according to locale (but that's ambiguous thanks to Americans
> being weird like that), or perhaps better, an ISO-8601 date".

Why do you think a short date is ambiguous? It's the same date but in a
different format.

> I do not expect Kleopatra to offer options beyond what is provided by the
> system-wide locale settings, so using QLocale::LongFormat would be fine, but
> at the moment the interface is pretty useless since it does not allow you to
> unambiguously determine certificate validity dates due to using an
> inappropriate date format.
>
> Can you tell me how do *you* check your certificates' expiry dates in
> Kleopatra?

Again, I do not understand what you find so ambiguous about short dates. On my
system the short format is (DD/MM/YYYY). While the Long format would include
Weekday, and Month name. Including Weekday and Month I would find unnecessary
information in Kleopatra and would help further clutter the interface.

> And thank you so much for allowing the opportunity to respond before closing
> the ticket, by the way.

You can always respond (as you did) even to closed or resolved tickets. If one
does not change the status directly tickets tend to "rot" in my experience.

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