Developer take care of the…

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

Developer take care of the translators!

Yes, I am a developer and translator and I see a bad behaviour that it is easy to fix and can help the translation of your 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 from the community.

First rule: No automatic translation! As I already said on the last WP Translation Day the English language is not very good for translation and it is easy to spot when they are automatic. The communities have a glossary and rules that the automatic translator doesn’t follow. So the PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. has to check every stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. that usually is rejected and that time could be used to approve beautiful translations.

Second Rule: Why put your name as developer and links of your website or of the plugin site under the __(),_e() etc? GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. detect them and ask to translator to translate! It’s useless!

Do you have any other rules for the developers that need to be followed to improve the life of a translator?

Pascal Casier 2:16 pm on January 24, 2017

Hi Daniele,

Something extra: Please give comments.
We are not into your code, so help the translators and give an explanation on the line just above:

/* translators: Timeout is if payment failed or user did not complete the process */
__( ‘Timeout’, ‘my-text-domain’ );
- Tor-Björn Fjellner 8:18 am on January 26, 2017
  Note that there are actually two ways to handle this:
  When there are some placeables, the best approach is use a comment on the line immediately before line where the stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. occurs, like Pascal just showed.
  But: for stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. of just one-two words, that may not be clear directly, or where their use may not be directly understood, it may be better to use the context approach. This tells the translator how the translated string is going to be used, and makes sure that the translation won’t be automatically used in a different place, there the string happens to look exactly the same, but might have a different meaning.
```
$translated_text1 = _x( 'Help', 'Verb. Used on button', 'my-text-domain' );
_ex( 'Help', 'Noun. Used in top-level menu', 'my-text-domain' );
```
Tor-Björn Fjellner 12:16 am on January 26, 2017

There’s more:
Don’t build concatenated stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings.. In some languages you may translate different parts of a stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. separately and then combine it together to a full phrase. But for many languages that’s an impossible task.
(Russian example: Edit – Редактировать, page – страница, but Edit page – Редактировать страницу)

Make sure that you handle plurals correctly. Whenever you have phrase where you report a variable number of something, then you SHALL use the functions for plurals.
Because: Different languages handles plurals in different ways. And with the correct 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. you make it possible to make it right. Did you know, that Russian uses singular not only for 1, but also for 21, 31, 41…
(But, if something talks about, say, 48 hours, and you know that you aren’t really going to change this parameter, then you give that just as an ordinary phrase “The process takes up to 48 hours.” No need to overdo the plural complexity here.)

When you have more than one plaeable in a string, make sure to use ordering parameters (%1$s, rather than %s). This makes it possible for the translator to build a phrase that feels logical in the target language.
Tor-Björn Fjellner 4:54 pm on January 26, 2017
One more thing:
Avoid overly long stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings.. If you put 4-5 sentences or more in one single stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings., then it becomes a bit heavy for translation.
- There’s a bigger risk that the translator misses some details that might be important.
- In case you change anything the translation has to be done again. Really small changes usually create so called fuzzy matches. But for a fuzyy match, the editor has to figure out what has changed and whether anything needs to be changed in the translation, (for instance httpHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. -> httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. or the best -> one of the best). The longer the string, the more job to figure this out.

Translate WordPress

Weekly Meetings

Posting here

Share this: