I18N Kickoff for 4.6 Chat Summary

This is a summary of the I18N Kickoff chat from April 21st.

Attendees: @petya, @SergeyBiryukov, @swissspidy, @ocean90

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

User Adminadmin (and super 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.

Language Packs

  • To push language packs to the next level, #34213 (Change priority for loading theme/pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party 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 WP_LANG_DIR constant.

Database Collation

  • No decision was made for #32405 because @pento wasn’t around.

Other Tasks

  • @swissspidy mentioned #18146 (Add user-level timezone setting) as an UXUX User experience improvement similarly to #29783
    • @ocean90: “Have to read that ticketticket Created for both bug reports and feature development on the bug tracker. 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 patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..
  • @ocean90 mentioned that the i18n report has a lot of tickets by @ramiy related to “Avoid using HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. tags in translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. 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 PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher & JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. representations), multiple text domains, and multiple loaded locales in the future” by @dd32.
    • @swissspidy asked what this would mean for #17268.
    • (after the chat) @dd32: “As for Ginger-MO, my main intention was so we *didn’t* have to use the native gettext tools. I built it with one aim – To get English (US) and non-English pageloads closer to eachother in terms of performance.”

Bug Scrub

It was decided that the first bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. 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

#4-6, #i18n