This is a summary of the I18N Kickoff chat from April 21st.
- #20491 and #22229 are moved to the 4.6 milestone.
- To solve this the team will look into Jed https://slexaxton.github.io/Jed/ and its feasibility for core.
- For a possible comparison other libraries were named:
User Admin Language
- #32879 was closed as a duplicate of #26511.
- Having a
switch_to_locale()function is a precondition for #29783 and thus this feature is part of the 4.6 milestone.
- To push language packs to the next level, #34213 (Change priority for loading theme/plugin translations) and #34114 (Remove the requirement to call load_plugin_textdomain() or load_theme_textdomain()) are part of the 4.6 milestone.
- #34213 should go in early.
- #34114 needs a refresh and the tests should make use of the
- @swissspidy mentioned #18146 (Add user-level timezone setting) as an UX improvement similarly to #29783
- @ocean90: “Have to read that ticket in detail but one of the biggest task is probably to define the line between user setting and site setting.”
- @SergeyBiryukov volunteers to expand https://make.wordpress.org/core/handbook/best-practices/internationalization/
- @SergeyBiryukov mentioned #13651 and that it should finally get fixed.
- @ocean90 will review the latest patch.
- @ocean90 mentioned that the i18n report has a lot of tickets by @ramiy related to “Avoid using HTML tags in translation strings*” which need to be reviewed. One of the reasons why it’s good to have the handbook page ready as soon as possible.
- @ocean90 mentioned Ginger-MO https://github.com/dd32/ginger-mo, “a minimal .mo reader (with support for PHP & JSON representations), multiple text domains, and multiple loaded locales in the future” by @dd32.
It was decided that the first bug scrub for the i18n component is on Tuesday April 26th, 2016 at 18:00 UTC.
Full meeting logs: https://wordpress.slack.com/archives/core-i18n/p1461243825000006