• Karl Ove Hufthammer's avatar
    Properly handle timezones and user’s preferred date format in bundles · 127e81f1
    Karl Ove Hufthammer authored
    Before: The ‘created’ and ‘updated’ times were stored as datetimes
    in the author’s time zone, but *without* a time zone marker. If a
    different user had a different time zone, the time displayed would
    be wrong (e.g., it could be a datetime in the future). Also, the
    format of the displayed time was a strange mix of locale-aware
    stuff (e.g. localised month names) and non-locale aware stuff
    (the order of the different components in the datetime).
    
    Now: The times are always stored as UTC datetimes, with an explicit
    datetime marker (‘Z’). (So no information about the author’s
    location is leaked.) They are always shown in the user’s preferred
    short datetime format (and in the user’s time zone).
    
    The above is true for ‘created’ and ‘updated’ times stored as
    actual datetimes. Older versions of Krita only stored the date,
    and in the fixed ‘dd/mm/yyyy’ format. For these bundles, the date
    is displayed in the user’s preferred short date (not datetime)
    format.
    127e81f1
Name
Last commit
Last update
..
animationrenderer Loading commit data...
buginfo Loading commit data...
clonesarray Loading commit data...
colorrange Loading commit data...
colorspaceconversion Loading commit data...
imagesize Loading commit data...
imagesplit Loading commit data...
layergroupswitcher Loading commit data...
layersplit Loading commit data...
metadataeditor Loading commit data...
modify_selection Loading commit data...
offsetimage Loading commit data...
pykrita Loading commit data...
qmic Loading commit data...
resourcemanager Loading commit data...
rotateimage Loading commit data...
separate_channels Loading commit data...
shearimage Loading commit data...
waveletdecompose Loading commit data...
CMakeLists.txt Loading commit data...
Mainpage.dox Loading commit data...