Translate WordPress

Keyboard Shortcuts | Hide comment threads

WordPress 5.3 ready to be translated

WordPress 5.3, planned for November 12, 2019, is now ready to be translated on translate.wordpress.org!

The strings are in the development projects. The strings for WordPress 5.2 have been moved to projects/wp/5.2.x.

So far there are around 380 string changes. The about page has not been updated yet. Soft string freeze is announced for next week, October 7th.

Most of the new strings are related to an update of the block editor (Gutenberg). Existing translations have been migrated to the WordPress project.

WordPress 5.3 will also bundle a new default theme, called Twenty Twenty. Active development still happens on GitHub.
Twenty Twenty can be translated in the projects/wp-themes/twentytwenty project.

Happy translating! 🌏🌍🌎

#announcement #5-3

Guten Tag. Könnten Sie die…

Guten Tag. Könnten Sie die Übersetzung meines Plugins auf Deutsch http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/en/formal/wp-plugins/carousel-upsells-and-related-product-for-woocommerce/ überprüfen? Ich bitte Sie auch, der Person, die das Plugin übersetzt hat, oder mir als Autor des Plugins PTE-Rechte einzuräumen

#editor-requests

Cross Locale PTE Request for A+ Booking System – A+ booking calendar

Hello Polyglots, I have suggested strings for this A+ Booking System – A+ booking calendar and would like to become a Cross Locale PTE, can you please add me:

Name: A+ Booking System – A+ booking calendar
URL: http://wayback.fauppsala.se:80/wayback/20191101081404/https://wordpress.org/plugins/a-booking-system/

I speak romanian language very well because I am romanian.
For the other languages ​​I’ve applied for, I hired an authorized translator.

Thanks.

#editor-requests

Perhaps a better role to apply for would be a Cross Locale PTE, you can read more about how it works, and what you need to do in that case. http://wayback.fauppsala.se:80/wayback/20191101081404/https://make.wordpress.org/polyglots/handbook/rosetta/roles-and-capabilities/#cross-locale-project-translation-editor

Hi Tor-Bjorn Fjellner,

I’ve changed the request into “Cross Locale PTE”. ( like you said)

Thanks

@abookingsystem
Asking for CL PTE is not just a matter of changing a word in your request. Please read carefully the link I gave.
You’re supposed to use a separate account and in the profile of that account provide good channels for translation feedback.
Also: You need to show us that you’re using professional translations that are made in observance of glossaries and style guides of the various locales (see http://wayback.fauppsala.se:80/wayback/20191101081404/https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/list-of-glossaries-per-locale/ )

Since you want to go for CL-PTE, I’ll close this request.

¡Hola @abookingsystem!

Thanks for contributing to the es_ES translation! You can take a look at this page where there is more info on how we handle PTE requests and why we don’t grant PTE authority by default.

You can get in touch with us joining the #traductores-plugins channel in the Spanish Community Slack. Also remember to take a look at our Guía de traductores where we describe the best practices and recommendations for creating a perfect localization for plugins and themes.

¡Gracias!

¡Hola @abookingsystem!
Thanks for contributing to the es_ES translation! You can take a look at this page where there is more info on how we handle PTE requests and why we don’t grant PTE authority by default.

Also please note that your plugin cannot be translated yet because is not properly prepared for localization:
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/projects/wp-plugins/a-booking-system/

You should get that sorted before applying for PTE or CLPTE again.

You can get in touch with us joining the #traductores-plugins channel in the Spanish Community Slack. Also remember to take a look at our Guía de traductores where we describe the best practices and recommendations for creating a perfect localization for plugins and themes.
¡Gracias!

If you look at http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/projects/wp-plugins/a-booking-system/ you’ll see that your plugin still isn’t correctly prepared for translation.

In the plugins headers, you need to specify the text-domain, and it should be identical with your plugin slug `a-booking-system`
You also need to indicate the same text-domain string every time you call a translation function.

Hi Tor-Bjorn Fjellner.

I want to translate first the description file readme.txt file.
The other texts are already translated but are stored in a global variable.

Thanks

Plugin not prepared for localization.
No strings submitted.
#ru_RU

Hi Yui.

I want to translate first the description file readme.txt file.
The other texts are already translated but are stored in a global variable.

Thanks

Same for French Team

Hi fxbenard.

I want to translate first the description file, readme.txt file.
The other texts are already translated but are stored in a global variable.

Thanks

Hello Polyglots,

I would like to join the Español Mexico team. Can you please make me a GTE? I am a PTE but would like to translate other plugins. I’m active all through the week.

Many thanks.
Here is the link to the Plugin I am working on currently. — http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/projects/wp-plugins/church-admin/

#editor-requests

Let me know if there’s anything I should do beforehand.

Hello.

Here are some new plugins string to be reviewed in es-mx Most of them are just 1 or 2 strings long and could be ready for 100%, there are a couple of larger ones, @tokyobiyori @hiwhatsup @mushmellow @marcozink

http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/yikes-inc-easy-mailchimp-extender/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/wp-profile-picture/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/eh-mortgage-calculator/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/woo-banorte/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/kantoniak-about-me/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/car-demon/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/simple-move-javascript-to-footer/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/select-primary-category/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/limit-image-sizes/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/imoneza/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/copyright-info-for-child-theme/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/dynamic-slider/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/link-control-commando/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/doboz-for-woocommerce/
http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/es-mx/default/wp-plugins/pay-in-store-woocommerce-payment-gateway/

#editor-requests

Hello, thanks so much for your contributions 🙂 I’ll take some time to go through all of these, but on a quick glance I can see there are several discrepancies in the voice (some strings using “usted” and others using “tu”), so please check them when you have time. I’ll go approving them little by little so your patience is greatly appreciated.

Hi.
I saw what you mean, I have rejected some of the strings with discrepancies myself, those were my first attempts to correct fuzzy strings and I must have made a mistake somewhere in the process.

WP polyglots facilitator

I am Jesús Amieiro, one of the GTE of the Galician language. The Galician language is spoken by some 2.4 million people, mainly in Galicia, an autonomous community located in northwestern Spain, where it is official along with Spanish.

The Galician people are bilingual in both languages, so we can take advantage of this to translate WordPress and its environment (plugins, themes, …) from Spanish to Galician and not from English to Galician (the Spanish translation community is the most important worldwide and usually has translated the entire top 200 plugins and themes). In this way we avoid having to interpret each translation string, and we only have to translate from one language to another (both languages are very similar, both are Iberian Romance languages).

To automate this work I have developed a tool, WP polyglots facilitator, which allows you to generate a .po file with the strings pending translation (in a plugin or theme) of a language with the pre-translated strings of another language. The source code is available at this link.

I think that this tool can also be very useful for cases in which there is a variation in the language, as are the cases of Spanish, which has variants in Spain, Peru, Argentina, Mexico, … or English, which also has variants in Canada, UK, Australia,…

I published this tool on September 22, 2019, in WordCamp Pontevedra, and in the Galician translation community (with 4 active translators, 109 translators) we have gone from having 28 plugins translated 100% in the top 200 to 95, only behind the Spanish community (207 plugins – 3202 translators) so I think it is a tool that facilitates a lot of work with a good quality of results.

I would love to hear what you think of the tool and suggest me improvements.

I can only say that I had the opportunity to test this tool in its beginnings, when it only worked with plugins, and it’s fantastic!
Now the tool is able to work with themes as well (and I’m sure that in the future it will work with much more).
It is the perfect tool for those language variations that are starting translations, as it saves them an enormous amount of time, because translators only have to adapt the translations already done to their language peculiarities.
In my opinion, in such cases, it is an indispensable tool.
And, of course, thanks to Jesús for creating it… Well done! 😉

Thank you @nobnob
Very good explanation of the usefulness of the web tool

I believe that it is definitely a great tool, but still it seems that the GlotPress “Other Languages” section already does something like that. It allows you to see the translation in different languages, and you can translate from this point. Is there something that I can’t see that makes a huge difference?

Anyway, it is nice to know that has improved the local performance (that is what really matters). Congratulations!

Hello Felipe

Thank you for your comment. GlotPress has a similar functionality, but when you are translating a string it shows you the translations from several languages, many of them unintelligible to you.

My web tool tries to focus on getting the translation of a language very similar to the one you want to translate the string, so the work is much faster using an external tool like Poedit or a text editor than if you do it with GlotPress.

In very similar languages, such as Spanish and Galician, when you translate 200 strings, in a high percentage you don’t have to do anything, since the string is the same. The same happens for variations of the same language, where the changes are minimal (think, for example, in Portuguese of Portugal and Portuguese of Brazil). The same is true for variants of Spanish, English, French,…

This web tool allows us the translators of the Galician community (we are 4 active translators out of a total of 109 translators) to advance very quickly in our work with a good quality of the final product.

Agenda: Weekly Polyglots Chat – October 30, 2019 (12 GMT)

Here’s the agenda for our weekly chat.

This meeting will be held at Wednesday, October 30, 2019 at 12:00 PM UTC in the #polyglots channel in the “Making WordPress” Slack.

  • Weekly locale stats
  • WordPress 5.3:
  • Meeting times reminder
    • We now alternate meeting times every week between (06:00 and 12:00 UTC/GMT). Keep in mind that the meeting times are tied to GMT/UTC – if your location is using DST (daylight saving time), then the meeting time in your local time may move accordingly.
    • On Wednesday November 6 at 21:30 GMT (time corrected, was half an hour off), we’ll have our first monthly chat on “Americas friendly time”. It will repeat the first Wednesday every month.
  • HelpHub i18n
    • In addition to Japanese and Serbian, other locales (Russian, Brazilian Portuguese, and Dutch) started testing. See this Docs Handbook for more info & instruction.
    • @netweb is working on contents import
  • Reminder: give some thoughts on the “measuring polyglots team success” post.
  • Achievements & Open Floor

Leave a comment if you’d like to add something else to the agenda.

#weekly-meeting-agenda, #weekly-meetings

Here are the weekly stats:
Below stats are dated 2019-10-30 compared to 2019-10-23 (differences between brackets)

*Releases*: 203 (±0) locale, 51 (+3) up to date, 8 (-3) behind by minor versions, 5 (±0) behind by one major version, 54 (±0) behind more than one major version, 77 (±0) have site but never released, 8 (±0) have no site.
*Translations*: 203 (±0) total, 20 (+10) at 100%, 30 (-6) over 95%, 21 (-3) over 90%, 37 (-1) over 50%, 83 (±0) below 50%, 118 (±0) have a language pack generated, 12 (±0) have no project.

*Requests*: There are 35 unresolved editor requests out of 2 834 (+14) total and 10 unresolved locale requests out of 116 (+1) total.

*Translators*: There are 639 (+2) GTE, 3 472 (+36) PTE and 36 481 (+161) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

*Site language*: 53,986% (+0,106%) of WordPress sites are running a translated WordPress site.

#editor-requests Hi Polyglots, I have…

#editor-requests
Hi Polyglots, I have suggested strings for Wp Whydonate plugin and would like to become a PTE, can you please add me:

Name: Wp Whydonate
URL: http://wayback.fauppsala.se:80/wayback/20191101081404/https://wordpress.org/plugins/wp-whydonate/

Please let me know if you have any questions. Thanks for your help!

Kind regards,

Niels

Via http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/projects/wp-plugins/wp-whydonate/ I could see that the only locale with suggested strings for this plugin is #nl_NL so I’ve added that tag in the request. (And include it here to have a notification sent to the team.)

Hi Tor-Bjorn,

Thanks for your reply. I am quite new to how this works. I just tried to approve the nl_NL strings we added to the plugin. But I’m still not allowed to do so. Any idea what I’m doing wrong?

We are working with Spanish (ES) and German (DE) translators as well. Could you also allow me to approve those?

Thanks for your help!

Kind regards,

Niels

This here is just a multi-author blog with some nice formatting and check boxes, but there are just for plain manual follow-up.
When we tag a locale, like #nl_NL then the global translation editors of that locale will be able to get notified about it, if they’ve added their locale tag as a watched word in http://wayback.fauppsala.se:80/wayback/20191101081404/https://profiles.wordpress.org/me/profile/notifications/ (You can also use this to find out when someone mentions things that are important to you. )
They can also find still unresolved posts where their locale tag is mentioned using a link like http://wayback.fauppsala.se:80/wayback/20191101081404/https://make.wordpress.org/polyglots/tag/nl_NL/?resolved=unresolved
So when you ticked that box (which I reverted for you), you basically indicated that your request for said locale has been sorted already…

Once someone from the relevant language team gets around to it, they’ll leave a comment with feedback under this post.

You may speed up things by having the person who is actually doing the translation joining the relevant local Slack team. The ones we know about are listed in http://wayback.fauppsala.se:80/wayback/20191101081404/https://make.wordpress.org/polyglots/handbook/about/teams/local-slacks/ .

As a matter of fact, both #es_ES and #de_DE really want the translator to join their Slack team before they approve a request for PTE. If you post a similar request for their locales, they’ll come back with specifically a request to submit some translations and join their local chat for feedback. That’s very understandable to me: We’re all volunteering our time here. And for a GTE it’s more efficient to help translators become better and becoming translation editors, than time after time checking/fixing “anonymous” translations where your comments will never reach the translator.

PTE Request for Sensei LMS

Hello Polyglots, I have suggested strings for this Sensei LMS and would like to become a PTE, can you please add me:

Name: Sensei LMS
URL: http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/projects/wp-plugins/sensei-lms/

If you have any questions, just comment here. Thank you!

#editor-requests

PTE Request for Gutenberg

Hello Polyglots, I have suggested strings for this Gutenberg and would like to become a PTE, can you please add me:

Name: Gutenberg
URL: http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/projects/wp-plugins/gutenberg/

If you have any questions, just comment here. Thank you!

#editor-requests

I began translating dokan plugin…

I began translating dokan plugin but the string is still in waiting mode as I am native Amharic speaker i want to be Amharic locale translator and approve the string that translated by the contributor

#editor-requests

@elyas1 It’s a bit unclear which plugin you’re referring to. Could you please add a link to the plugin page?

PTE Request for OP Payment Service for WooCommerce

Hello Polyglots, I am the plugin author for OP Payment Service for WooCommerce. We have a number of great translation editors that we’d like to be able to approve translation for our plugin(s). Please add the following WordPress.org users as translation editors for their respective locales:

If you have any questions, just comment here. Thank you!
#editor-requests

Done for Swedish, please refer to http://wayback.fauppsala.se:80/wayback/20191101081404/https://wpsv.se/engagera-dig/stilguide-for-oversattningar/ and most welcome to join the Swedish Slack space and the channel “translations” where you’re more than welcome to ask for advice and “peer review”. Self-invite via http://wayback.fauppsala.se:80/wayback/20191101081404/https://wpsv.se/wpsv-slack/

PTE Request for Bookly

Hello Polyglots, I am the plugin author for Bookly http://wayback.fauppsala.se:80/wayback/20191101081404/https://wordpress.org/plugins/bookly-responsive-appointment-booking-tool/. We have a number of great translation editors that we’d like to be able to approve translation for our plugin(s). Please add the following WordPress.org users as translation editors for their respective locales:

— pt_PT – @jmdcp
— pt_BR – @jmdcp

We’ve been notified that Bookly plugin is not properly prepared for localization. But what we need now is just to add translations for readme files.

If you have any questions, just comment here. Thank you!
#editor-requests

It may not be too hard to get it working:
Your slug is “bookly-responsive-appointment-booking-tool”, and you need to change your text-domain to exactly the same string both in the header and in your code. (Currently you’re using just “bookly”.)

While you’re at it, you should also try to make your readme.txt smaller. It should not be bigger than 10k in order for the plugin directory to work well. The quickest solution is usually to move older changelog entries to a separate changelog.txt.

Hi!

I’ll be happy to promote @jmdcp to PTE for that plugin but he needs to:

  • join our slack instance
  • send more translations. Right now we have only 2 strings sent by him there. The stable project needs to be 95% translated in order to generate a translation package.

He can ping me here or on our slack instance to move forward with the request.

Thanks!

Since the next steps for #pt_BR now are with the translator, I’ll “untag” your locale in this request.

Hi,
As mentioned in How the Portuguese Community handles PTE Requests, I would like to suggest @jmdcp to please join the Portuguese Slack Community and channel #traducao to get in touch with the portuguese community of translators.
I would also like to suggest @jmdcp to please read all the info about Translation, including the Translator Guide that include some guidelines and the Glossary.

Similarly as above, untagging #pt_PT since next steps are on the translator.

Hi

Thanks a lot for all your replies!

Our Dutch translator @renevanhal contributed translations in Development Readme (trunk) http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/locale/nl/default/wp-plugins/bookly-responsive-appointment-booking-tool/

Since nobody replied to our PTE request for this user, can somebody at least approve translated strings? Can we request for approval in this thread or is there another place for such requests? Thanks.

@ladela
We’re all volunteers here, with more or less time available to respond to requests. You posted your request only three days ago, so I’m afraid that nobody in the #nl_NL team has been able to have a look yet at your request.

Hello Polyglots, I am the…

Hello Polyglots, I am the Theme author for [ http://wayback.fauppsala.se:80/wayback/20191101081404/https://translate.wordpress.org/projects/wp-themes/business-consultant-finder/ ]. We have a number of great translation editors that we’d like to be able to approve translation for our theme(s). Please add the following WordPress.org users as translation editors for their respective locales:

— fr_FR – @nour75016

#editor-requests

If you have any questions, just comment here. Thank you!

I corrected the locale tags #es_MX #fr_FR (and mentioned them here to have the notifications getting sent).

@athemeart Have you confirmed with these users that they want to take on the translation editor role for their respective locales?

@tobifjellner You can mark fr_FR as done, @athemeart reached to me directly on Slack. I’ll have a look at the translation as soon as possible.

Thanks.

Since you’re now in direct contact with each other, I’ll simply “untag” French in this request.