I have been translating for tamil ta_IN. Can I be made validator for the language?
Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts
Shouldn’t these have proper plural formatting?
All the others in that section have plural formatting and there are locales (like ours) where ONE covers no only 1 but also 11 etc.
All languages in development project has two same strings “Hide” and “Show”? There are 1718 strings instead of 1716.
Guys, I have done the translation to Chinese for bp 2.3 recently, is it a way to merge that in?
there is no response from current chinese team unfortunately.
Hello dear Administrators!
We have finished translating the development version. I wanted to merge the developemnt verstion’s translation with the 4.2.x but something went wrong, and translations percentage got 104%. Please, check it. Thanks!
Reading the descriptions of team roles (https://make.wordpress.org/polyglots/handbook/about/teams/#roles), I asume “Team Representative” is a locale level role, and “Lead” is a global role. Is it right? It’s not very clear.
Happy WordPress 4.3! Thank you all for your hard work on this release. Here’s the agenda for today’s chat:
- WordPress 4.3 locale stats
- WordPress 4.3 release support for the locales that are still behind
- Translate.WordPress.org changes and improvements
- New pages planned to add to the contributor handbook
- Open discussion
If you have anything to add to the agenda, suggestions are welcome in the comments
See you at 10am UTC.
The results of the intial build:
- 35 release packages for 4.3 were built: he_IL, el, is_IS, it_IT, de_DE_formal, de_DE, en_GB, en_NZ, eo, fi, fr_FR, lt_LT, nb_NO, sv_SE, es_MX, th, cy, tr_TR, es_ES, sk_SK, nn_NO, pt_PT, ro_RO, en_CA, ko_KR, ar, bs_BA, hy, bg_BG, eu, pt_BR, en_AU, nl_NL, sq, and da_DK
- 45 language packs for 4.3 were updated: hu_HU, he_IL, el, is_IS, id_ID, ja, it_IT, de_DE_formal, de_DE, en_GB, en_NZ, eo, fi, gl_ES, fr_FR, lt_LT, nb_NO, sv_SE, es_MX, th, cy, tr_TR, es_ES, sk_SK, nn_NO, pl_PL, pt_PT, sr_RS, ro_RO, en_CA, ko_KR, ca, ar, zh_TW, bs_BA, hy, bg_BG, eu, pt_BR, hr, en_AU, bn_BD, nl_NL, sq, and da_DK
Thanks to all of the contributors who provided translations for WordPress 4.3 and subtitles for the release video! You rock! 🎉
Reminder: Please do not translate…
dewith your locale.)
When translating strings you should always keep an eye on the comments. If it includes a hint like “Do not translate into your own language.” then your shouldn’t translate it.
The upcoming release of WordPress will become available in the next 24 hours. This is a reminder on what you should do to benefit of the automated package build process.
- If you have never had any custom changes and i18n.svn.wordpress.org is entirely empty for your locale, you do not need to do anything. Your release package will be created automatically for you. An example locale is en_GB.
- If you have no custom changes for 4.3, please ensure you have an empty
tags/4.3/distdirectory at i18n.svn.wordpress.org. (Having an empty
trunk/distdirectory does not help you.) You do not need a
tags/4.3is empty. An example would be nl_NL. Your release package will be created automatically for you.
- If you have minor custom changes consisting of, at most, a translated readme, license file, and wp-config-sample.php, please ensure these files exist in a
tags/4.3/distdirectory at i18n.svn.wordpress.org. (Having your stuff in only
trunk/distdoes not count.) An example would be de_DE or nn_NO. Your release package will be created automatically for you.
- If you have extensive custom changes consisting of other files, such as
wp-content/languages/$locale.phpor core modifications, you will need to create a package via Rosetta as you have done in the past.
If your locale is currently eligible for automatic creation of release packages (which includes being at 100%), you’ll find an RC2 build generated from tags/4.3-RC2 waiting for you on your dashboard. Please inspect these ZIPs. Those locales are: de_DE_formal, de_DE, it_IT, en_CA, en_AU, eo, nb_NO, sv_SE, tr_TR, nn_NO, ro_RO, nl_NL, ko_KR, eu, hy, and bs_BA (zip links).
Language packs are generated for de_DE_formal, de_DE, el, he_IL, it_IT, id_ID, gl_ES, fr_FR, en_CA, en_AU, eo, ja, nb_NO, sv_SE, es_ES, th, tr_TR, sk_SK, sr_RS, nn_NO, pl_PL, ro_RO, nl_NL, ko_KR, eu, hy, bs_BA, ca, and bg_BG.
Locales which are at 100% but skipped because of missing tags/branches: el, he_IL, id_ID, gl_ES, fr_FR, ja, es_ES, th, sk_SK, sr_RS, pl_PL, ca, and bg_BG.
If you have any questions, comments, concerns, or issues, please comment here or find us in #polyglots on Slack.
WordPress 4.3 is scheduled for tomorrow – August 18th. Strings have been frozen for a while, last week we also got the last 14 strings in, so we’re in a hard freeze since Friday. It would be great if the remaining strings were translated and we were prepared to launch with more than 60 locales.
Pinging the validators for the locales who have more than 90% translated. If you get a chance, please get your locales ready for the release tomorrow.
More than 95%
30 locales have more than 95% translated. Translators and translation editors, please head to your locales and translate the about page strings, so we can prepare the packages for the release on Aug 18th
Locale WP Locale Version GlotPress Albanian Shqip sq 4.2.2 95% sq Details Arabic العربية ar 4.2.4 99% ar Details Azerbaijani Azərbaycan dili az 4.2.4 99% az Details Bengali বাংলা bn_BD 4.2.2 97% bn Details Bulgarian Български bg_BG 4.2.4 99% bg Details Chinese (China) 简体中文 zh_CN 4.2.2 95% zh-cn Details Chinese (Taiwan) 繁體中文 zh_TW 4.2.4 97% zh-tw Details Croatian Hrvatski hr 4.2.4 98% hr Details Danish Dansk da_DK 4.2.4 98% da Details English (New Zealand) English (New Zealand) en_NZ None 99% en-nz Details English (UK) English (UK) en_GB 4.2.4 99% en-gb Details Estonian Eesti et 4.2.4 95% et Details German (Switzerland) Deutsch (Schweiz) de_CH 4.2.4 95% de-ch Details Hungarian Magyar hu_HU 4.2.4 99% hu Details Icelandic Íslenska is_IS 4.2.4 96% is Details Korean 한국어 ko_KR 4.2.4 99% ko Details Lithuanian Lietuvių kalba lt_LT 4.2.2 95% lt Details Norwegian (Nynorsk) Norsk nynorsk nn_NO 4.2.4 99% nn Details Occitan Occitan oci 4.2.4 99% oci Details Pashto پښتو ps 4.1.2 96% ps Details Persian فارسی fa_IR 4.2.4 95% fa Details Portuguese (Brazil) Português do Brasil pt_BR 4.2.4 95% pt-br Details Portuguese (Portugal) Português pt_PT 4.2.4 99% pt Details Russian Русский ru_RU 4.2.4 95% ru Details Serbian Српски језик sr_RS 4.2.4 99% sr Details Spanish (Mexico) Español de México es_MX 4.2.4 95% es-mx Details Spanish (Peru) Español de Perú es_PE 4.2.2 95% es-pe Details Tagalog Tagalog tl 4.2.2 99% tl Details Turkish Türkçe tr_TR 4.2.4 99% tr Details Ukrainian Українська uk 4.2.4 99% uk Details
Pinging the translation editors for the langueages mentioned above: @gaygysyz, @wordpress-tr, @krzheiyah @Kel-DC, @marcozink, @hiwhatsup, @dimadin, @lanche86, @Reyson, @Atrax, @SergeyBiryukov, @slaFFik, @jenia, @krioteh, @catiakitahara, @Gabriel Reguly, @Dianakc, @rafaelfunchal, @valeriosza, @vmassuchetto, @vanillalounge, @alvarogois, @nbar, @mani_monaj, @Gonahkar, @sajadsafi, @msadat, @meinmycell, @chriscena, @hgmb, @peterhoob, @pokeraitis, @jonasltu, @drssay, @Kaul, @martian36, @stebbiv, @egill, @samueljon, @valurthor, @djzone, @fgywp, @sooskriszta, @Blintux, @openstream, @swissspidy, @swissky, @Erko.Risthein, @UncleOwl, @petskratt, @westi, @s1m0nd, @DJPaul, @GaryJ, @tareiking, @Shevy, @culturemark, @tntc1978, @DanielJuhl, @hammerfar, @brianbrandt, @GeorgWP, @maxemil, @weblysdal, @intoxstudio, @heinohund, @mikwolbre, @Mirta, @yuraz, @Kirin_Lin, @pseric, @s9011514, @levinng, @carrielis, @bibi-wang, @Dreamcolor, @jiehanzheng, @dallaslu, @xslidian, @musiclog, @franklsf, @jimmyxu, @tareq1988, @wzislam, @badsha_eee, @muhsinmushviq, @rasheed, @alex-ye, @Besnik
Seven locales have more than 90% translated
Locale WP Locale Version GlotPress French (Canada) Français du Canada fr_CA None 94% fr-ca Details Hazaragi هزاره گی haz 4.1.2 92% haz Details Macedonian Македонски јазик mk_MK 4.1.1 92% mk Details Myanmar (Burmese) ဗမာစာ my_MM 4.1 92% mya Details Slovenian Slovenščina sl_SI 4.1.2 94% sl Details Uighur Uyƣurqə ug_CN 4.1.2 91% ug Details Vietnamese Tiếng Việt vi 4.2.1 93% vi Details
Pinging the translation editors for the languages mentioned above:
@rilwis, @philiparthurmoore, @tucq, @htdat, @tony.bui, @huynetbase, @Moorshidi, @Alim-Ahat, @andrejz, @Hekos, @st1FFFy, @herzcthu, @minnkyaw, @chombium, @Kuzmanov, @goce.mitevski, @jjanev86, @l10n, @server986, @tohave
Thank you all for your help and the time you dedicate to the project. Now going to go take care of the bg_BG strings, as it’s also only 99% done.
As we head into a new era (plugins and theme in the repo, yay), we will need to improve documentation on how things are done in the team.
I’ve dedicated some time in August for working on the Handbook, but your help will be highly appreciated!
How can I help?
I’m so glad you asked! Here is how:
Read and suggest edits
- Go to the handbook, read separate sections
- Suggest edits in this Hackpad: https://hackpad.com/Polyglots-handbook-suggested-edits-5kK1odaUYu9 – suggestions might include changes like the name of the page, certain terms, wrong term corrections, typo fixes, consistency problems with other pages, missing content
- In the Glossary part of the document, please add all terms that you were not familiar with and always wondered about, so we can explain them better (ex: soft, hard freeze, release package, p2, trac, meta trac, glotpress). This is the team’s Glossary – for all terms we, as translators and translation editors, need to be familiar with.
Test the handbook using a persona
- As a new translator, just starting to help out – look if it’s easy to understand how to
- Find your locale and start translating
- Understand how your translations get online
- Understand who is in charge of validating your suggestions
- Find information about your locale translation editor
- Contact your local translation editor
- Contact the polyglots team
- Find other polyglots to talk to, understand what channels we use to communicate
- Become a part of the weekly Polyglots conversations
- As an experienced translator, wishing to become a part of the translation editor team – look if it’s easy to understand:
- What is the role of the translation editor
- How to find out who the other contributors for your locale are
- How to contact the translation editors for your locale
- How to ask to become a part of the translation editors for your locale
- As a new translation editor, who just got in charge of a new locale test if you can understand and enough information on:
- What is the role of the translation editor and what your responsibilities will be
- How to setup your local site – translate it, setup the main pages, setup RTL, etc.
- How to validate strings
- How to use the translation tools provided
- How to communicate with translators
- How to communicate with the Polyglots team
- How to join the weekly chats and what are the communication channels the team uses
- How a language gets into the WordPress installer
- How to prepare and release a package
- As a new contributor for a non exsitent locale who would like to translate WordPress in their language
- How to request the new locale
- Who to contact for help
- What does the role of the translation editor include and what are the responsibilities
These are just some example questions, I am sure a lot of you who have experience with user testing will have more ideas about questions that can be included.
The main structure of the handbook will remain as is now, we can, however, add new pages and sections and expand current sections. The Hackpad includes all current pages – if you have an edit to suggest, please add it as a comment below the page’s name.
If you’d like to suggest new pages, please do it at the bottom of the document below the “New pages suggestions” and provide the path to the new page you’re suggesting. Example: “Setting up your local site > Translating the interface – gives a link to the Rosetta project and a step by step guide about translating and requesting a deploy of the translation on the site”.
If you feel you can dedicate more time for this and have sufficient experience with working on the team, please comment below and you can be added as an editor for the Handbook, so you can add and edit pages.
Thank you in advance for your help!
During the last polyglots chat a seldom known feature has been brought up – *WordPress in all languages can have the WordPress News widget in the Dashboard display news from local sites (like http://pl.wordpress.org).*
This wasn’t really documented anywhere AFAIK so *plase push this post to the handbook*. The 2 strings described below should also have comments added, which I ask anyone to do.
In every install of WordPress there’s a WordPress News widget in the Dashboard (you can show and hide it under the Screen Options), which always displays 1 expanded, most recent post from the 1st RSS feed source (by default: blog post from https://wordpress.org/news/) and 3 post titles from the 2nd RSS feed source (by default: blog posts from https://planet.wordpress.org/).
You can change both of those RSS feed URLs to fetch news from other sources, like your local WordPress website.
The 2nd site is a “Planet” service, which is an automatic aggregator of blog posts from various WordPress sites. It’s not very likely that you have a Planet set up for your language – if not, you can eighter create it or provide the same URL for both sources, which results in 1 expanded post from that feed and – below – 3 most recent blog posts from the same feed (1st of which will be the same as the expanded one, but it’s the best option we’ve got). You can also set the 2nd feed URL to the English WordPress.org blog, but then the expanded post will be in your local language, and 3 post titles that follow will be in English. It’s your call.
To set the feed URLs, go to https://translate.wordpress.org/ and navigate to your language. Then, you will see all currently maintained versions of WordPress. Do the following steps for *all versions:* click the title that represents a version -> Administration -> Filter -> type “feed” in the Term field -> click the Filter button -> scroll down to see 2 strings that are URLs of feeds.
*Note:* do NOT set the translation of these strings to an empty string, a space bar, a # sign or the URL of your local WordPress site (like http://pl.wordpress.org for Polish). Read on.
The original “https://wordpress.org/news/feed/” string is the 1st described feed source. The 1st post from it is displayed in the Dashboard widget, in an expanded fashion. You most likely want to set this to your local, official WordPress site feed URL. Navigate to your local WordPress site to discover this URL (you might need to search for it in the site’s source code in the head section). For Polish, the feed URL is https://pl.wordpress.org/feed/
The original “https://planet.wordpress.org/feed/” string is the 2nd described feed source. The 3 most recent post titles from it are displayed in the Dashboard widget. You can translate this string to any other RSS or Atom feed URL. You most likely want to consider using:
- a Planet for WordPress feed in your language, if there is one,
- the same URL as for the 1st feed source, so pointing to the local WordPress.org site feed,
- the feed for the official English WordPress.org blog, which is: https://wordpress.org/news/feed/
- leaving the English Planet URL feed as it was: https://planet.wordpress.org/feed/
Remember to change these for all current WordPress versions, as described above.
After approving the string change, wait about 12-24 hours for translation propagation. After you update your translation files in WordPress, see if it works. If you still see the news in English, wait another 12 hours for the caching mechanism to refresh that content.
“Hard” string freeze is now in effect for 4.3.
The About page strings are now available for translation, and we expect to tag RC3 later today or tomorrow.
“Hard” freeze means that all core and About page strings are available for translation, and all other string changes have been frozen beyond this point.
Strings for WPiOS 5.5
Hey folks, we’re shipping WPiOS 5.5 pretty soon and we could use some help translating the release notes and the app strings. If you’ve got some spare time, we’d appreciate any help towards getting those strings translated