It would be great if we could edit…

Welcome to the official blog of the translator team for the WordPress open sourceOpen Source Open 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.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/ account and suggesting translations (more details).

Want to help in managing and validating translations? Get in touch with the existing language team and follow the glossaries & style guides if the team has them.

Don’t see your language? You can request support for it.

Weekly Meetings

We have meetings every week on SlackSlack Slack 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 sidebarSidebar 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. 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.

#polyglots

It would be great if we could edit the readme.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. from within rosettaRosetta 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. possibly with a short code that auto inserts the version and the wp-config-sample.php from stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. and have the compiler script automatically pull them and make those files. It would allow more rapid push out of new releases/updates without the need for tagging the new version in SVNSVN Apache 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/.. In theory, if the version number gets auto filled in the readme.html with this method, it would also allow the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. admins to push all the translations too for a security release if there are no changed strings.

#suggestion

Andrew Nacin 5:34 am on October 3, 2013

Definitely something we’ve talked about before. There are a number of potential issues. A lot of installs have their own readme.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. file, with the actual filename translated as well. Thus it would ship next to the American English readme.html. We could encourage this for all languages, but then we’d have a conflict for non-American English translations. Or we could discourage this, thus readme.html would always reflect the local language. But when you start dealing with updates, versus just a standard download package, things get a bit messy.

When using an American English install, WordPress currently downloads only changed files when updating to a minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.. Since we know which files changed and we know that no stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changed, it’s entirely fine to do so. We’re nearing the point of “language packs” that would update po and mo filesMO 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/ separately. Unfortunately, this readme.html file remains a thorn, especially with the version number. It’s not a big deal if the translated readme says “3.5” but the actual install is 3.5.1. But, if a translator is simply replacing readme.html, then we’re going to stomp on their changes. Now, I don’t necessarily mind this as users aren’t relying on their readme once they are installed (or at all — it’s a bit of an anachronism). It’s also no different from when a user opts to update to WordPress in English before a zip is ready.

Oh, and some include a translation of the license file, too.

I think we’re at the point where, at the very least, RosettaRosetta 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. can replace a placeholder for you inside readme.html. Then you could just always take the trunk or branch dist files which will have nothing more than a readme.html and wp-config-sample.php. Over time I’m very happy to see newer tools here.

Translate WordPress

Weekly Meetings

Posting here

Share this: