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!
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!
Please make sure 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/ is always eligible for automated release packagesAutomated Release PackagesAutomated release packages are release packages of locales that have no custom changes..
A 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.is a ZIP file consisting of WordPress in its entirety, along with translation files for coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., the default themes and Akismet, and any custom changes you may have.
If you have never had any custom changes and i18n.svn.wordpress.org is entirely empty for your locale or doesn’t exist, you do not need to do anything. Your release package will be created automatically for you. An example locale is en_GB.
If you have no custom changes for the current stable version (like 5.4), please ensure you have an empty branches/5.4 directory at i18n.svn.wordpress.org. Your release package will be created automatically for you.
If you have minor custom changes for the current stable version (like 5.4), consisting of, at most, a translated readme, license file, and wp-config-sample.php, please ensure these files exist in a branches/5.4/dist directory at i18n.svn.wordpress.org. Your release package will be created automatically for you.
If you have extensive custom changes consisting of other files, such as wp-content/languages/$locale.php or core modifications, you will need to create a package via 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..
For this, we are phasing out the ability to ship any customizations beyond license, readme, and wp-config-sample.php. This means you need to reach out to the WordPress core contributorsCore ContributorsCore contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. to fold your modifications into the WordPress core. You can start this process by creating a Trac ticket.
Release packages and language packs for stable versions are usually built every hour on the hour after the “Development” sub project is at least 90% AND the “Administration” sub project is at least 75%.
A new build will be created only if a translation was changed after the latest build. Rejecting and approving one translation within the WordPress project on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins. is all that is needed.
No worries. First, create your SVNSVNApache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. branches. Since a language pack was probably already built, you have to update one translation (see the question above). Your package will be created during the next build window (see above).