[wp-trac] [WordPress Trac] #19831: Multisite strings in standard translation
WordPress Trac
wp-trac at lists.automattic.com
Mon Mar 19 14:32:32 UTC 2012
#19831: Multisite strings in standard translation
--------------------------+------------------------------
Reporter: pavelevap | Owner:
Type: defect (bug) | Status: reopened
Priority: normal | Milestone: Awaiting Review
Component: I18N | Version: 3.3.1
Severity: normal | Resolution:
Keywords: |
--------------------------+------------------------------
Comment (by pavelevap):
There is no problem with string duplication, I guess. In administration
will be loaded default localization file + admin file and due to changes
in 19852 it will lead to specified increase.
I did not make any tests yet, but differences between original and
localized version in WP 3.3.1 were usually 6 - 8 MB. So when there will be
string increase of 10 %, then I would expect the same increase in memory
needed (0,5 - 1 MB). Too bad for localized versions, especially when these
strings are not needed.
The main purpose of this ticket was to DECREASE number of loaded strings
which are NOT needed by most of users. That means multisite strings which
were loaded by default. But the only way to achieve this is marking these
strings with multisite textdomain. So, I hoped, that there will be
autogeneration based on some directories (as it was in WP 3.3.1 - 482
strings) + strings which are located throughout other files, but we can
find them and mark them with multisite textdomain (estimated cca 100
strings). So there could be less strings loaded in the end. But now (based
on changes in ticket 19852) there is important increase of loaded strings.
Instead of estimated decrease somewhere to 3400 strings, we have 3838
strings (!) now.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/19831#comment:17>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list