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

Woongeluk 11:45 am on May 23, 2019
Tags: request ( 1,460 )

In the midst of building…

In the midst of building a new site (wp and woo-plus-plugins) we realised we ONLY need a translation for the frontend/clientside. English backend-translations we could easily do without. It would also save a host of work, because now front and backend translations are intermixed. Could the WP crew consider splitting them up? It would be greatly appreciated and it would save an enormous number of stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. running in the background.

#request

Besnik 12:19 pm on May 23, 2019

Someone from the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team can answer this request better, but I think even if they answer positively, implementing what you’re asking would not make it at the top of priorities list: we’re talking about over 3500 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings., without counting those from Continents & Cities and Administration sections. Finding which ones qualifies for your request and separating them would be to much work with little gain for the larger WordPress community.

Regards,
Besnik
- Sergey Biryukov 8:25 pm on May 23, 2019
  
  FWIW, WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. has separated front end and back end translations 7 years ago: https://core.trac.wordpress.org/ticket/19852
  
  However, doing the same for plugins and themes doesn’t seem feasible, as there is generally no way to know which stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are only used on front end.
Tor-Bjorn Fjellner 4:09 pm on May 23, 2019

Which language are we talking about?
The systems that handle translations of WordPress are configured to create language packs for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. only when 100% of the stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are ready.

For projects in WordPress directories of free plugins and themes, language packs are generated when at least 95% of the strings are ready. (Readme files for Plugins are not included in this, they are handled stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. by string.)

Currently, there is no distinction in the translation interface between strings that are visible on the front end or not.

But: You can get a “cleaner” back end if you for each user in their profile choose “English US” as their language for the admin pages.
Further: If you handle translations locally, then with tools like poedit and/or plugins like locotranslate, Say-what you can translate what you need, specifically.

On translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. you can navigate to the relevant project and download even all waiting strings as a po-file and further handle it with poedit and upload the translation via FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients. to the web server.
Note that on the server, .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/ are used.
Human 6:43 pm on May 23, 2019

We are taling about Dutch Tor, and also about themes. Lately we bumped into two excellent theme’s where the backend stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. were written not very translatable, bacause of the quality of the english. What is served through po-edit is way too often ‘off’, because many strings from their servers (and microsoft) don’t take grammar into account and also sprinkle lots of words into them which are not to be translated or give several different translations for the same meaning without any logic. We found it not to be as good as it seems to be. All kinds of code which is in strings is also garbled or ‘overspaced’ or even ruined completely, so you have to check every one of the 2500,450, 75, 2388, etc. where we would only really need less than 150. Plus hours of wasted time in debugging the gremlins you overlooked in that other pluginPlugin 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’s other translation, which has several locations on the server because of some migratinal rule from years back. Woocommerce is a bitch in that aspect.
Translation has now been coded as a bulkprocess, where there are two separate things going on: front and backside, which really are two different worlds to clients and users. It might be a rethink, but as users we would be very much helped by a more non-tech userfriendlyness. WordPress has become (sorry to say) a quagmire of plugins and especially themes with way too much interloping options where the backend too often does not give sufficient clues to what the checkbox really does all over the site. And CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. should be impeached, now.
- Tor-Bjorn Fjellner 9:25 am on May 24, 2019
  
  @b11n
  In general, I’d say that CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is quite well-behaved. StringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. for translation are split up in meaningful chunks and with good explanations/comments where needed. As Sergey noted above, the strings in core are already split between front and admin. The translation of core for #nl_NL is well maintained.
  
  However the i18nInternationalization 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. (internationalizationInternationalization 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.) of various themes and plugins are varying a lot.
  I usually try to notify the developers when I find constructions that are hard to translate, for instance when several separate strings are “glued” together to form a sentence. But new developers are sharing their work all the time, and many of them need to understand these issues before they can do it right.
  You might find it useful to look for plugins and themes that are already translated:
  See https://translate.wordpress.org/locale/nl/default/stats/plugins/
  and https://translate.wordpress.org/locale/nl/default/stats/themes/
Human 12:08 pm on May 25, 2019

Tx. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is quite ok indeed. I understand your ideas about translated themes, but most of them we think are not suited towards the design-agency-with-a-new-twist we are building at woongeluk.nl. My point is exactly about the standard option which should be built in, to split translations into customer-side and backend. It should be a standard which could be implemented into each of the myriad themes which are being developed. By default when running the .pots. It would save many siteowners a host of time translating only those stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. they absolutely need for their multilang websites. A lean solution, instead of a solution including the kitchensink (like topheavy wpml). Yust our 5 cents.

Translate WordPress

Weekly Meetings

Posting here

Share this: