https://bugs.kde.org/show_bug.cgi?id=494521
Luke Horwell <c...@horwell.me> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |CONFIRMED
--- Comment #7 from Luke Horwell <c...@horwell.me> ---
(In reply to popov895 from comment #5)
>
> So it looks like this is an intentional change in Qt 6.8. Therefore, it
> seems reasonable to me that KIO should use its own "long" format to display
> the date/time. Actually, I don't see any point in displaying the timezones
> here at all, because the creating/modification time should be converted to
> the user's local timezone.
I agree. This makes sense. The code for this is at
src/widgets/kpropertiesdialogbuiltin_p.cpp in the "kio" repository. It directly
uses a QLocale which only has 3 format types: LongFormat, ShortFormat,
NarrowFormat, confirming Qt 6.8's QLocale changed the behaviour.
I didn't see a way with Qt alone to exclude the time zone when formatting, so
having KIO handle a "long format without time zone" seems like a good idea.
Perhaps it could be as simple as taking the time zone string (e.g. "British
Summer Time") and subtracting that from the original 'long' output? (I'm just a
user however, not a KDE developer)
As a local hack, one could patch their own copy by forcing their desired date
format:
> - d->m_ui->modifiedTimeLabel->setText(locale.toString(dt,
> QLocale::LongFormat));
> + d->m_ui->modifiedTimeLabel->setText(dt.toString(QStringLiteral("dddd d
> MMMM yyyy, hh:mm:ss")));
--
You are receiving this mail because:
You are watching all bug changes.
