[wp-trac] [WordPress Trac] #19852: Don't load admin strings on the frontend

WordPress Trac wp-trac at lists.automattic.com
Thu Mar 22 09:11:17 UTC 2012


#19852: Don't load admin strings on the frontend
----------------------------+-----------------------
 Reporter:  nacin           |       Owner:
     Type:  task (blessed)  |      Status:  reopened
 Priority:  normal          |   Milestone:  3.4
Component:  I18N            |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by pavelevap):

 >  * Move wp-login.php strings to wordpress-admin.pot and load wordpress-
 admin.pot on wp-login.php.
 Yes, there would be less strings for frontend, but I am not sure if it is
 needed. There were more than 2000 strings removed from frontend, so moving
 some others is a good idea, but it is not such a pain as increased total
 number (frontend + admin).
 >  * Create a single wordpress-ms.pot that contains 136 strings from wp-
 includes MS, wp-activate, and wp-signup.
 Yes, it would be helpfull, but another localization file and another
 GlotPress project is not so fine for translators. What about adding these
 strings to current multisite admin? And rename multisite admin to only
 multisite? So, all multisite strings would be loaded also on frontend?

 > There are 265 multisite strings that were in the ms pot before but are
 now in either the frontend (136) or admin (129) pot.
 Yes, this is the main problem (regression). Is it possible to move these
 strings back to only multisite installations (and load for example all
 multisite strings on frontend and backend)? There are up to 500 strings
 total, so it is not such a pain. Or at least 129 strings from admin pot
 can be moved back to multisite admin pot?

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


More information about the wp-trac mailing list