Start translating WordPress 5.1

WordPress 5.1, planned for February 21, 2019, is now ready to be translated on translate.wordpress.org!

The strings are in the Development project at https://translate.wordpress.org/projects/wp/dev. The strings for WordPress 5.0 have been moved to https://translate.wordpress.org/projects/wp/5.0.x.

So far there are ~140 string changes. The about page has not been updated yet.
You’ll find a few strings related to pausing or resuming themes/plugins. These are part of the new “PHP Fatal Error Protection” feature. You can read more about this in the dev note:

PHP Site Health Mechanisms in 5.1

Happy translating! 🌏🌍🌎

PS: If you provide translations for the readme and/or sample config file, please read this post.

#announcement #5-1

WordPress 5.1 String Changes in HTML/PHP Files

WordPress 5.1 Beta 3 is currently scheduled for release on January 29th. This release will also mark the soft string freeze point for the 5.1 release. A soft string freeze means that no more new strings can be introduced or changed in the codebase. The only exception is the About page in the admin.

5.1 introduces some changes to files that cannot use gettext. These files will require manual translation and deployment from Locale Managers with commit access on the /dist repository.

wp-config-sample.php

In #41000, changes were made to replace “blog” and “Happy blogging” terms with “site” and “Happy publishing”.

In wp-config-sample.php, the following string will have to be translated within the inline PHP comment (so that non-English speakers are able to understand how to configure their WordPress site). This comment is located on line 82:

/* That's all, stop editing! Happy blogging. */

is replaced with:

/* That's all, stop editing! Happy publishing. */

readme.html

In the readme.html file, the term “blog” has also been replaced with “site”. This string occurs on line 29.

#44955 also introduced the lang attribute to the <html> tag in the readme.html file (line 1). This is especially useful for users relying on assistive technologies to help indicate the primary language of the document.

Locale Managers with commit access must replace <html lang="en"> with the proper language tag or subtag. For example, the French (Belgium)” Locale would be <html lang="fr-be">.

You can find the correct tag/subtag to use for your Locale in the translation of html_lang_attribute string in GlotPress. Here is an example with en-GB.

How to deploy your translations

To internationalize or localize components of WordPress that cannot use gettext, Locale Managers with commit access will need to replace the English version of the files with a manually translated version.

Then they have to commit them via the /dist directory in i18n.svn.wordpress.org.

Hard String Freeze and 5.1 Release

The hard string freeze for WordPress 5.1 will coincide with 5.1 RC1, which is currently scheduled for February 7th. A hard string freeze means that no more string changes will happen in the codebase, even on the About page.

The final release of WordPress 5.1 is currently scheduled for February 21, 2019.

You can read more about the schedule on the 5.1 Development Cycle page.

#5-1, #announcement