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!
To release your translations manually, you need to manually create a release package from your local WordPress site (http://locale.wordpress.org). Locale Managers have access to do that.
Before you package and build your localized version of WordPress, you should make sure everything is ready.
Check in all updated files into the current branch directory via 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/. under i18n.svn.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// (Access to SVN may need to be requested via make.wordpress.org/polyglots; it’s handled separately and not automatically connected to the roles “Locale Manager” or “General Translation EditorGeneral 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.”).
The 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. consists of four different sub-projects that all need to be translated to 100%: WordPress, Countries & Cities, Administration, and Network Admin. Make sure all the stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. are translated.
In your SVN directory, copy the current branch directory and create a new tag directory under locale/tags/X.X.X
Once you have the revision number of the version you’ll be packaging, it’s time to build the actual package. To do that, follow these steps:
Log in as a General Translation Editor to your local WordPress site (locale.wordpress.org)
Go to “Tools → Release Packages”.
Scroll down to “Build New Package” section.
For “Where should we get your translations from”, select “translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins.” if you want to use those current translations. If you’ve checked in translated message files in svn, select “SubversionSVNApache 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/.”.
After building a new package, you can share the download URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org among your translation team for testing. You can find the URLs under the “Links” column on the Translations for page, in .zip or .tar.gz format.
If testing goes well and you’re ready to release the final version to the public, simply click the version’s “Release” link under the “Action” column. This will mark the official release of that version. Users will be prompted for an upgrade of their language package on their dashboard, and download information on your locale site will be updated.
RevisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. numbers must be taken from build.trac.wordpress.org.