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!
When translating plugins or themes, it can be hard to know the context in which the stringStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. appears. In GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., we’ve got the table view for translations where there is very little context. Sometimes you can use the “References” to find the right line in code and try to guess context from code.
Our work on Local GlotPress, as announced in February, is an attempt to bring GlotPress translation to your local blog by making use of the currently installed plugins or themes. You can load their translations into the Local GlotPress, make changes, and deployDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. the translations back into WordPress to see them right away.
Additionally, Local GlotPress features inline translation: when viewing the interface with the (partially) translated stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings., the strings can be translated in-place. Colors indicate the availablility of inline translation for the particular text.
Now, combining Local GlotPress with the WordPress Playground (see also the lately announced Tech Demos on the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.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/. and this overview post at web.dev) allows you to make use of the above without having to set up anything.
Making Quick In-Context Translation Possible
Since WordPress Playground a kind of a virtual machine running WordPress, just in your browser, we can use it together with Local GlotPress to make translation any 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 or theme much easier:
You open the Playground via the link on the top right, and it will load a WordPress with that plugin activated, plus Local GlotPress. You can then navigate to the plugin’s screens and add your translations.
Remember that this is a sandbox! If you reload the page, all your translations will be gone. So make sure to “Contribute back,” i.e. submit the translations to translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins..
Should things fail, you can also download a PO file of your translations from that screen and then try to import it manually.
Afterwards, you can confirm your submission by opening the playground again. As it will take the most current (and waiting) translations from translate.wordpress.org, your new translations should be displayed.
The above is just an example link, it is enabled for any other plugin/theme and language. Some work better than others, and larger plugins with many translations tend to load slower but usually it should only take a few seconds to load.
Booting up WordPress
In-context translation (right click the colored text)
Translation is displayed in place after adding it
Submit back to translate.wordpress.org
We think that the WP Translation Playground is a new and exciting way to translate plugins and themes but also to verify that translations work well in context. It also allows you translate the most important strings first: the ones that you see.
There is certainly still room for improvement and iteration (there are a number of pending pull requests) and we’re curious for your opinions and experiences. Please give us feedback in the comments!
Thank you @amieiro and @spiraltee for reviewing this draft and your collaboration on this feature, and @zieladam for creating the WP Playground!