[wp-trac] Re: [WordPress Trac] #4260: Maintaining context of current plugin can simplfy i18n API

WordPress Trac wp-trac at lists.automattic.com
Sat Feb 9 19:48:13 GMT 2008


#4260: Maintaining context of current plugin can simplfy i18n API
--------------------+-------------------------------------------------------
 Reporter:  omry    |        Owner:  anonymous
     Type:  defect  |       Status:  new      
 Priority:  normal  |    Milestone:  2.5      
Component:  i18n    |      Version:           
 Severity:  normal  |   Resolution:           
 Keywords:          |  
--------------------+-------------------------------------------------------
Comment (by darkdragon):

 Reading over the discussion, I've come to the conclusion that the
 arguments made in the discussion are correct. Plugin authors should be
 responsible for maintaining l10n context. The API needs to maintain its
 optimized status and an decrease in performance such as this ticket could
 slow !WordPress down.

 I'm not going to close this ticket out, because I haven't looked at the
 code, nor did any profiling. I just don't think that the API for plugins
 and themes is that difficult, that it justifies something like this.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/4260#comment:3>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list