[wp-trac] Re: [WordPress Trac] #9730: The new date_i18n hook creates potential bugs in the admin interface

[WordPress Trac]

#9730: The new date_i18n hook creates potential bugs in the admin interface
-------------------------------+--------------------------------------------
 Reporter:  Denis-de-Bernardy  |       Owner:  Denis-de-Bernardy      
     Type:  defect (bug)       |      Status:  new                    
 Priority:  normal             |   Milestone:  2.8                    
Component:  i18n               |     Version:  2.8                    
 Severity:  major              |    Keywords:  has-patch tested commit
-------------------------------+--------------------------------------------

Comment(by hakre):

 yeah i think it is a good idea to stop at this certain level. this will at
 least offer a lot more possibilities.

 for the frontend / theme / widget areas some best practice suggestions
 should be made, like let's say, convert partially values (number of the
 year), convert it into a timestamp and the pass it over with the 'Y'
 formatstring to ''date_i18n()'' or ''mysql2date()'' with ''$translate =
 true''.

 plust +1 to have widgets with their own calendars. maybe archive strings
 are fixable, there is one myslq2date left i mean:

 {{{
                         $text = mysql2date($archive_day_date_format,
 $date, true);
 }}}

 line 838. will add a patch for that one.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9730#comment:25>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software