• Resolved Eduardo Larequi

    (@elarequi)


    I have just updated Jetpack plugin to version 7.1, in three different sites, with different themes, plugins and settings. I have also updated and uploaded .po and .mo Jetpack translation files, and even the new jetpack-es_ES-1bac79e646a8bf4081a5011ab72d5807.json file, which I have uploaded to /wp-content/plugins/jetpack/languages/json folder.

    After the update, all Jetpack strings in WordPress admin interface are translated, except Jetpack blocks, which remain in English. I can’t understand why, as the updated translation files (.mo and .json) include most of the strings related to Jetpack blocks.

    I’ve noticed the same behaviour in some other plugins which add blocks to new WordPress editor: even after updating and uploading the translation files, blocks are not translated. Here it is a ticket I recently opened about this issue in Block Gallery plugin: https://www.ads-software.com/support/topic/some-questions-about-block-gallery-translation/.

    Any help would be appreciated.

    Eduardo Larequi.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor James Huff

    (@macmanx)

    That’s odd, I have a few questions to narrow this down.

    1. What version of WordPress are you running?

    2. Why do you need to upload your own translations to /wp-content/plugins/jetpack/languages/json/? (Jetpack is fully translated into Spanish, so the translations should be pulled into /wp-content/languages/ when you go to Dashboard > Updates and update translations there.)

    Thread Starter Eduardo Larequi

    (@elarequi)

    I run WordPress 5.1 in all my sites.

    I upload my own translations because I don’t like some aspects of the “official” ones. GlotPress is a very good way of making collaborative translations, but at the same time we should admit that the quality of many of them is, to put it politely, quite questionable.

    Anyway, I do not want to criticize the efforts of the community, which I respect and admire. I only want to understand the mechanisms of the new translation system, as described here, https://make.www.ads-software.com/core/2018/11/09/new-javascript-i18n-support-in-wordpress/, and use it for my own particular needs.

    As for Jetpack, apart from the “official” .po and .mo files, which are downloaded automatically to /wp-content/languages/folder when user clicks the Update button, there is a /wp-content/plugins/jetpack/languages/json/ folder, which contains the translation .json files necessary for translating Jetpack admin pages. In other words: .po and .mo files are a necessary, but not a sufficient condition for translating Jetpack.

    My question is very simple: if Jetpack is fully translated to Spanish in GlotPress (and it is), why Jetpack blocks are not translated, even after updating all translation files? And this is only a part of the problem: as I have said before, many plugins which add blocks to Gutenberg editor lack appropriate translations for them. In some cases, these translations only translate admin pages, but not the name and the options of the blocks.

    In my humble opinion, the correct and thorough translation of non native Gutenberg blocks is a crucial point in the development and success of the new edition interface established by WordPress 5.0. I like Gutenberg very much and I don’t have any personal problem with texts in English, but at the same time I consider the current lack of translations for many, many blocks, a very serious problem for those users who feel uncomfortable with English words.

    In addition to about 12 personal sites (most of them are test sites), I manage more than 190 sites for schools in Navarre, Spain, and I feel very worried about the current situation. Until version 5.0, I was able to modify standard translations when I needed it, by means of custom .po and .mo files; now I do not know how to get proper and thorough translations.

    Plugin Contributor James Huff

    (@macmanx)

    Hm, this is rather odd, I see what you mean though.

    I just switched my site to Spanish, so I’m not using any custom translations, and at the very least block titles are not translated: https://cld.wthms.co/ZM15o9

    Additionally, some blocks are only partially translated: https://cld.wthms.co/wOZM2s

    It’s not just Spanish too, here’s German: https://cld.wthms.co/E0hTGr and https://cld.wthms.co/cKRFQo

    This is definitely _not_ expected behavior, so I have filed a bug report for our developers to investigate: https://github.com/Automattic/jetpack/issues/11491

    Thanks for the report!

    Thread Starter Eduardo Larequi

    (@elarequi)

    Thanks four your attention and interest, @macmanx.

    Thread Starter Eduardo Larequi

    (@elarequi)

    In versión 7.1.1 Jetpack blocks remain untranslated.

    Plugin Contributor James Huff

    (@macmanx)

    This will unfortunately need to wait for the next release: https://github.com/Automattic/jetpack/issues/11491#issuecomment-470084876

    Thread Starter Eduardo Larequi

    (@elarequi)

    Thanks for the information, James.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Jetpack blocks are not translated in version 7.1’ is closed to new replies.