Follow-up Comment #5, task #2614 (project savane):

Ok, I'm a bit puzzled right now.

---------------------

Having utils_format_date() deprecating format_date() seems quite hard to
understand. For now on, there are a few aliases that are exactly like the
function they are aliases of without the first part (utils_). And then, here,
we have format_date()  that would not be an alias of utils_format_date()?
Ouch!

Also, in fact, why cant we just add an extra parameter to format date so
nothing in the code would have to be changed, we should just have to get
format_date used where it is missing?

----------------------

Short and minimal are too long. When we want minimal, we want "18.11.2005" or
"18/11/2005", nothing longer. And short provide a long month name but it miss
the hour.
 
Finally, it is not the clean way to put up a default which is not a localized
one. We we certainly not waste time to manage every possible locale on earth
while date() already do that.
To make it clear, the only date strings that should be used are:

       %c     locale’s date and time (Sat Nov 04 12:02:33 EST 1989)
and
       %A     locale’s full weekday name, variable length
(Sunday..Saturday)
       %x     locale’s date representation (mm/dd/yy)
       %X     locale’s time representation (%H:%M:%S)

The others are not acceptable. To get something working, I think we should
have

normal = "%A %x at  %X " with the seconds striped, cause we dont care of
seconds, and with "at" inside, something a little verbose, not just numbers
short = "%x at %X" with the seconds striped, would be used in tables and
things like that
minimal =  "%x", that would be used for instance in feature boxes.

If we can't strip seconds from %X, then we'll be forced to use %R. 

---------------------------

$sys_datefmt only purpose is for an installation to force something. It
should not be used actually but most installation, only on rare occasions.
We should not care about it, only make sure it is taken into account.






    _______________________________________________________

Reply to this item at:

  <http://gna.org/task/?func=detailitem&item_id=2614>

_______________________________________________
  Message posté via/par Gna!
  http://gna.org/


_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev

Reply via email to