Welcome to the official blog of the translator team for the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.
We’d love for you to help out!
Translate WordPress
You can help translate WordPress to your language by logging in to the translation platform with your WordPress.orgWordPress.orgThe 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/ account and suggesting translations (more details).
We have meetings every week on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. in polyglots (the schedule is on the sidebarSidebarA 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. of this page). You are also welcome to ask questions on the same channel at any time!
Posting here
In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.
WordPress 5.9, planned for January 25, 2022, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins.!
The new stringsStringA 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.8 have been moved to projects/wp/5.8.x.
As for previous releases, most of new strings are related to updates to the blockBlockBlock 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. Thus existing translations from the GutenbergGutenbergThe 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. WordPress 5.9 is now in soft string freezeString freezeThe 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.. The remaining strings for the updated about page and a new welcome panel should follow soon.
A note for localesLocaleLocale = 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/ which have also translated wp-config-sample.php and/or readme.html: There were some updates which you may want to adopt in your localized file. You can find the changes in this and this changeset (green means new).
You may have noticed a few new projects on Translate: Patterns and Meta > Pattern Directory. These projects were created to help provide a localized version of the new BlockBlockBlock 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. Pattern Directory.
The Pattern Directory will act similarly to the Theme and PluginPluginA 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 directories, allowing users to search for unique block patterns to use on their sites via https://wordpress.org/patterns/.
Block patterns are a streamlined way to add pre-designed block layouts to your site. As both the use and features of block patterns expand, the Pattern Directory is expected to launch along with the upcoming July 20th, 2021 WordPress 5.8 release.
Help Translate the Block Patterns
After the WordPress 5.8 translation is complete, you can help to create a localized experience of this new feature by translating the Block Patterns included in the new directory via:
This is a great project to encourage new or not currently active translation contributors to get involved in! Many Patterns have a small number of stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings., and it’s very easy to find the context – the References section shows a link to preview the Block.
Though patterns will be called from coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. WordPress via search in the Block Editor in the future, the translation percentage of the above project does not affect the core release threshold. In other words, the highest priority for translations remains the same: releasing the core language pack.
Please note there still are some open issues around i18nInternationalizationInternationalization (sometimes shortened to I18N , meaning “I - eighteen letters -N”) is the process of planning and implementing products and services so that they can easily be adapted to specific local languages and cultures, a process called localization. This is the process of making software translatable. Information about Internationalization for developers can be found in the Developer’s handbooks. of the directory (RTL, categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., strings in .jsonJSONJSON, 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. file are not deployedDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. yet).
What’s coming next
The future of the Block Pattern Directory will include third-party, user-generated block patterns. The mechanism for translating these block patterns has not been finalized. This is a great time to follow the related conversations and help weigh in on the future of how to translate user-generated block patterns.
There are a few possibilities being discussed, including:
Building a localeLocaleLocale = 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/ picker in the Block Pattern Directory to filterFilterFilters 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. block patterns by language, i.e. https://ja.wordpress.org/patterns/
Creating a localized copy of each locale, similar to forking an existing block pattern.
Conversation around how to translate user-generated block patterns in the future is happening on this proposal from@tellyworth, and will continue to happen in #core and #core-editor chats in the future. Updates on these discussions will also be included in the regular Polyglots weekly meetings and on the Make/Polyglots blog as well.
Thanks to @nao and @dd32 for helping to write this post!
WordPress 5.8, planned for July 20, 2021, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins.!
The new stringsStringA 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.7 have been moved to projects/wp/5.7.x.
As for previous releases, most of new strings are related to updates to the blockBlockBlock 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. Thus existing translations from the GutenbergGutenbergThe 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. So far there are ~90 (+350 if Gutenberg project was not translated) new strings and ~80 strings had a partial match and thus marked as fuzzy. Strings for the updated about page should follow soon.
Happy translating! 🌏🌍🌎
A note for localesLocaleLocale = 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/ which have also translated wp-config-sample.php and/or readme.html: There were some slightly wording updates which you may want to adopt in your localized file. You can find the changes in this and this changeset (green means new).
WordPress 5.7.2 has been released. It is a security release. There are no stringStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. changes in the main project.
In order to benefit from the automated release process it could be possible that you have to prepare your localeLocaleLocale = 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.
WordPress 5.7.1 has been released. It is a security and maintenance release. There is one stringStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. change in the main project.
In order to benefit from the automated release process it could be possible that you have to prepare your localeLocaleLocale = 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.
WordPress 5.7, planned for March 9, 2021, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins.!
The new stringsStringA 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.6 have been moved to projects/wp/5.6.x.
Some of the new strings are related to updates to the blockBlockBlock 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. Thus existing translations from the GutenbergGutenbergThe 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. So far there are 280 new strings and 30 strings have been fuzzied. Strings for the updated about page should follow soon.
Happy translating! 🌏🌍🌎
Required translation status for coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. language packs
On a related note, the requirement to have WordPress 100% translated before a language pack is built has been updated. From today on the new requirements are as follows:
Related handbook pages have been updated accordingly (one, two, three).
This should give teams with less contributors a better chance to get WordPress released into their localeLocaleLocale = 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/ to hopefully attract new contributors to join the team to help finishing the translations of WordPress core and other projects.
WordPress 5.6, planned for December 8, 2020, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins.! The deadline for the final stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. is set to November 17th.
Some of the new strings are related to updates to the blockBlockBlock 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. Thus existing translations from the GutenbergGutenbergThe 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. So far there are only 236 new strings and 47 strings have been fuzzied.
WordPress 5.5, planned for August 11, 2020, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins.!
The stringsStringA 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 GutenbergGutenbergThe 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-updatesfeature pluginFeature PluginA 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.
The translatable stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. of WordPress coreCoreCore 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 stringStringA 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:
I’ve drafted a handbook page called “Translation EditorTranslation EditorTranslation 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 & LocaleLocaleLocale = 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 EditorA 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 EditorA 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.
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.
“(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.
“(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 SlackSlackSlack 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.
“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.
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 localeLocaleLocale = 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 PackagesAutomated release packages are release packages of locales that have no custom changes..
As of today all localesLocaleLocale = 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
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 RepositoryThe 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 coreCoreCore 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 PluginPluginA 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 packageA 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.
After a small cleanup of unused localesLocaleLocale = 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 localeLocaleLocale = 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.orgThe 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 filterFilterFilters 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..
The filters have been extended to allow limiting the term search by scope. For example search only in originals or only in references.
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” stringStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. in the blockBlockBlock 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.
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 HTMLHTMLHTML 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.
WordPress 5.4, planned for March 31, 2020, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins.!
The stringsStringA 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 stringStringA 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 freezeThe 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 good starting point is the Fuzzy view since many strings have been changed to use sentence case. This may not apply to your localeLocaleLocale = 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.
WordPress 5.3, planned for November 12, 2019, is now ready to be translated on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins.!
The stringsStringA 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 stringStringA 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 freezeThe 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 blockBlockBlock 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 (GutenbergGutenbergThe 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.
Since the last update, the docs team decided to turn on the HelpHub feature on Japanese & Serbian RosettaRosettaThe 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
MetaMetaMeta 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.
LocaleLocaleLocale = 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 sidebarSidebarA 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)