WordPress 5.5 ready to be translated

WordPress 5.5, planned for August 11, 2020, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.!

The stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are in the development projects. The strings for WordPress 5.4 have been moved to projects/wp/5.4.x.

As usual, a few of the new strings are related to updates to the block editor. Thus existing translations from the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ project have been copied to the WordPress project. The same was done for the WordPress Auto-updates feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., also part of WordPress 5.5.

Happy translating! 🌏🌍🌎

#announcement #5-5

Enhanced file references list for WordPress Core projects

The translatable stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. of WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. are split into four projects: Front end, Administration, Admin Network and Continents & Cities. To avoid the need for translating strings twice or more when they exist in multiple projects they are merged into the project with the initial occurrence.

Until now you wouldn’t know for sure if a stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. is only used in the front-end project or if it’s also used in the admin because the extracted file references were only for the first string occurrence.

To solve this the string extraction has been updated to preserve the references and comments during the merge task, allowing you to view the full list of file references. Following an example of a string that’s available for translation in the front-end project but is also used in the admin:
references

#announcement

Translation Editor & Locale Manager Vetting Criteria Page Draft

I’ve drafted a handbook page called “Translation EditorTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor & LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ Manager Vetting Criteria” in an effort to 1) provide more clarity on how global mentors assign PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves./GTEGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale./Locale Managers and 2) help locale teams set their own guideline.

Thanks, @tobifjellner @lidialab @evarlese @gperch for your initial feedback on the Google Doc.

There are some items that I’m still not sure if this page should include. Please leave a comment with your thoughts.

Keep in mind we are trying to come up with a minimum set of criteria as a guideline, rather than covering all the best practices and expectations.

  1. “(PTE) may suggest improvements of source texts back to the relevant developers”
    • I think this is a nice-to-have quality for a PTE but doesn’t have to be a requirement for a first-time PTE. I wouldn’t turn down someone from becoming a PTE just because they haven’t learned how to do this.
  2. “(PTE) joins the Global Make WordPress Slack via https://make.wordpress.org/chat/ & Locale specific Slack”
    • Same as above, I don’t think not being on global/local SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. is a blocker. I’d still grant someone a PTE role without joining Slack.
  3. “Role Removal Process” section
    • I added this section that was not in the Gdocs draft.

I will remove the callout saying “This handbook is still in progress” on the handbook page once we sort out the above items.

#documentation #announcement

Updated documentation for localized release packages

This is a short announcement for an update on the documentation for the release process of WordPress release packages with translations. The following handbook pages have been updated/created:

The overall recommendation remains unchanged: Ensure that every localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ is always eligible for automated release packagesAutomated Release Packages Automated release packages are release packages of locales that have no custom changes..

As of today all localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/, with only one exception, are already using automated release packages. 👏 To reflect this status in the handbook the documentation has been restructured and updated by removing outdated information and replacing complex descriptions with shorter and simple question/answer sections.

Here’s a summary of the updates:

  • The documentation for manual release packages has been moved into a separate page with a warning that it’s no longer actively supported.
  • The requirements for automated releases packages have been simplified into three simple rules:
    • Never had any custom changes
    • No custom changes for the current stable version
    • Minor custom changes for the current stable version
  • When working with the Translation Repository:
    • It’s no longer recommended to use the tags/ directory, only branches/ and trunk/. All existing tags already have been removed.
    • It’s not allowed to use the repositoryWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details. for other directories/files which are not related to WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
    • If you have made changes like a translated readme.html oder wp-config-sample.php you’re also responsible to keep up to date with the latest development and update the files accordingly.
    • It’s required that any by default included plugins are also hosted on the WordPress 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 Directory. They also must be declared as compatible with the latest stable WordPress release. Otherwise the plugin must not be bundled with the localized release packageRelease package release package is a packaged version of WordPress. That is, a ZIP file consisting of WordPress in its entirety, along with PO and MO files for core, the PO and MO files of default themes and Akismet, and any custom changes a locale has. In the past, most locales built their release package using the form in Rosetta’s dashboard..

Those rules exist to ensure the continued quality standard of the default WordPress release packages and to release localized release packages as fast as possible after an official WordPress release.

#announcement, #handbook

Back to 200 locales and new filters on translate.wordpress.org

After a small cleanup of unused localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ at the end of last year, the team is happy to announce that we’re back to 200 available locales in WordPress. Please welcome the recent additions of

There’re still some requests in the pending queue and we hope to process them as soon as possible to continue increasing the list of localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ teams.

Changes on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.

Last week the translation platform got an update:

New translation views for tables give a better overview over the currently selected filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output..

A view to show only translated stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings..
A view + count for the currently filtered strings.

The filters have been extended to allow limiting the term search by scope. For example search only in originals or only in references.

Use term scope and new options to further limit the strings.

Want to show only the translations that have a plural form? Now you can with the new “With plural” filter option.

Submitting a translation containing the UTF-8 characters → and ↵ is now possible. Very useful for the recently introduced “A → Z” stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor.

No limits anymore, just use → when you want.

And many other fixes:

  • Remove default sorting for untranslated view.
  • Highlight glossary terms on translation previews.
  • Fix multi-select for forward and backwards selections.
  • Fix mangled HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. tags in originals with some glossary entries.
  • Fix duplicate glossary tooltips for the same term.
  • Fix import of escaped unicodes in Android strings files.
  • Fix incorrect key in Apple strings file exports.
  • Fix querying translations by priority. 
  • Improve calculation of translation status counts.
  • Prevent adding duplicate glossary entries. 
  • and even more.

#announcement

WordPress 5.4 ready to be translated

WordPress 5.4, planned for March 31, 2020, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.!

The stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are in the development projects. The strings for WordPress 5.3 have been moved to projects/wp/5.3.x.

So far there are around 400 stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes. This already includes strings for the about page.
While string freezeString freeze The term "string freeze" is used by the core team to mark the end of changes to the strings of an upcoming release. A string freeze also means that there will be no more strings added to the core project. Sometimes a string freeze has two phases a soft freeze and a hard freeze. A string freeze is announced on the Polyglots blog by the current release lead. has been announced, depending on the severity changes may still occur.

A few of the new strings are related to updates to the block editor. Thus existing translations have been migrated to the WordPress project.

ℹ️ A good starting point is the Fuzzy view since many strings have been changed to use sentence case. This may not apply to your localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ so you can bulk approve many of them.

Happy translating! 🌏🌍🌎

#announcement #5-4

WordPress 5.3 ready to be translated

WordPress 5.3, planned for November 12, 2019, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.!

The stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are in the development projects. The strings for WordPress 5.2 have been moved to projects/wp/5.2.x.

So far there are around 380 stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes. The about page has not been updated yet. Soft string freezeString freeze The term "string freeze" is used by the core team to mark the end of changes to the strings of an upcoming release. A string freeze also means that there will be no more strings added to the core project. Sometimes a string freeze has two phases a soft freeze and a hard freeze. A string freeze is announced on the Polyglots blog by the current release lead. is announced for next week, October 7th.

Most of the new strings are related to an update of the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor (GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/). Existing translations have been migrated to the WordPress project.

WordPress 5.3 will also bundle a new default theme, called Twenty Twenty. Active development still happens on GitHub.
Twenty Twenty can be translated in the projects/wp-themes/twentytwenty project.

Happy translating! 🌏🌍🌎

#announcement #5-3

HelpHub & Handbook i18n Updates

Last edition: https://make.wordpress.org/meta/2019/06/20/helphub-handbooks-localisation/

HelpHub

HelpHub is a future home for all of the WordPress user documentation currently residing in the WordPress CodexWordPress Codex Living online manual to WordPress.org https://codex.wordpress.org/. Example of a HelpHub page: https://wordpress.org/support/article/overview-of-wordpress/

Since the last update, the docs team decided to turn on the HelpHub feature on Japanese & Serbian RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. site first as a trial.

After the trial period, it will be activated on all Rosetta sites that have active /support section.

Currently, there is no sync mechanism between the original English content and the translation. We are also talking with Docs team about how we handle the change notification process #.

Next Steps

  • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team will be helping with content import (ref) to prepare for the teams that want to have a copy of the original English documents.
  • LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ teams: let’s start discussing how we are going to collaborate in translation & keep track of the progress.

Handbook

Handbook on Rosetta site is a section under the /team/ P2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/. (o2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/.) where you can create sets of documentation with a menu sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. Example of a handbook on Rosetta site: https://ja.wordpress.org/team/handbook/

If your Rosetta site has a /team/ site already, the handbook will be automatically activated. If you need to have a /team/ site activated, post a request on this (polyglots) P2.

Information and example localized handbook can be found in the FAQ page in Polyglots Handbook.

Next Steps

  • Locale teams: decide which handbook(s) to translate and how to translate them.
  • We need to put together more information on how it works (e.g. ordering pages, creating multiple handbooks)

#announcement

Proposal for handling PTE requests

At WCEU, @petya, @nao, @casiepa, and @ocean90 have discussed the future of PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. requests.
The goal is to move them in a separated place (but still on this p2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/. site) and have the data of each request in a more structured format available.

Here are the notes:

Form to collect the data

Instead of the free form textarea we ask for the data via a form:

  • Maybe: Ask if 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/author or translators
  • Select plugin/theme slugs (autocomplete)
  • Select LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/(s)
  • List contributor(s) per locale
  • Form can be submitted by the theme/plugin author but also contributors
  • Request can include many projects/localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams//contributors

Validate the data

  • Does the contributor exist? (error)
  • Are the locales correct? (error)
  • Are the plugins/themes available?
  • Pre-requirements
    • Does the contributor have submitted at least 5? translations for the requested projects in the locale? (warning)
    • Check number of requested locales, maybe CLPTECross-locale Project Translation Editor A Cross-Locale Project Translation Editor is an account owned by a plugin or theme author (or the authoring organization), which uses professional translators to localize their product. The cross-locale project translation editor can import/validate strings on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor over multiple locales instead of one. Cross-Locale Project Translation Editors need to meet a set of criteria before being appointed by General Translation Editors.? (warning)
  • Is the contributor already an approved PTE? => Make they automatically a PTE for the new project?

Store the data in a custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept.

  • Benefit: Removes the requests from the index page of the polyglots p2

Output of requests

  • Table to list all requests, similar to teams page
  • Split requests into locales
  • Filterable by locale, date, …
  • Notifications to all GTEs
  • Link to the project on translate.w.org with active user filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.
  • Tell the GTEGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. whether the user is already a PTE
  • Approve button for GTE without visiting the wp-admin for all GTEs
  • Show some stats about the user
  • Send reminder about requests that are two weeks old, automatically approve a week after the reminder?
  • Post request on the team p2 or just summary/activity log
  • Show comments from team p2 at the global requests (depends on previous point, discussions need to be in English)
  • Show the “Resources for translation contributors” in the request (automated comment, see French, …)
  • Reject with feedback only with predefined reasons (grammar, punctuations, typos, style guide)
  • (Nice to have) Activity log for each new PTE (user x by user y/automatically) on date)

Open TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets

Next steps

Please let us know what you think about this proposal. Do you have any suggestions or can you provide some mockups for how a list of requests or a detail page of a request can look like? What would be a good minimum viable productMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia (MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia), what are the must haves for a first version?
Are you a developer and can help us with the implementation?

Whatever you have, please let us know in the comments. Thank you!

#announcement, #wceu

WordPress 5.2.1 comes with string changes

The first Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. of WordPress 5.2.1 has been released.

WordPress 5.2.1-RC1

This minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. includes a few string changes which are already available for translation on https://translate.wordpress.org/projects/wp/dev and https://translate.wordpress.org/projects/wp/dev/admin.

The release is scheduled for Tuesday, May 21.

#announcement #5-2

Updated Editor Interface

Since translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. exists the design has only slightly changed, mostly to match the wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ design. But what has not changed is the editor for adding translations. This has changed as of today. ✨

Before

Here are some before screenshots. While the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. was very basic it was also limited at the same time, preventing adding more tools to the editor.

Continue reading

#announcement, #meta3522, #meta4430, #meta4431

WordPress 5.2 ready to be translated

WordPress 5.2, planned for May 7, 2019, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.!

The stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are in the development projects. The strings for WordPress 5.1 have been moved to projects/wp/5.1.x.

So far there are around 200 stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes. The about page has not been updated yet.
Most of the new strings are related to the new Site Health page, a subpage of Tools. This was previously maintained as a plugin. Existing translations have been migrated to the WordPress project.

Please note that WordPress 5.2 will increase the minimum required PHP version to 5.6.20. If your localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ uses a translated readme please ensure that the readme for 5.2 includes the new requirements.

Happy translating! 🌏🌍🌎

#announcement #5-2

Start translating WordPress 5.1

WordPress 5.1, planned for February 21, 2019, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.!

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 stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes. The about page has not been updated yet.
You’ll find a few stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. related to pausing or resuming themes/plugins. These are part of the new “PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.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 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 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 freezeString freeze The term "string freeze" is used by the core team to mark the end of changes to the strings of an upcoming release. A string freeze also means that there will be no more strings added to the core project. Sometimes a string freeze has two phases a soft freeze and a hard freeze. A string freeze is announced on the Polyglots blog by the current release lead. means that no more new stringsString A string is a translatable part of the software. A translation consists of a multitude of localized 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 LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ Managers with commit access on the /dist repositoryWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details..

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 stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. will have to be translated within the inline PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.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.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.

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 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 with the proper language tag or subtag. For example, the French (Belgium)” Locale would be .

You can find the correct tag/subtag to use for your Locale in the translation of html_lang_attribute string in GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.. Here is an example with en-GB.

How to deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. 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

WordPress 5.0.3 has been released

WordPress 5.0.3 has been released. It is a maintenance release with some stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes.

WordPress 5.0.3 Maintenance Release

In order to benefit from the automated release process it might be possible that you have to prepare your localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ first and/or need to translate the new stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings..

#5-0, #announcement