[wp-trac] [WordPress Trac] #51123: commonL10n removed without backwards compatibility
WordPress Trac
noreply at wordpress.org
Tue Aug 25 02:12:21 UTC 2020
#51123: commonL10n removed without backwards compatibility
---------------------------+------------------------------
Reporter: kbjohnson90 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Script Loader | Version: 5.5
Severity: normal | Resolution:
Keywords: | Focuses: javascript
---------------------------+------------------------------
Comment (by TimothyBlynJacobs):
Replying to [comment:5 peterwilsoncc]:
> I am also very slightly concerned such an approach makes the changes in
the earlier commits a little redundant as the `commonL10n` object remains
in memory, it simply results in requiring the `wp-i18n` script as a
dependency for each of the files.
Does `wp-i18n` cache translations? If not, there might be performance
benefit to storing the translated version of an object.
There is also the question of strings that were changed to use `_n` since
it requires the number of results to give a result.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/51123#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list