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 locale 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 packages Automated release packages are release packages of locales that have no custom changes..
As of today all locales 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 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 core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
- If you have made changes like a translated
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 Plugin 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 package A 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.
Last month, @lidialab and I posted a plan for the Polyglots Handbook reorganization. We set June 30th as our deadline (which may have been too ambitious to finish everything!) but we have made excellent progress so far.
Now that it is the end of June, we would like to share an update on our progress and next steps.
Currently, we have edited, written, and reviewed 47% of the Handbook pages. All of these pages are in the shared Polyglots Handbook folder. Our plan is to make all of these changes live once we have reviewed everything. Then, we will reorder the Handbook itself, as we want to be careful to not break any permalinks in this process.
For the next steps, we still need volunteers! If you can help:
- Please sign up for a page to edit, write, or review in our spreadsheet. Create the page as a new document in the Polyglots Handbook folder, add your changes as Suggestions, and, once you have finished, add the date to the spreadsheet.
- We also need volunteers to review pages that were edited. In the spreadsheet, please check the column Needs review to find pages that need a second review.
If you’re unsure of the best way to contribute, please ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me (@erica) or Lidia (@lidia) in Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. and we will be happy to help.
We aim to continue editing these pages over the next month and will post another summary at the end of July to explain our progress and the next steps.
Big thanks also to @nao, @casiepa, @psmits1567, and @devinmaeztri for helping get us to 47%!
Please activate the handbook plugin 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 on fr.wordpress.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/
Docs Team: @kenshino, @atachibana, @milana_cap, @cristianozanca
Polyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/.: @nao (note taker), Matteo S.
Meta 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: @sergeybiryukov
Community Team: @_dorsvenabili
MultilingualPress: @nullbyte, @dinamiko
Community Team: Handbook Translation
- The Spanish team has been manually translating it and put it on their Rosetta 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
- @_dorsvenabili said the community team was looking into focusing on handbook i18n Internationalization (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. dev in the near feature
We agreed on identifying common key requirements so that a general solution can be created for both the Community and Docs team’s handbooks
In short, after a lengthy discussion, we realized that the key requirement was really to have a place that local teams could write into the Rosetta site. Everything else could be decided on and improved upon later.
We therefore discussed various technical possibilities.
GlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. vs Custom 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. (CPT)
- A large number of translation contributors are already familiar with it
- Translation review (validation) flow and role system is established
- Glossaries & fuzzy detection work well
- Need to somehow push WordPress content into files (possibly)
- The text in the source file needs to be wrapped around l10n functions
- Not really meant for long-form text
- Does not allow for new content to be created (relies on a base English version)
- Relatively easy to build an MVP "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 then test & extend
- MultilingualPress (if used) can offer ways to connect sites, send notifications, and add hooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.
- Since it’s WP based, should be easy for translators to learn
- Allows local teams to create new localized contents rather than translated docs
- No detailed (e.g. per paragraph) validation flow like GlotPress
- Additional roles may have to be defined
- Users need to be added to Rosetta sites, possibly causing a bottleneck/gatekeeper situation
MVP for the CPT solution
Write up the necessary custom post types on one Rosetta site so that the locale 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/ team can create a copy of English pages and translate (see details on this post under “Phase 1”).
- Notification for original text changes
- Diff between the original and the starting point of the translation
- Ways to distinguish obsolete contents
- A content approval workflow to ensure the correctness of content
- And more to be discussed
+make.wordpress.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//docs +make.wordpress.org/community
Locale 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/ stats
Releases: 162 locales 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/. 60 locales up to date. 1 locale behind by minor versions. 15 locales behind by one major version.16 locales behind more than one major version. 61 locales have a site but never released. 9 locales don᾿t have a site.
Next short term goal is getting to 75 locales up to date before 4.6
All 15 locales behind one major version are 85% + translated with the exception of Latvian.
Translations: 162 locales. 59 locales at 100%. 4 locales have more than 95%. 6 locales have more than 90%. 22 locales have more than 50%. 61 locales have less than 50%. 10 locales don᾿t have a WP project.
Locales translated more than 95%
We started filling out data about locale status during the releases to get a history of how things progressed as far back as we can. To give a hand with filling out the data, please ask for access to the spreadsheet.
https://wordpress.slack.com/archives/polyglots/p1461754491001295 was enabled and works pretty good.
||Dominik Schilling ocean90
Coming later this day: When a plugin 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 releases a new version all translations will be copied from dev to stable.
Handbook task list
- Add a page about how WordPress ships translations based on Nikolay & John’s video from GWTD
Let’s create a list of questions to add to the FAQ section of the handbook:
- Add a Frequently asked questions page and include
- How often are translations deployed Launching code from a local development environment to the production web server, so that it's available to visitors. for plugins (every six hours?)
- How long does it take for new translations to get to users? (translations get pushed every 24 hours?)
- How do translations for Rosetta 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. sites appear on the site? (Automatically pushed every 24 hours, at 1pm UTC)
- Why are my translations still ‘waiting’?
- Why my translations were rejected? What can I do in that case?
- I have translations in po/mo files MO, or Machine Object is a binary data file that contains object data referenced by a program. It is typically used to translate program code, and may be loaded or imported into the GNU gettext program. This is the format used in a WordPress install. These files are normally located inside .../wp-content/languages/, how can I import them in translate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.?
- How long does it take for a new plugin/theme to get added to translate.wordpress.org?
- Why can’t I be a GTE 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. for all languages for my plugin/theme?
- I’m getting a lot of “502 Bad Gateway”. What can I do?
- Other FAQs? Add them in the comments
- Support Team mentioned that Codex will be retired and translations will get lost. We need to collect more information here.
- Organizing WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe, there is a chance @petya won’t be around at the weekly meetings for the next weeks. It is important to keep the meetings going. @chantalc, @deconf, @wolly, @tacoverdo, @pixolin and @coachbirgit will take care of organizing the meetings.
Thank you to everyone who participated! Please leave comments if you have anything else to add to the notes.
We have a Glossary section of the handbook: https://make.wordpress.org/polyglots/handbook/glossary/
I need your help with gathering all the terms we need to explain in the glossary, so here goes:
- Experienced contributors, please add the terms you’re missing in a comment of this post
- New contributors, please add any term you’re not familiar with you come across – again in a comment here.
To clear up some confusion around the revision number used for building a local package, I updated this Translation Handbook page: Packaging Localized WordPress
I appreciate it you could read through the process and let me know what needs to be changed/added. Thanks!
Hello again polyglots!
One of things discussed at the chat a few weeks ago was the handbook for your team. Contributor handbooks are a great way to cover all the basic and even advanced parts of what your team does. (Check out the handbooks from the core and mobile teams for great examples.)
The polyglots contributor handbook was started by @nbachiyski and has been worked on by @nao as well. They’ve both done a great job so far!
I’d like to continue their work and get a full handbook published, with detailed pages just like the handbooks linked above.
Why is this important? A lot of questions come in to make/polyglots that could easily be answered if they were documented well. In fact, a lot of the answers are documented well already, but are scattered throughout this site and others. Let’s combine them and clean up everything so it’s incredibly easy for anyone to start a new translation of WordPress or pick up where someone else left off.
One of the most important parts of a good, consistent handbook is a good editor. @nao has agreed to act as editor!
I’ll be helping @nao bring content over from other places and put them in a new handbook. The current handbook and other pages will be merged into this handbook and updated as needed.
But @nao and I can’t do it alone! We need volunteers to help write new new pages. Are you interested in contributing in any way to the handbook? Leave a comment here with your level of interest so we can get to work making the handbook awesome. Thanks!
Hi Zé, I’ve talked to siobhan and I volunteered to be in charge of the Polyglots Handbook. But I need access to the dashbord to edit the page. Could you please do that for me? Thanks
On our last meeting a week ago (https://irclogs.wordpress.org/chanlog.php?channel=wordpress-polyglots&day=2013-02-12&sort=asc) I promised Siobhan from the Docs team to find someone to own the Polyglots Handbook. However, the person I had in mind can”t help us right now. So, this is a call for volunteers. Someone needs to assume this task and it would be better if this person knew the process of starting a new locale.wordpress.org site, setting up locale forum, the translation process itself and building the packages. Anyone, please?
I’m working on a new draft Translator’s Handbook, on light of the most asked questions here. The final purpose is to merge that with the current one, to have a complete and thorough overview of the translation process of WordPress. I’d love to have feedback. What is missing? Is something not clear? Is there too much information anywhere? All comments welcome, thanks in advance.
I’m editing Translator’s Handbook. Posting it here. I hope this will help new comers and anyone who want to start translating WordPress.
Any experienced person’s suggestion is welcome. Actually I also am a beginner at WordPress translation. So some information may be wrong. So need correction or suggestion.
I added a little bit of text on the handbook documentation:
I’m planning on adding some more under “Local sites” section later.
As mentioned before, can we have a page for a viewer and eventually link this page from the sidebar 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. or Resource page?
I created a new page
with a tag policy on how to tag your posts… check it out!