Plugin translation

Honestly, I know very little about how the whole translation thing works. ?? I do know that I am using the appropriate translation functions (__(), _e(), etc).

I think you can become an editor for the project and add translations through www.ads-software.com. That will make the translations available to everyone. Alternatively, I think I can ship custom translation files (a .mo and .po file) with the plugin itself. I’m just not sure how to to go about adding your own translations to an existing plugin.

Thanks for suggestions! I became part of the translation community a few months ago after reading all the documentation and guidelines (mainly because of this plugin).

And although I haven’t publicly updated the translation entries for the last few versions (I intend to soon), I have a full translated file in my project.

I’ve spent some time today checking everything and so far I found that the language entries for the file “accordion-blocks.php” work fine.
The problem seems to be all the other entries for files such as “../src/block/edit.js“, that as far as I know doesn’t exist. Instead all of those entries should point to “build\index.js“. But I’m not sure that file is getting the texts from the language files.

Let me know what you can find and if you need any help I can give.

Thanks again for your time!

Interesting. That certainly give me somewhere to start looking. Give me a day or two to do some digging.

Hi @prccp,

I may have figured out the issue. Can you try this development version of the plugin and let me know if the translations work in the JS file?

Thanks, Phil!

Tomorrow is a national holiday here in Brazil and I won’t haven able to do it, but I’ll definitely take a look on friday.

@philbuchanan, I gave it a shot, but it didn’t work.

Since this beta version didn’t come with a translation file (I think WordPress generates those automatically) I used the file from the last version (with the translation file from previous version (1.3.5).

Editing strings in “\wp-content\plugins\accordion-blocks\build\index.js” worked, so I dont’t know if that file is not translated or the translation file references are outdated.

Well that is unfortunate.

I’ve tried creating the file manually using Poedit. But it refuses to find the strings from the build version of the JS file (i.e. /build/index.js). It will only grab them from the source (i.e. /src/), which doesn’t ship with the plugin (since that code is never executed). I’ve tried everything I can think of, but nothing seems to work.

I’m not sure what the next move is.