<div dir="ltr">👍<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 14, 2023 at 12:25 PM Tobias Leupold <<a href="mailto:tl@stonemx.de">tl@stonemx.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Am Freitag, 14. April 2023, 08:27:20 CEST schrieb <a href="mailto:josephj@main.nc.us" target="_blank">josephj@main.nc.us</a>:<br>
> Nerd answer: Just provide a place to add a strftime format string and make<br>
> everybody happy (at least those who know what strftime is). :)<br>
> <br>
> Joe<br>
<br>
But that would not allow heuristics to distinguish short periods of time from <br>
longer ones. And this is IMHO something that should not be configurable. Or at <br>
least, adding such decision rules in a configurable way would require a quite <br>
big and complex configuration dialog. I'm not sure if this would be "too much" <br>
for the aber KPA "User" (no developer, no coder, not even an enthusiast) ...<br>
<br>
> <br>
> > Am Mittwoch, 12. April 2023, 13:27:11 CEST schrieb Tobias Leupold:<br>
> >> Am Mittwoch, 12. April 2023, 06:22:07 CEST schrieb Per Funke:<br>
> >> > "1.83 y/m/d ago" is unconventional but attractive<br>
> >> > IMHO,<br>
> >> > Per Funke<br>
> >> <br>
> >> Hmmm ... I think this would be too unconventional, especially facing the<br>
> >> fact that a year is not divided into decimal units (it's 12 months after<br>
> >> all, not 10).<br>
> > <br>
> > Maybe it's just me, but using decimal representation for time units does<br>
> > not<br>
> > seem so odd. "1.83 years ago" is easy to read and understand, even if one<br>
> > does<br>
> > not intuitively realize that it is the same as "1 year, 9 months, 28 days,<br>
> > 19<br>
> > hours 20 minutes ago".<br>
> > Plus: it eliminates the need to come up with a universal way to shorten<br>
> > this<br>
> > (should it be 1 year, 10 months, or 1 year, 9months, almost 29 days?).<br>
> > <br>
> > Would a hybrid approach work better in your opinion? I.e. "1 year, 9.96<br>
> > months". This does arguably combine the best and worst of both approaches:<br>
> > <br>
> > - ugly to compute (depends on the length of the month)<br>
> > - decimal point in non-decimal unit (e.g. "4.6 months")<br>
> > + canonical representation (always "X years, Y months", no complicated<br>
> > heuristic needed)<br>
> > + more intuitive than pure decimal notation ("1 year 9.96 months ago" vs<br>
> > "1.83<br>
> > years ago")<br>
> > <br>
> >> Any objections if I implement this in a way I would expect it to be<br>
> >> (both<br>
> >> for birthdays/ages and timespans) soonish and you all have a look at it<br>
> >> then?<br>
> > <br>
> > Sure - I'll gladly take a look at that work branch and comment on it ;-)<br>
> > <br>
> > Cheers,<br>
> > <br>
> > Johannes<br>
<br>
<br>
<br>
<br>
</blockquote></div>