Bug 359320 - formatDateTime(..., KLocale::FancyShortDate, ... ) should take LC_TIME into account
Summary: formatDateTime(..., KLocale::FancyShortDate, ... ) should take LC_TIME into a...
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kdelibs4support
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-12 14:30 UTC by Arek Guzinski
Modified: 2025-04-06 18:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arek Guzinski 2016-02-12 14:30:40 UTC
This is related to my bugreport for akregator  https://bugs.kde.org/show_bug.cgi?id=359191 (theres a screenshot too), which turned out to belong to a frameworks component. I hope this is the correct component (probably not...), but after trying to find out which component exactly this belongs to for about 40 minutes, i had enough and took my best guess....

with the following env...
LANGUAGE=en_US:de
LC_TIME=de_DE.UTF-8

akregator shows the time as "MM/DD/YYYY hh:mm AM/PM", as opposed to "DD.MM.YYYY hh:mm", which is what i would expect with LC_TIME=de_DE.UTF-8.

What i would expect , vs what i get is (examples)
Expected       |     What i get
Yesterday 14:35     |  Yesterday 02:35 PM
29.01.2016 19:20  |   01/29/2016 07:20  PM

so in my opinion the function should translate the words based on LANGUAGE (as it does), but the numeric part based on LC_TIME, as this would be consistent with the Interface language being english and the date/time format being german

as a workaround, LANGUAGE=en_GB:de makes things a bit better for me

Reproducible: Always
Comment 1 Arek Guzinski 2025-04-06 18:16:41 UTC
The Problem is no longer present.