https://bugs.kde.org/show_bug.cgi?id=393956
--- Comment #18 from pallaswept <pallasw...@proton.me> --- (In reply to Aaron Wolf from comment #17) > I think this is easy enough that someone able to hack on this at all could > figure out this step. There is no difficulty in figuring it out. The difficulty is that once we do figure it out, it becomes apparent that the only solutions are either, one of various messy hacks, or a wait for upstream - so the best solution is upstream. I am very hesitant to put in work on this, only to deliver an almost-solution and a let-down. That's why I looked into limitations like this (and other things like milliseconds) Still, let us not ignore that this issue has been open for some 7 years now. I would not be sane, to make changes which will *require* a future developer to maintain my spaghetti code. It's obvious that such a developer might not even exist. I'd be creating an unsustainable maintenance burden, and a clock that will break in the future, which I'm sure everyone can agree, is even worse than a clock which lacks a desired formatting option. I do understand that this feature is important to you, so I'll spend some extra time trying to find the least-spaghetti way to deal with it, and see if I can make something practical... but no promises. The official answer from me is "not supported upstream, sorry". I'll see what I can do. -- You are receiving this mail because: You are watching all bug changes.
