1 Prettydate creates strings like this: _Last edited in the wee hours of Tuesday night, July 1st, 2009_. However, July 1st is a Wednesday, so either date or Weekday should be modified. In the spirit is probably _Tuesday night, June 30th_. --ulrik
3 > The default prettydate times are fairly idiosyncratic to
4 > how [[Joey]] thinks about time. Specifically, it's still
5 > Tuesday night until he wakes up Wednesday morning -- which
6 > could be in the afternoon. :-P But, Joey also realizes
7 > that dates change despite his weird time sense, and so
8 > July 1st starts at midnight on Tuesday and continues
9 > through Tuesday night and part of Wednesday.
11 > (This might not be as idiosyncratic as I make it out to be..
12 > I think that many people would agree that in the wee hours
13 > of New Years Eve, when they're staggering home ahead of
14 > the burning daylight, the date is already January 1st.)
16 > I think the bug here is that prettydate can't represent
17 > all views of time. While the times
18 > of day can be configured, and it's possible to configure it
19 > to call times after midnight "Wednesday morning, July 1st",
20 > it is not possible to configure the date or weekday based
23 > In order to do so, prettydate's timetable would need to be
24 > extended to include the "%B %o, %Y" part, and that extended
25 > to include "%B-", "%o-", and "%Y-" to refer to the day
30 >> fair enough, I think I can get converted to a warped time perspective. --ulrik
32 >>> Perhaps we can consider this [[done]], then? --[[smcv]]